Master Provisioning 2.1.4

1 minute read

RELEASED: Public: 2018-04-11

New features


Resolved issues

  • CloudBees Internal Ticket: [TIGER-3983]

    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

  • CloudBees Internal Ticket: [TIGER-4098]

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

  • CloudBees Internal Ticket: [TIGER-4406]

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

  • CloudBees Internal Ticket: [TIGER-4228]

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

  • CloudBees Internal Ticket: [TIGER-4214]

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

  • CloudBees Internal Ticket: [TIGER-4379]

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

Known issues