Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rancher vSphere CPI chart for 1.23 and 1.24. #2867

Closed
4 tasks done
phillipsj opened this issue May 6, 2022 · 9 comments
Closed
4 tasks done

Update Rancher vSphere CPI chart for 1.23 and 1.24. #2867

phillipsj opened this issue May 6, 2022 · 9 comments
Assignees
Milestone

Comments

@phillipsj
Copy link
Contributor

phillipsj commented May 6, 2022

Rancher vSphere chart for CPI and CSI have been updated. In the update process, the chart now supports 1.23 with the official image and 1.24 through skew policy.

CPI: 1.2.201

Related Issues:

Backports:

  • main
  • 1.23
  • 1.22
  • 1.21
@phillipsj
Copy link
Contributor Author

@rancher-max whats the correct process for this now? I keep forgetting how you all move these issues.

@rancher-max
Copy link
Member

rancher-max commented May 9, 2022

@rancher-max whats the correct process for this now? I keep forgetting how you all move these issues.

The process is to create backport issues for applicable branches and assign the correct milestones and status in the Development Project. I can take care of this.

That being said, I do wonder if the backport to 1.21 should be present or not now since I think 1.21.12 was our last release of 1.21 (except for critical bug fixes).
EDIT: 1.21 should be present as I guess I was wrong about EOL: https://kubernetes.io/releases/patch-releases/#1-21

@rancher-max rancher-max added this to the v1.24.0 milestone May 9, 2022
@rancher-max
Copy link
Member

/backport v1.23.7+rke2r1

@rancher-max
Copy link
Member

/backport v1.22.10+rke2r1

@rancher-max
Copy link
Member

@ShylajaDevadiga Let's wait to validate this one particularly until we have 1.24 present in master branch.

@rancher-max
Copy link
Member

/backport v1.21.13+rke2r1

@phillipsj
Copy link
Contributor Author

@rancher-max I already did the backports

@rancher-max
Copy link
Member

Yep I linked your PRs to them. We like to have an issue per milestone for the backports so that we can track the validations more clearly.

@ShylajaDevadiga
Copy link
Contributor

Validated on release branch 1.23 using commit id a0e81e4

  • Validated chart version is correct
  • correct version of the CPI image deployed
  • pv,pvc is created successfully
rancher@rancher1:~$ rke2 -v
rke2 version v1.23.6-dev+a0e81e4a (a0e81e4a88665d55d4433773e3e9513ef0196d50)

rancher@rancher1:~$ helm ls -A
NAME               	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART                                       	APP VERSION   
rancher-vsphere-cpi	kube-system	1       	2022-05-24 21:58:54.14385817 +0000 UTC 	deployed	rancher-vsphere-cpi-1.2.201                 	1.2.2         
rancher-vsphere-csi	kube-system	1       	2022-05-24 21:58:54.057679633 +0000 UTC	deployed	rancher-vsphere-csi-2.5.1-rancher101        	2.5.1-rancher1

rancher@rancher1:~$ kubectl get pods -A
NAMESPACE     NAME                                                    READY   STATUS              RESTARTS   AGE
default       basic                                                   0/1     ContainerCreating   0          10s
kube-system   etcd-rancher1                                           1/1     Running             0          6m55s
kube-system   helm-install-rancher-vsphere-cpi-qsqsd                  0/1     Completed           0          7m21s
kube-system   helm-install-rancher-vsphere-csi-vz8px                  0/1     Completed           0          7m21s
kube-system   helm-install-rke2-canal-dt9lx                           0/1     Completed           0          7m21s
kube-system   helm-install-rke2-coredns-mfszn                         0/1     Completed           0          7m21s
kube-system   helm-install-rke2-ingress-nginx-gwhrr                   0/1     Completed           0          7m21s
kube-system   helm-install-rke2-metrics-server-xtvgh                  0/1     Completed           0          7m21s
kube-system   kube-apiserver-rancher1                                 1/1     Running             0          6m58s
kube-system   kube-controller-manager-rancher1                        1/1     Running             0          7m
kube-system   kube-proxy-rancher1                                     1/1     Running             0          6m46s
kube-system   kube-scheduler-rancher1                                 1/1     Running             0          6m51s
kube-system   rancher-vsphere-cpi-cloud-controller-manager-nxdvx      1/1     Running             0          6m57s
kube-system   rke2-canal-98lbb                                        2/2     Running             0          6m56s
kube-system   rke2-coredns-rke2-coredns-547d5499cb-z88bw              1/1     Running             0          6m57s
kube-system   rke2-coredns-rke2-coredns-autoscaler-65c9bb465d-qtwj4   1/1     Running             0          6m57s
kube-system   rke2-ingress-nginx-controller-4gbnf                     1/1     Running             0          6m7s
kube-system   rke2-metrics-server-6564db4569-652jg                    1/1     Running             0          6m20s
kube-system   vsphere-csi-controller-bbc6db9f8-flsnh                  5/5     Running             0          6m56s
kube-system   vsphere-csi-controller-bbc6db9f8-g8cpj                  5/5     Running             0          6m56s
kube-system   vsphere-csi-controller-bbc6db9f8-pz2fh                  5/5     Running             0          6m56s
kube-system   vsphere-csi-node-d65tr                                  3/3     Running             0          6m24s

rancher@rancher1:~$ kubectl get sc,pv,pvc

NAME                                                   PROVISIONER              RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
storageclass.storage.k8s.io/vsphere-csi-sc (default)   csi.vsphere.vmware.com   Delete          Immediate           false                  10m

NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM            STORAGECLASS     REASON   AGE
persistentvolume/pvc-228490b7-5926-4e81-be6b-60091a9f98a1   1Gi        RWO            Delete           Bound    default/claim1   vsphere-csi-sc            9s

NAME                           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
persistentvolumeclaim/claim1   Bound    pvc-228490b7-5926-4e81-be6b-60091a9f98a1   1Gi        RWO            vsphere-csi-sc   10s

rancher@rancher4:~$ kubectl describe pod -n kube-system rancher-vsphere-cpi-cloud-controller-manager-nxdvx |grep image
  Normal  Pulling    11m   kubelet            Pulling image "rancher/mirrored-cloud-provider-vsphere-cpi-release-manager:v1.23.0"

Validated on master branch using commit id 139c31c

  • Validated chart version is correct
  • correct version of the CPI image deployed
  • pv,pvc is created successfully
rancher@rancher4:~$ rke2 -v
rke2 version v1.24.0-dev+139c31c8 (139c31c8b75d96e1ec60be65a4b334ef456de30d)
go version go1.18.1b7
rancher@rancher4:~$ helm ls -A
NAME               	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART                                       	APP VERSION   
rancher-vsphere-cpi	kube-system	1       	2022-05-24 23:58:13.696047425 +0000 UTC	deployed	rancher-vsphere-cpi-1.2.201                 	1.2.2         
rancher-vsphere-csi	kube-system	1       	2022-05-24 23:58:13.635196216 +0000 UTC	deployed	rancher-vsphere-csi-2.5.1-rancher101        	2.5.1-rancher1
rke2-canal         	kube-system	1       	2022-05-24 23:58:13.599948206 +0000 UTC	deployed	rke2-canal-v3.22.2-build2022050902          	v3.22.2       
rke2-coredns       	kube-system	1       	2022-05-24 23:58:13.738110005 +0000 UTC	deployed	rke2-coredns-1.17.000                       	1.9.1         
rke2-ingress-nginx 	kube-system	1       	2022-05-24 23:58:43.377445176 +0000 UTC	deployed	rke2-ingress-nginx-4.1.002                  	1.2.0         
rke2-metrics-server	kube-system	1       	2022-05-24 23:58:43.543227526 +0000 UTC	deployed	rke2-metrics-server-2.11.100-build2021111904	0.5.0         
rancher@rancher4:~$ kubectl get pods -A
NAMESPACE     NAME                                                    READY   STATUS              RESTARTS   AGE
default       basic                                                   0/1     ContainerCreating   0          3m57s
kube-system   etcd-rancher4                                           1/1     Running             0          7m46s
kube-system   helm-install-rancher-vsphere-cpi-p5sdv                  0/1     Completed           0          7m36s
kube-system   helm-install-rancher-vsphere-csi-jnwkh                  0/1     Completed           0          7m36s
kube-system   helm-install-rke2-canal-8g4zv                           0/1     Completed           0          7m36s
kube-system   helm-install-rke2-coredns-h5gwg                         0/1     Completed           0          7m36s
kube-system   helm-install-rke2-ingress-nginx-b5bc7                   0/1     Completed           0          7m36s
kube-system   helm-install-rke2-metrics-server-9mqfv                  0/1     Completed           0          7m36s
kube-system   kube-apiserver-rancher4                                 1/1     Running             0          7m19s
kube-system   kube-controller-manager-rancher4                        1/1     Running             0          7m50s
kube-system   kube-proxy-rancher4                                     1/1     Running             0          7m44s
kube-system   kube-scheduler-rancher4                                 1/1     Running             0          7m50s
kube-system   rancher-vsphere-cpi-cloud-controller-manager-45k9m      1/1     Running             0          7m24s
kube-system   rke2-canal-nkf7h                                        2/2     Running             0          7m23s
kube-system   rke2-coredns-rke2-coredns-658f5f9786-mhgrs              1/1     Running             0          7m24s
kube-system   rke2-coredns-rke2-coredns-autoscaler-766678cb7b-f597m   1/1     Running             0          7m24s
kube-system   rke2-ingress-nginx-controller-s9wxj                     1/1     Running             0          6m42s
kube-system   rke2-metrics-server-6979d95f95-d4sw2                    1/1     Running             0          6m54s
kube-system   vsphere-csi-controller-568f5c779b-hmdqf                 5/5     Running             0          7m24s
kube-system   vsphere-csi-controller-568f5c779b-rh72z                 5/5     Running             0          7m24s
kube-system   vsphere-csi-controller-568f5c779b-wv59h                 5/5     Running             0          7m24s
kube-system   vsphere-csi-node-h985m                                  3/3     Running             0          7m

rancher@rancher4:~$  kubectl get sc,pv,pvc
NAME                                                   PROVISIONER              RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
storageclass.storage.k8s.io/vsphere-csi-sc (default)   csi.vsphere.vmware.com   Delete          Immediate           false                  10m

NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM            STORAGECLASS     REASON   AGE
persistentvolume/pvc-1db67040-2e53-46d9-a616-4ee7ae5af676   1Gi        RWO            Delete           Bound    default/claim1   vsphere-csi-sc            6m51s

NAME                           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
persistentvolumeclaim/claim1   Bound    pvc-1db67040-2e53-46d9-a616-4ee7ae5af676   1Gi        RWO            vsphere-csi-sc   6m52s
 

rancher@rancher4:~$ kubectl describe pod -n kube-system rancher-vsphere-cpi-cloud-controller-manager-45k9m |grep image
  Normal  Pulling    7m31s  kubelet            Pulling image "rancher/mirrored-cloud-provider-vsphere-cpi-release-manager:v1.23.0"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants