CLOUDP-295785 - re-add release tasks for readiness-probe and version-upgrade-hook (#463)

# Summary

This PR is re-adding release tasks for `readinessprobe` and
`version-upgrade-post-start-hook`. It is also bumping `readinessprobe`
to `1.0.23` and `version-upgrade-post-start-hook` to `1.0.10`. Next time
when we are going to release the operator the `readinessprobe` and
`version-upgrade-post-start-hook` are also going to be released, if the
version was incremented. The new `skip-if-exists` flag in
`build_info.json` makes sure we don't overwrite the tag if it already
exists.

The pre-commit hook was run to update the `readinessprobe` to `1.0.23`
and `version-upgrade-post-start-hook` to `1.0.10`. This was based only
on updating `release.json` respective values and running pre-commit
script updated logic.

The `mongodb-community-operator/conifg/` directory contained unused
.yaml files that were also referencing `readinessprobe` and
`version-upgrade-post-start-hook` - those I deleted. The
`mongodb-community-operator/conifg/samples/` were moved to
`public/samples/community/`.

## Proof of Work

Triggered release job ->
https://spruce.mongodb.com/version/68ca8a70f93aab0007c723d3/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

...which pushes them to quay with `-rc` suffix:
-
`quay.io/mongodb/mongodb-<REDACTED:macos_notary_keyid>-version-upgrade-post-start-hook:1.0.10-rc@sha256:082df2395b5a8ee4c89053a098b8b7b021b0cc5313d2090a2048e29aa13ffaea`
-
`quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.23-rc@sha256:85c0257d3f63921509878543db8aa91f53cdee1db8ce5e380984da60b9642dae`

In the subsequent
[run](https://spruce.mongodb.com/version/68cac45d8e609100074a86be/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC)
the images were skipped as expected:
```
[2025/09/17 16:27:33.509] INFO     2025-09-17 14:27:33,509 [atomic_pipeline]  Image with tag quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.23-rc already exists. Skipping it.
[2025/09/17 16:27:33.509] INFO     2025-09-17 14:27:33,509 [atomic_pipeline]  All specified image tags already exist. Skipping build.
```

## Checklist

- [x] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you added changelog file?
    - use `skip-changelog` label if not needed
- refer to [Changelog files and Release
Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes)
section in CONTRIBUTING.md for more details

Author: MaciejKaras

.evergreen-functions.yml

@@ -46,6 +46,8 @@ variables:
       - RELEASE_INITIAL_VERSION
       - RELEASE_INITIAL_COMMIT_SHA
       - OPERATOR_VERSION
+      - READINESS_PROBE_VERSION
+      - VERSION_UPGRADE_HOOK_VERSION
       - BUILD_SCENARIO
 
 functions:

.evergreen-release.yml

@@ -70,6 +70,24 @@ tasks:
         vars:
           IMAGE_NAME: database
 
+  - name: release_readiness_probe
+    tags: [ "image_release" ]
+    allowed_requesters: [ "patch", "github_tag" ]
+    commands:
+      - func: clone
+      - func: setup_building_host
+      - func: quay_login
+      - func: pipeline_readiness_probe
+
+  - name: release_version_upgrade_hook
+    tags: [ "image_release" ]
+    allowed_requesters: [ "patch", "github_tag" ]
+    commands:
+      - func: clone
+      - func: setup_building_host
+      - func: quay_login
+      - func: pipeline_version_upgrade_hook
+
   - name: prepare_and_upload_openshift_bundles
     tags: [ "openshift_bundles" ]
     allowed_requesters: [ "patch", "github_tag" ]
@@ -121,6 +139,8 @@ buildvariants:
       - name: release_init_database
       - name: release_init_ops_manager
       - name: release_database
+      - name: release_readiness_probe
+      - name: release_version_upgrade_hook
 
   - name: preflight_release_images
     display_name: preflight_release_images

build_info.json

@@ -221,6 +221,7 @@
       "release": {
         "sign": true,
         "olm-tag": true,
+        "skip-if-exists": true,
         "repositories": [
           "quay.io/mongodb/mongodb-kubernetes-readinessprobe"
         ],
@@ -250,6 +251,7 @@
       "release": {
         "sign": true,
         "olm-tag": true,
+        "skip-if-exists": true,
         "repositories": ["quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook"],
         "platforms": [
           "linux/arm64",

config/manager/manager.yaml

@@ -112,9 +112,9 @@ spec:
             - name: MDB_COMMUNITY_AGENT_IMAGE
               value: "quay.io/mongodb/mongodb-agent:108.0.2.8729-1"
             - name: VERSION_UPGRADE_HOOK_IMAGE
-              value: "quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.9"
+              value: "quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.10"
             - name: READINESS_PROBE_IMAGE
-              value: "quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.22"
+              value: "quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.23"
             - name: MDB_COMMUNITY_IMAGE
               value: "mongodb-community-server"
             - name: MDB_COMMUNITY_REPO_URL

helm_chart/values.yaml

@@ -149,10 +149,10 @@ agent:
 # This is only used by the MongoDBCommunity resource reconciler - START
 versionUpgradeHook:
   name: mongodb-kubernetes-operator-version-upgrade-post-start-hook
-  version: 1.0.9
+  version: 1.0.10
 readinessProbe:
   name: mongodb-kubernetes-readinessprobe
-  version: 1.0.22
+  version: 1.0.23
 # This is only used by the MongoDBCommunity resource reconciler - END
 
 # This is used by AppDB and by static containers to determine the image that the operator uses for databases.