Release v1.9.0

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.9.0] - 2024-07-02
+
 ### Changed
 
 - Update vSphere CPI to `1.29` for Kubernetes 1.29 compatibility.
@@ -98,7 +100,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Add upstream CPI chart at 1.22.6
 
-[Unreleased]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.8.0...HEAD
+[Unreleased]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.9.0...HEAD
+[1.9.0]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.8.0...v1.9.0
 [1.8.0]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.7.0...v1.8.0
 [1.7.0]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.6.0...v1.7.0
 [1.6.0]: https://github.com/giantswarm/cloud-provider-vsphere-app/compare/v1.5.1...v1.6.0

helm/cloud-provider-vsphere/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-version: 1.8.0
+version: 1.9.0
 appVersion: 0.0.1
 name: cloud-provider-vsphere
 description: A Helm chart for cloud-provider-vsphere with CPI and CSI

helm/cloud-provider-vsphere/charts/cloud-provider-for-vsphere/values.yaml

@@ -12,39 +12,45 @@ config:
   region: "k8s-region"
   zone: "k8s-zone"
   thumbprint: ""
+
   secret:
     # Specifies whether Secret should be created from config values
     create: true
     # The name of the Secret referred to in the vsphere-cloud-config ConfigMap
     # If your Kubernetes platform provides this secret, set create to false and adjust the secret name
     name: vsphere-cloud-secret
+
 ## Specify if a Pod Security Policy for kube-state-metrics must be created
 ## Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/
 podSecurityPolicy:
   enabled: false
   annotations: {}
-  # Specify pod annotations
-  # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#apparmor
-  # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#seccomp
-  # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#sysctl
-  #
-  # seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*'
-  # seccomp.security.alpha.kubernetes.io/defaultProfileName: 'docker/default'
-  # apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default'
+    # Specify pod annotations
+    # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#apparmor
+    # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#seccomp
+    # Ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#sysctl
+    #
+    # seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*'
+    # seccomp.security.alpha.kubernetes.io/defaultProfileName: 'docker/default'
+    # apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default'
+
 # Run containers to have security context. Default is 'nobody' (65534/65534) in distroless
 securityContext:
   enabled: true
   runAsUser: 1001
   fsGroup: 1001
+
 # RBAC configuration
 rbac:
   # Specifies whether RBAC resources should be created
   create: true
+
 serviceAccount:
   # Specifies whether a ServiceAccount should be created
   create: true
   # The name of the ServiceAccount to use.
   name: cloud-controller-manager
+
 # Daemonset configuration
 daemonset:
   annotations: {}
@@ -61,12 +67,12 @@ daemonset:
     additionalParams: {}
   replicaCount: 1
   resources: {}
-  # limits:
-  #   cpu: 500m
-  #   memory: 512Mi
-  # requests:
-  #    cpu: 256m
-  #    memory: 128Mi
+    # limits:
+    #   cpu: 500m
+    #   memory: 512Mi
+    # requests:
+    #    cpu: 256m
+    #    memory: 128Mi
   podAnnotations: {}
   ## Additional pod labels
   ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/