Release 1.22.6

kubernetes · Mar 25, 2022 · 493ec2a · 493ec2a
1 parent 9c62385
commit 493ec2a
Show file tree

Hide file tree

Showing 10 changed files with 15 additions and 15 deletions.
diff --git a/index.yaml → charts/index.yaml b/index.yaml → charts/index.yaml
@@ -2,10 +2,10 @@ apiVersion: v1
 entries:
   vsphere-cpi:
   - apiVersion: v2
-    appVersion: 1.22.5
-    created: "2022-01-20T21:02:52.518394-08:00"
+    appVersion: 1.22.6
+    created: "2022-03-24T21:52:41.788836-07:00"
     description: A Helm chart for vSphere Cloud Provider Interface Manager (CPI)
-    digest: 47c6c4d533d7ea84e57e7fe012f30f9af76be9f1380641fd2a0ce0fb682f8524
+    digest: e71a47c8fab9dd32012025eae90b14db8d15284f18f3a386b7feb4976c7369d8
     home: https://github.com/kubernetes/cloud-provider-vsphere
     icon: https://raw.githubusercontent.com/kubernetes/cloud-provider-vsphere/master/docs/vmware_logo.png
     keywords:
@@ -18,6 +18,6 @@ entries:
     sources:
     - https://github.com/kubernetes/cloud-provider-vsphere
     urls:
-    - https://kubernetes.github.io/cloud-provider-vsphere/charts/vsphere-cpi-1.0.0.tgz
-    version: 1.0.0
-generated: "2022-01-20T21:02:52.517483-08:00"
+    - https://kubernetes.github.io/cloud-provider-vsphere/vsphere-cpi-1.22.6.tgz
+    version: 1.22.6
+generated: "2022-03-24T21:52:41.787198-07:00"
diff --git a/charts/vsphere-cpi-1.0.0.tgz b/charts/vsphere-cpi-1.0.0.tgz
diff --git a/charts/vsphere-cpi-1.22.6.tgz b/charts/vsphere-cpi-1.22.6.tgz
diff --git a/charts/vsphere-cpi/Chart.yaml b/charts/vsphere-cpi/Chart.yaml
@@ -1,8 +1,8 @@
 apiVersion: v2
-appVersion: 1.22.5
+appVersion: 1.22.6
 description: A Helm chart for vSphere Cloud Provider Interface Manager (CPI)
 name: vsphere-cpi
-version: 1.0.0
+version: 1.22.6
 keywords:
   - vsphere
   - vmware

diff --git a/charts/vsphere-cpi/values.yaml b/charts/vsphere-cpi/values.yaml
@@ -50,7 +50,7 @@ serviceAccount:
 daemonset:
   annotations: {}
   image: gcr.io/cloud-provider-vsphere/cpi/release/manager
-  tag: v1.22.5
+  tag: v1.22.6
   pullPolicy: IfNotPresent
   dnsPolicy: ClusterFirst
   cmdline:

diff --git a/cluster/images/controller-manager/Dockerfile b/cluster/images/controller-manager/Dockerfile
@@ -33,7 +33,7 @@ ARG DISTROLESS_IMAGE=gcr.io/distroless/static@sha256:9b60270ec0991bc4f14bda475e8
 FROM ${GOLANG_IMAGE} as builder
 
 # This build arg is the version to embed in the CPI binary
-ARG VERSION=1.22.5
+ARG VERSION=1.22.6
 
 # This build arg controls the GOPROXY setting
 ARG GOPROXY

diff --git a/docs/book/tutorials/deploying-cpi-with-k3s.md b/docs/book/tutorials/deploying-cpi-with-k3s.md
@@ -4,7 +4,7 @@ This document is designed to show you how to integrate k3s with cloud provider v
 
 When running with a cloud-controller-manager, it is expected to pass the node provider ID to a CCM as `<provider>://<id>`, in our case, `vsphere://1234567`. However, k3s passes it as `k3s://<hostname>`, which makes vsphere CCM not be able to find the node.
 
-We only support `vsphere` as the provider name that is used for constructing **providerID** for both [vsphere](https://github.com/kubernetes/cloud-provider-vsphere/blob/v1.22.5/pkg/cloudprovider/vsphere/cloud.go#L51) and [vsphere-paravirtual](https://github.com/kubernetes/cloud-provider-vsphere/blob/v1.22.5/pkg/cloudprovider/vsphereparavirtual/cloud.go#L42).
+We only support `vsphere` as the provider name that is used for constructing **providerID** for both [vsphere](https://github.com/kubernetes/cloud-provider-vsphere/blob/v1.22.6/pkg/cloudprovider/vsphere/cloud.go#L51) and [vsphere-paravirtual](https://github.com/kubernetes/cloud-provider-vsphere/blob/v1.22.6/pkg/cloudprovider/vsphereparavirtual/cloud.go#L42).
 
 ## How to integrate k3s with cloud provider vsphere
 
@@ -54,7 +54,7 @@ curl -sfL https://get.k3s.io | K3S_TOKEN=${token} sh -s - agent \
 
 ### Install CCM
 
-Now after k3s server starts we need to install the CCM itself. Simply apply the yaml manifest that matches the CCM version you are using, e.g. for v1.22.5:
+Now after k3s server starts we need to install the CCM itself. Simply apply the yaml manifest that matches the CCM version you are using, e.g. for v1.22.6:
 
 ```shell
 kubectl apply -f releases/v1.22/

diff --git a/docs/book/tutorials/disable-node-deletion.yaml b/docs/book/tutorials/disable-node-deletion.yaml
@@ -234,7 +234,7 @@ spec:
       serviceAccountName: cloud-controller-manager
       containers:
         - name: vsphere-cloud-controller-manager
-          image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.22.5
+          image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.22.6
           args:
             - --cloud-provider=vsphere
             - --v=2

diff --git a/releases/README.md b/releases/README.md
@@ -8,7 +8,7 @@ Note that YAML files from [manifests/controller-manager repo](https://github.com
 
 ## Example workflow
 
-In this tutorial, we will be installing the latest version of cloud provider vsphere(v1.22.5).
+In this tutorial, we will be installing the latest version of cloud provider vsphere(v1.22.6).
 
 ### Step 1: find the kubernetes major version you are using
 

diff --git a/releases/v1.22/vsphere-cloud-controller-manager.yaml b/releases/v1.22/vsphere-cloud-controller-manager.yaml
@@ -234,7 +234,7 @@ spec:
       serviceAccountName: cloud-controller-manager
       containers:
         - name: vsphere-cloud-controller-manager
-          image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.22.5
+          image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.22.6
           args:
             - --cloud-provider=vsphere
             - --v=2