Skip to content

Release of MCK 1.3.0
Compare
Choose a tag to compare
@mongodb-kubernetes-gh-app mongodb-kubernetes-gh-app released this 08 Sep 10:57
· 49 commits to master since this release
1.3.0
1d28c2c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

MCK 1.3.0 Release Notes

New Features

Multi-Architecture Support

The Kubernetes Operator now supports deployment on multiple CPU architectures, allowing for greater flexibility in your environment. Current supported architectures:

  • ARM64 (arm64)
  • IBM Power (ppc64le)
  • IBM Z (s390x)
  • Intel/AMD (x86_64) (existing)

Affected Components: Multi-architecture support has been enabled for all core container images, including the operator, agent, init containers, database, and readiness probe. The container runtime will automatically pull the correct image for your node's architecture.

Important Limitation: Please note that Ops Manager and the init-ops-manager image are not included in this update.

Important Changes Related to the MongoDB Agent Images

We're deprecating quay.io/mongodb/mongodb-agent-ubi repository in favor of quay.io/mongodb/mongodb-agent. Please note:

  • Default urls in the helm chart contains the new repo.
    • If you don't customize those url, you don't need to change anything.
    • If you do please migrate to the new mongodb-agent.
  • The new mongodb-agent contains multi-arch images, while the deprecated one does not.
  • mongodb-agent-ubi is kept only for backwards compatibility, please do not use it anymore.

Bug Fixes

  • We've fixed 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.
  • For static containers: We've shifted to a 3-container setup (database, agent, utilities-holder). 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.
  • Fixed an issue where the readiness probe reported the node as ready even when its authentication mechanism was not in sync with the other nodes, potentially causing premature restarts.
  • Fixed an issue where the MongoDB Agents did not adhere to the NO_PROXY environment variable configured on the operator.
  • Changed webhook ClusterRole and ClusterRoleBinding default names to include the namespace. This ensures that multiple operator installations in different namespaces don't conflict with each other.

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.
  • We have deliberately not published the container images for OpsManager versions 7.0.16, 8.0.8, 8.0.9 and 8.0.10 due to a bug in the OpsManager which prevents MCK customers to upgrade their OpsManager deployments to those versions.
Assets 7
Loading