Upgrading TIBCO Control Plane

You can upgrade self-hosted TIBCO Control Plane by upgrading updated Helm charts.

Before you begin If you are using a custom container registry, you must push the updated images to your custom registry. For more information, see Pushing Images to Custom Container Registry.
Note: You cannot change default container registry and Helm chart repository when upgrading from an earlier version.
    Procedure
  1. Update your local helm repo with the latest charts.

    helm repo update
  2. For a new installation of TIBCO Control Plane, recipe jobs have Time to Live (TTL) of one hour. They get automatically deleted after one hour. If you are trying to upgrade within this hour, you must delete the recipe jobs first.

    kubectl delete job -n <namespace> dp-oauth2proxy-recipe-oauth2proxy tp-cp-hawk-console-recipes-hawk-console tp-cp-infra-recipe-cp-proxy tp-cp-infra-recipe-integrationcore tp-cp-infra-recipe-monitor-agent tp-cp-infra-recipe-o11y-exporter tp-cp-infra-recipe-o11y tp-cp-servicemesh-recipe capability-contribution-tibco-hub
  3. Upgrade platform-bootstrap chart by using the following command. For more information about the chart version, see Helm Chart Version Matrix.

    helm upgrade --install --reset-then-reuse-values -n <namespace> platform-bootstrap tibco-platform/platform-bootstrap --version=<version>

    Example:

    helm upgrade --install --reset-then-reuse-values -n cp1 platform-bootstrap tibco-platform/platform-bootstrap --version=1.4.85
  4. Upgrade platform-base chart by using the following command. For more information about the chart version, see Helm Chart Version Matrix.

    helm upgrade --install --reset-then-reuse-values -n <namespace> platform-base tibco-platform/platform-base --version=<version>
  5. If you are already signed in to TIBCO Control Plane, sign out and sign in again.