Existing CloudBees Core installations to Helm migration guide

You can use the CloudBees Core Helm chart to migrate an existing CloudBees Core installation to Helm.

Why migrate?

Installations of CloudBees Core performed without Helm used a YAML file, and administrators had to directly modify the cloudbees-core.yml file to update or modify the CloudBees Core configuration.

Switching to Helm to manage CloudBees Core gives administrators the ability to "offload" administration of CloudBees Core to Helm and automate the upgrade process.

Before you migrate

  1. As all migrations carry a risk of data loss, CloudBees strongly recommends backing up your Operations Center and JENKINS_HOME prior to migrating. For more information, see the Backup and restore guide.

  2. If you wish to use a custom values file to set options, set that file up prior to starting the migration.

Example migration custom values file

The following custom values file is based on the migration-values-example.yaml file from the CloudBees Public GitHub repository.

# A helm example values file for migrating a CloudBees Core for Modern Platform Install.
# Install an nginx-ingress controller
  Enabled: false <1>

  # Set the HostName for the Operation Center
  HostName: 'cloudbees-core.example.com' <2>
    ## Set this to true in order to enable TLS on the ingress record
      Enable: false <3>
      SecretName: core-example-com-tls
      Host: jenkins.cluster.local

# If you are migrating from an existing manual installation of CloudBees Core, provide the PVC that was created
# during the initial installation
  ExistingClaim: 'jenkins-home-cjoc-0' <4>
1 If you want NGINX Ingress controller installed, change this value to true.
2 Replace cloudbees-core.example.com domain name with your domain name.
3 If you want to enable TLS, set this value to true.
4 jenkins-home-cjoc-0 is the PVC that is created using the CloudBees Core, so keep this value.
Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.