CLOUDP-295785 - add pipeline_main.py extended help

[MaciejKaras]

Summary

Adding more help information for the scripts.release.pipeline_main python script.

Proof of Work

(venv) ➜  mongodb-kubernetes git:(maciejk/use-ar-related-versions) ✗ python3 -m scripts.release.pipeline_main --help
usage: pipeline_main.py [-h] [-b ] [-p ] [-v ] [-r ] [-s] [--parallel] [--parallel-factor ] image

Builder tool for container images. It allows to push and sign images with multiple architectures using Docker Buildx. By default build information is read from 'build_info.json' file in the project root directory based on the build scenario. It can be inferred from the environment variables or overridden with the '--build-scenario' option.

positional arguments:
  image                 Image name to build. Supported images: meko-tests, operator, mco-tests, readiness-probe, upgrade-hook, database, agent, init-appdb, init-database, init-ops-manager, ops-manager

options:
  -h, --help            show this help message and exit
  -b, --build-scenario
                        Override the build scenario instead of inferring from environment. Options: release, patch, staging, development. Default is to infer from environment variables. For 'development' the 'patch' scenario is used to read values from 'build_info.json'
  -p, --platform        Override the platforms instead of resolving from build scenario. Multi-arch builds are comma-separated. Example: linux/amd64,linux/arm64
  -v, --version         Override the version/tag instead of resolving from build scenario. Default is to infer from environment variables based on the selected scenario.
  -r, --registry        Override the base registry instead of resolving from build scenario
  -s, --sign            If set force image signing. Default is to infer from build scenario.
  --parallel            Build agent images in parallel.
  --parallel-factor     Number of agent builds to run in parallel, defaults to number of cores

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.3.0 Release Notes

Bug Fixes

• This change fixes the current complex and difficult-to-maintain architecture for stateful set containers, which relies on an "agent matrix" to map operator and agent versions which led to a sheer amount of images.
• We solve this by shifting to a 3-container setup. This new design eliminates the need for the operator-version/agent-version matrix by adding one additional container containing all required binaries. This architecture maps to what we already do with the mongodb-database container.

Other Changes

• Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
• subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.