Prepare Release 2.5.1

charts/opensearch-cluster/Chart.yaml

@@ -2,5 +2,5 @@ apiVersion: v2
 name: opensearch-cluster
 description: A Helm chart for OpenSearch Cluster
 type: application
-version: 2.5.0
-appVersion: 2.5.0
+version: 2.5.1
+appVersion: 2.5.1

charts/opensearch-operator/Chart.yaml

@@ -15,10 +15,10 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 2.5.0
+version: 2.5.1
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 2.5.0
+appVersion: 2.5.1

charts/opensearch-operator/values.yaml

@@ -41,7 +41,7 @@ manager:
   parallelRecoveryEnabled: true
 
   image:
-    repository: public.ecr.aws/opensearch-project/opensearch-operator
+    repository: opensearchproject/opensearch-operator
     ## tag default uses appVersion from Chart.yaml, to override specify tag tag: "v1.1"
     tag: ""
     pullPolicy: "Always"

docs/designs/crd.md

@@ -559,7 +559,7 @@ InitHelperConfig defines global Opensearch InitHelper image configuration
         <td>string</td>
         <td>Define InitHelper image</td>
         <td>false</td>
-        <td>public.ecr.aws/opensearch-project/opensearch-operator-busybox</td>
+        <td>docker.io/busybox</td>
       </tr><tr>
       </tr><tr>
         <td><b>imagePullPolicy</b></td>

docs/userguide/main.md

@@ -767,7 +767,7 @@ manager:
 
 ### Custom init helper
 
-During cluster initialization the operator uses init containers as helpers. For these containers a busybox image is used ( specifically `public.ecr.aws/opensearch-project/busybox:latest`). In case you are working in an offline environment and the cluster cannot access the registry or you want to customize the image, you can override the image used by specifying the `initHelper` image in your cluster spec:
+During cluster initialization the operator uses init containers as helpers. For these containers a busybox image is used ( specifically `docker.io/busybox:latest`). In case you are working in an offline environment and the cluster cannot access the registry or you want to customize the image, you can override the image used by specifying the `initHelper` image in your cluster spec:
 
 ```yaml
   spec:     

jenkins/release.jenkinsfile

@@ -120,7 +120,8 @@ pipeline {
                                 string(name: 'RELEASE_VERSION', value: "${OPERATOR_VERSION}"),
                                 booleanParam(name: 'DOCKER_HUB_PROMOTE', value: true),
                                 booleanParam(name: 'ECR_PROMOTE', value: true),
-                                booleanParam(name: 'TAG_LATEST', value: true)
+                                booleanParam(name: 'TAG_LATEST', value: true),
+                                booleanParam(name: 'TAG_MAJOR_VERSION', value: false)
                             ]
                     }
                 }