From f087637f64f12e76d8c4f5a25a2bfcc44e518ca0 Mon Sep 17 00:00:00 2001 From: lubronzhan Date: Thu, 8 Dec 2022 09:58:52 -0800 Subject: [PATCH] Release 1.23.3 --- cluster/images/controller-manager/Dockerfile | 2 +- docs/book/tutorials/deploying-cpi-with-k3s.md | 2 +- docs/book/tutorials/disable-node-deletion.yaml | 2 +- releases/README.md | 2 +- releases/v1.23/vsphere-cloud-controller-manager.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/cluster/images/controller-manager/Dockerfile b/cluster/images/controller-manager/Dockerfile index 09fcfc22a..84c275aeb 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.2 +ARG VERSION=1.23.3 # 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 430f3a79d..aba2ab4c1 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.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). +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.3/pkg/cloudprovider/vsphere/cloud.go#L51) and [vsphere-paravirtual](https://github.com/kubernetes/cloud-provider-vsphere/blob/1.23.3/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 bf087b929..18743df5e 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.2 + image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.3 args: - --cloud-provider=vsphere - --v=2 diff --git a/releases/README.md b/releases/README.md index 8ca48dc63..79d5b1d1f 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.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. +In this tutorial, we will be installing the latest version of cloud provider vsphere(v1.23.3) 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 729b44477..87ddb31ce 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.2 + image: gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.23.3 args: - --cloud-provider=vsphere - --v=2