diff --git a/charts/vsphere-cpi-1.23.2.tgz b/charts/vsphere-cpi-1.23.2.tgz new file mode 100644 index 000000000..4029acd7b Binary files /dev/null and b/charts/vsphere-cpi-1.23.2.tgz differ diff --git a/charts/vsphere-cpi/Chart.yaml b/charts/vsphere-cpi/Chart.yaml index c17c26dd6..4911f8b65 100644 --- a/charts/vsphere-cpi/Chart.yaml +++ b/charts/vsphere-cpi/Chart.yaml @@ -1,8 +1,8 @@ apiVersion: v2 -appVersion: 1.23.1 +appVersion: 1.23.2 description: A Helm chart for vSphere Cloud Provider Interface Manager (CPI) name: vsphere-cpi -version: 1.23.1 +version: 1.23.2 keywords: - vsphere - vmware diff --git a/charts/vsphere-cpi/values.yaml b/charts/vsphere-cpi/values.yaml index 941d13513..50af069c7 100644 --- a/charts/vsphere-cpi/values.yaml +++ b/charts/vsphere-cpi/values.yaml @@ -58,7 +58,7 @@ serviceAccount: daemonset: annotations: {} image: gcr.io/cloud-provider-vsphere/cpi/release/manager - tag: v1.23.1 + tag: v1.23.2 pullPolicy: IfNotPresent dnsPolicy: ClusterFirst cmdline: diff --git a/cluster/images/controller-manager/Dockerfile b/cluster/images/controller-manager/Dockerfile index b94cfcf1e..09fcfc22a 100644 --- 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.23.1 +ARG VERSION=1.23.2 # 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 index df2c87792..430f3a79d 100644 --- 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 `://`, in our case, `vsphere://1234567`. However, k3s passes it as `k3s://`, 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.23.1/pkg/cloudprovider/vsphere/cloud.go#L51) and [vsphere-paravirtual](https://github.com/kubernetes/cloud-provider-vsphere/blob/1.23.1/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.23.2/pkg/cloudprovider/vsphere/cloud.go#L51) and [vsphere-paravirtual](https://github.com/kubernetes/cloud-provider-vsphere/blob/1.23.2/pkg/cloudprovider/vsphereparavirtual/cloud.go#L42). ## How to integrate k3s with cloud provider vsphere diff --git a/docs/book/tutorials/disable-node-deletion.yaml b/docs/book/tutorials/disable-node-deletion.yaml index 8800ff252..bf087b929 100644 --- a/docs/book/tutorials/disable-node-deletion.yaml +++ b/docs/book/tutorials/disable-node-deletion.yaml @@ -233,7 +233,7 @@ spec: priorityClassName: system-node-critical containers: - name: vsphere-cloud-controller-manager - image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.1 + image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.2 args: - --cloud-provider=vsphere - --v=2 diff --git a/index.yaml b/index.yaml index dda874886..475118030 100644 --- a/index.yaml +++ b/index.yaml @@ -1,11 +1,30 @@ apiVersion: v1 entries: vsphere-cpi: + - apiVersion: v2 + appVersion: 1.23.2 + created: "2022-09-23T15:23:21.44503-07:00" + description: A Helm chart for vSphere Cloud Provider Interface Manager (CPI) + digest: 883ec295a07ac932009179801748668090e915d1f88d1bf001337d7ab463100e + home: https://github.com/kubernetes/cloud-provider-vsphere + icon: https://raw.githubusercontent.com/kubernetes/cloud-provider-vsphere/master/docs/vmware_logo.png + keywords: + - vsphere + - vmware + - cloud + - provider + - cpi + name: vsphere-cpi + sources: + - https://github.com/kubernetes/cloud-provider-vsphere + urls: + - https://kubernetes.github.io/cloud-provider-vsphere/charts/vsphere-cpi-1.23.2.tgz + version: 1.23.2 - apiVersion: v2 appVersion: 1.23.1 - created: "2022-06-21T19:13:09.56809-07:00" + created: "2022-09-23T15:23:21.443879-07:00" description: A Helm chart for vSphere Cloud Provider Interface Manager (CPI) - digest: 43075cb997fe0e9f686b34625ec36963027180c3cb02b74c519bc08e1c3d8cd7 + digest: ec70834e13c37ab0080ddbad05f6b1ba80da097a32ee1a61e7ba19428276b54a home: https://github.com/kubernetes/cloud-provider-vsphere icon: https://raw.githubusercontent.com/kubernetes/cloud-provider-vsphere/master/docs/vmware_logo.png keywords: @@ -20,4 +39,4 @@ entries: urls: - https://kubernetes.github.io/cloud-provider-vsphere/charts/vsphere-cpi-1.23.1.tgz version: 1.23.1 -generated: "2022-06-21T19:13:09.567059-07:00" +generated: "2022-09-23T15:23:21.442397-07:00" diff --git a/releases/README.md b/releases/README.md index 63207fe4a..8ca48dc63 100644 --- 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.23.1) freshly. If you have an older version of CPI already installed, the steps to deploy and upgrade CPI stay the same. With our `RollingUpdate` update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically. +In this tutorial, we will be installing the latest version of cloud provider vsphere(v1.23.2) freshly. If you have an older version of CPI already installed, the steps to deploy and upgrade CPI stay the same. With our `RollingUpdate` update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically. ### Step 1: find the kubernetes major version you are using diff --git a/releases/v1.23/vsphere-cloud-controller-manager.yaml b/releases/v1.23/vsphere-cloud-controller-manager.yaml index 2381e2dbd..729b44477 100644 --- a/releases/v1.23/vsphere-cloud-controller-manager.yaml +++ b/releases/v1.23/vsphere-cloud-controller-manager.yaml @@ -233,7 +233,7 @@ spec: priorityClassName: system-node-critical containers: - name: vsphere-cloud-controller-manager - image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.1 + image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.2 args: - --cloud-provider=vsphere - --v=2