[CLOUDP-352579] Add evergreen function to promote and release kubectl plugin

[viveksinghggits]

Summary

As part of the efforts of atomic releases we would like to build the binary in dev/staging workflows and then would like to promote those binaries while releasing the product.
The build/push of kubectl plugin binary to dev/staging workflow has been complete successfully as part of the PR, but the promotion was still pending. This PR makes sure that the plugin that is uploaded to the staging bucket, is promoted to the release at the time of MCK release.

Proof of Work

Build the binary in staging workflow so that we can test the promotion process. The provided operator version is respective commit for the MCK tag 1.4.0

evergreen patch --path .evergreen.yml -p mongodb-kubernetes -v init_test_run -t build_test_image -f -y -u --browse -d "Build tests image to test kubectl push, staging scenario" --param BUILD_SCENARIO=staging --param OPERATOR_VERSION=78538991c
Banner: The AWS outage is getting better and tasks and hosts are starting to come back up.
Patch successfully created.

         ID : 68f7a99022f3b600070510b5
    Project : mongodb-kubernetes
    Created : 2025-10-21 15:41:06.232 +0000 UTC
Description : Build tests image to test kubectl push, staging scenario
      Build : https://evergreen.mongodb.com/version/68f7a99022f3b600070510b5?redirect_spruce_users=true
     Status : created

Job was successful and the artifacts were uploaded to the staging bucket

aws s3 ls s3://mongodb-kubernetes-staging/kubectl-mongodb/78538991c/dist/
                           PRE kubectl-mongodb_darwin_amd64_v1/
                           PRE kubectl-mongodb_darwin_arm64/
                           PRE kubectl-mongodb_linux_amd64_v1/
                           PRE kubectl-mongodb_linux_arm64/
                           PRE kubectl-mongodb_linux_ppc64le/
                           PRE kubectl-mongodb_linux_s390x/

test release of kubectl plugin

Running this command is not required while release, it will automatically be run when we create and push tag in github. To test this we just updated the repo and the github token so that the assets can be uploaded to my personal repo.

evergreen patch --path .evergreen.yml -p mongodb-kubernetes -v release_kubectl_mongodb_plugin -t release_kubectl_mongodb_plugin -f -y -u --browse -d "Test promotion of kubectl plugin" --param OPERATOR_VERSION=1.4.0
Banner: The AWS outage is getting better and tasks and hosts are starting to come back up.
Patch successfully created.

         ID : 68f7ac0bb1224400073a3565
    Project : mongodb-kubernetes
    Created : 2025-10-21 15:51:40.875 +0000 UTC
Description : Test promotion of kubectl plugin
      Build : https://evergreen.mongodb.com/version/68f7ac0bb1224400073a3565?redirect_spruce_users=true
     Status : created

The job would figure out the commit for the version 1.4.0 and then would copy the artifacts from staging from that version.
Job was completed successfully and we can see the artifacts in the release bucket

aws s3 ls s3://mongodb-kubernetes-release/kubectl-mongodb/1.4.0/
2025-10-21 18:01:20        646 checksums.txt
2025-10-21 18:01:13   13205230 kubectl-mongodb_1.4.0_darwin_amd64.tar.gz
2025-10-21 18:01:15   11883679 kubectl-mongodb_1.4.0_darwin_arm64.tar.gz
2025-10-21 18:01:16   12579581 kubectl-mongodb_1.4.0_linux_amd64.tar.gz
2025-10-21 18:01:17   11271962 kubectl-mongodb_1.4.0_linux_arm64.tar.gz
2025-10-21 18:01:18   11018193 kubectl-mongodb_1.4.0_linux_ppc64le.tar.gz
2025-10-21 18:01:19   12284864 kubectl-mongodb_1.4.0_linux_s390x.tar.gz

and the assets were uploaded to github release

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.6.0 Release Notes

New Features

• MongoDBCommunity: Added support to configure custom cluster domain via newly introduced spec.clusterDomain resource field. If spec.clusterDomain is not set, environment variable CLUSTER_DOMAIN is used as cluster domain. If the environment variable CLUSTER_DOMAIN is also not set, operator falls back to cluster.local as default cluster domain.
• Helm Chart: Introduced two new helm fields operator.podSecurityContext and operator.securityContext that can be used to configure securityContext for Operator deployment through Helm Chart.

Bug Fixes

• Fixed parsing of the customEnvVars Helm value when values contain = characters.

[MaciejKaras]

instead of hardcoding the platforms to download from staging use platforms in build_info

[viveksinghggits]

We have decided that we are going to work on this, after we stop building plugin binary using goreleaser.