Change operator version to 24.4.0-0 (#950)

Automated changes by pre-release.yml GitHub action

---------

Signed-off-by: GitHub <noreply@github.com>
Co-authored-by: cchen-vertica <cchen-vertica@users.noreply.github.com>
Co-authored-by: cchen-vertica <cchen8@opentext.com>

Author: github-actions[bot]

Makefile

@@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 2.2.0
+VERSION ?= 24.4.0-0
 export VERSION
 
 # VLOGGER_VERSION defines the version to use for the Vertica logger image

helm-charts/verticadb-operator/Chart.yaml

@@ -15,4 +15,4 @@ name: verticadb-operator
 description: An operator that can deploy and manage Vertica clusters
 type: application
 # Versions follow Semantic Versioning (https://semver.org/)
-version: 2.2.0
+version: 24.4.0-0

helm-charts/verticadb-operator/README.md

@@ -5,7 +5,7 @@ This helm chart will install the operator and an admission controller webhook.
 | affinity | The [affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) parameter allows you to constrain the operator pod only to specific nodes. If this parameter is not set, then no affinity setting is used with the operator pod. | Not set |
 | controllers.enable | This controls if controllers are enabled when running the operator. The controllers are the part of the operator that watches and acts on custom resources. This option is useful if you want to deploy the operator just as a webhook. This comes in handy when deploying the operator as the namespace scope | true |
 | controllers.scope | Defines the scope of the operator. You can define one of two values: cluster or namespace.<br><br>When set to cluster, the operator is cluster scoped. This means it will watch for changes to any custom resource across all namespaces. This is the default deployment.<br><br>When set to namespace, the operator is cluster scope. The operator will only set up watches for the namespace it is deployed in. You can deploy the operator in multiple namespaces this way. However, the webhook can only be run once in the cluster. You can control running of the webhook with the webhook.enable option. | cluster |
-| image.name | The name of image that runs the operator. | opentext/verticadb-operator:2.2.0 |
+| image.name | The name of image that runs the operator. | opentext/verticadb-operator:24.4.0-0 |
 | image.repo | Repo server hosting image.name | docker.io |
 | image.pullPolicy | The pull policy for the image that runs the operator  | IfNotPresent |
 | imagePullSecrets | List of Secret names containing login credentials for above repos | null (pull images anonymously) |

helm-charts/verticadb-operator/values.yaml

@@ -26,7 +26,7 @@
 
 image:
   repo: docker.io
-  name: opentext/verticadb-operator:2.2.0
+  name: opentext/verticadb-operator:24.4.0-0
   pullPolicy: IfNotPresent
 
 rbac_proxy_image:

pkg/meta/labels.go

@@ -45,7 +45,7 @@ const (
 	// the pod spec template. Rather it is set in the pod by a reconciler after
 	// the pod was created.
 	OperatorVersionLabel = "app.kubernetes.io/version"
-	CurOperatorVersion   = "2.2.0" // The version number of the operator
+	CurOperatorVersion   = "24.4.0-0" // The version number of the operator
 	// If any of the operator versions are used in the code, add a const here.
 	// But it isn't necessary to create a const for each version.
 	OperatorVersion100 = "1.0.0"