#Upgrading k8s to 1.25

1 messages · Page 1 of 1 (latest)

echo turtle
#

What is the correct order of operations for upgrading a k8s installation with the Trident operator from pre-1.25 to 1.25 or later? Are there versions of k8s that both the pre-1.25 and post-1.25 operator YAMLs support? Or do I need to remove the operator, then upgrade k8s, then install the new operator?

young mason
#

As long as you are running Trident 23.01 or newer, once you upgrade to k8s 1.25, the operator will recognize the change and remove the use of the Pod Security Policies (PSP) that it was previously using. There is no need to uninstall/re-install the operator.

echo turtle
#

@young mason thanks, so I can tell the customer to make sure to be at least on Trident 23.01 (with the pre-1.25 YAML) and then just upgrade his k8s environment, correct?

young mason
#

Yes

#

For some reason everyone want this to be more difficult than it is. It really is that simple. 😃

white swift
#

Openshift 4.11 is on Kubernetes 1.24
Openshift 4.12 is on Kubernetes 1.25

The prerequisite for the upgrade from openshift 4.11 to openshift 4.12 is to remove the PSP.

#

Hence, currently in my openshift 4.11 ( Kubernetes 1.24 ); Netapp trident 23.07.1 installed via trident operator method by applying bundle_pre_1_25.yaml .

#

I would like to stay on 23.07.1 . Can I just remove the PSP resources and other deletions and add lines as seen here?

#

Objective is to have minimal downtime.

white swift
young mason
#

What steps did you follow to hit #819?

white swift
#
  1. On openshift 4.11 ( Kubernetes 1.24 ); manually install using bundle_pre_1.25.yaml
  2. To prepare for upgrade from 4.11 to openshift 4.12 ( Kubernetes 1.25 ) based; A. uninstall using bundle_pre_1.25.yaml and then manually install bundle_post_1.25.yaml .
#

As the PSP resource is not bundled with bundle_post_1.25.yaml ; it was not installed. Yet , I noticed PSP resources named similar to trident-node and trident-controller* being created by trident-operator.

young mason
#

As long as you are running Trident 23.01 or newer, once you upgrade to k8s 1.25, the operator will recognize the change and remove the use of the Pod Security Policies (PSP) that it was previously using. There is no need to uninstall/re-install the operator or the bundle.

white swift