Skip to content

Operator Upgrade from 4.5.4 to 5.0.11 with KES and KMS enabled

Jump to bottom
Cesar Celis Hernandez edited this page Feb 8, 2024 · 7 revisions

Objective:

To document the upgrade process of the Operator under these circumstances:

  • Method: Helm or Kustomize
  • Initial Operator Version: 4.5.4
  • KES with Vault as KMS solution
  • Initial KES Version: v0.18.0
  • Final Operator Version: 5.0.11

Steps:

  1. Have Cluster with Initial Versions

  2. Make sure to keep KES Version and MinIO Version in the Tenant Spec, example:

spec:
  image: minio/minio:RELEASE.2023-10-16T04-13-43Z
  kes:
    image: minio/kes:v0.18.0

By doing so, the Operator will retain these versions throughout the upgrade process.

  1. Then you can upgrade Operator Version via Helm Chart or Kustomization

  2. Once you have upgraded to the latest version of the Operator, such as 5.0.11, you can proceed with upgrading MinIO and KES. Keep in mind that the configuration for KES may change over time, so ensure that your secret for KES configuration is updated accordingly. You can obtain the latest KES configuration from here: https://github.com/minio/kes/blob/master/server-config.yaml

Results:

In the aforementioned circumstances, the test transitioned smoothly from version 4.5.4 to 5.0.11 of the operator in a local cluster without any issues. However, if any KES issues are detected during this process, please assist us in obtaining the exact steps necessary to understand and identify the possible issue observed.

Clone this wiki locally