Master Provisioning 2.1.4

A custom storage class name can now be specified to provision managed controllers, instead of relying on the default storage class available in the Kubernetes cluster

Simplified the managed controller lifecycle: start/stop/restart. Operations Center will never delete an existing volume

Fix compatibility with recent nginx-ingress controller by adding a new set of annotations with the updated namespace

Jenkins command line arguments can be specified in the managed controller configuration

Fixed a NoSuchElementException displayed in the logs, preventing the provisioning status from being displayed in the controller manage screen

Fix some cases where controller state would not be correctly computed after a Operations Center restart or upgrade, preventing the controller from reconnecting