Bump kubernetes-sigs/cluster-api-provider-vsphere to latest release

abhay-krishna · Dec 1, 2023 · a794e8f · a794e8f
1 parent 91ce512
commit a794e8f
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/UPSTREAM_PROJECTS.yaml b/UPSTREAM_PROJECTS.yaml
@@ -189,8 +189,8 @@ projects:
             go_version: "1.19"
       - name: cluster-api-provider-vsphere
         versions:
-          - tag: v1.7.4
-            go_version: "1.19"
+          - tag: v1.8.4
+            go_version: "1.20"
       - name: cri-tools
         versions:
           - tag: v1.28.0

diff --git a/projects/kubernetes-sigs/cluster-api-provider-vsphere/GIT_TAG b/projects/kubernetes-sigs/cluster-api-provider-vsphere/GIT_TAG
@@ -1 +1 @@
-v1.7.4
+v1.8.4
diff --git a/projects/kubernetes-sigs/cluster-api-provider-vsphere/GOLANG_VERSION b/projects/kubernetes-sigs/cluster-api-provider-vsphere/GOLANG_VERSION
@@ -1 +1 @@
-1.19
+1.20
diff --git a/projects/kubernetes-sigs/cluster-api-provider-vsphere/README.md b/projects/kubernetes-sigs/cluster-api-provider-vsphere/README.md
@@ -1,5 +1,5 @@
 ## **Cluster API Provider for vSphere**
-![Version](https://img.shields.io/badge/version-v1.7.4-blue)
+![Version](https://img.shields.io/badge/version-v1.8.4-blue)
 ![Build Status](https://codebuild.us-west-2.amazonaws.com/badges?uuid=eyJlbmNyeXB0ZWREYXRhIjoiYm85WnJ4aDc2ZXhhVUxOWHJuUFJwN3FlQmE2L1Q4b2ZzNG91OVpjNVNGM1ZvbVBEUUM2bkdER3N5eVNrWTBKS2VSSW9Oa051aFVWS1dzVVlTOHBBZ0NRPSIsIml2UGFyYW1ldGVyU3BlYyI6IlEwOWNtd0llNXdjUGRvQWkiLCJtYXRlcmlhbFNldFNlcmlhbCI6MX0%3D&branch=main)
 
 The [Cluster API Provider for vSphere (CAPV)](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere) is a a concrete implementation of Cluster API for vSphere, which paves the way for true vSphere hybrid deployments of Kubernetes. CAPV is designed to allow customers to use their existing vSphere infrastructure, including vCenter credentials, VMs, templates, etc. for bootstrapping and creating workload clusters.
@@ -32,7 +32,7 @@ You can find the latest version of this image [on ECR Public Gallery](https://ga
    1. Run `git format-patch <commit>`, where `<commit>` is the last upstream commit on that tag. Move the generated patches under the patches/ folder in this repo.
 1. Update the `GIT_TAG` file to have the new desired version based on the upstream release tags.
 1. Compare the old tag to the new, looking specifically for Makefile changes.
-   ex: [1.7.0 compared to 1.7.4](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/compare/v1.7.0...v1.7.4). Check if the [manifest-modification](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L568) or [release-manifests](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L577C9-L577C26)
+   ex: [1.7.0 compared to 1.7.4](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/compare/v1.7.0...v1.8.4). Check if the [manifest-modification](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L568) or [release-manifests](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L577C9-L577C26)
    targets have changed in the Makefile, and make the required changes in create_manifests.sh
 1. Check the go.mod file to see if the golang version has changed when updating a version. Update the field `GOLANG_VERSION` in
    Makefile to match the version upstream.