Skip to content

How to update old Operator to new Operator 4.0.9 to newest version

Cesar Celis Hernandez edited this page Nov 14, 2022 · 17 revisions
  1. Assuming you are coming from a very old version like 4.0.9 of Operator
Screenshot 2022-11-14 at 10 12 14 AM
$ k version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:16:20Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:06:30Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/arm64"}
WARNING: version difference between client (1.23) and server (1.21) exceeds the supported minor version skew of +/-1

Where client version and server version are less than 1.24 in both client and server

  1. My first recommendation is to update kubernetes version in your client and server because 1.23 or 1.21 is too old already and new Operator version is intended to run in newer versions of k8s anyway. So let's do it.

https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/

  1. Updated the images of the Operator Deployment, operator and console:
image: minio/operator:v4.5.4
image: minio/console:v0.21.1
  1. Applied changes for new operator:
kubectl apply -k github.com/minio/operator/
Clone this wiki locally