Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

Switch to latest✕

Post-upgrade actions

Since Kubernetes policy does not allow updating images in existing IAM jobs, after Container Cloud automatically upgrades to 2.21.0, update the MariaDB image manually using the following steps:

1. Delete the existing job:

   kubectl delete job -n kaas iam-cluster-wait
   

2. In the management Cluster object, and add following snippet:

   kaas:
     management:
       enabled: true
       helmReleases:
       - name: iam
         values:
           keycloak:
             mariadb:
               images:
                 tags:
                   mariadb_scripted_test: general/mariadb:10.6.7-focal-20220811085105
   

   Wait until helm-controller applies changes.

3. Verify that the job was recreated and the new image was added:

   kubectl describe job -n kaas iam-cluster-wait | grep -i image