Skip to content

MongoDB Kubernetes Operator
Compare
Choose a tag to compare
@github-actions github-actions released this 09 Mar 12:21
v0.7.3
4660b6e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

MongoDB Kubernetes Operator 0.7.3

Upgrade breaking change notice

Versions 0.7.3, 0.7.4 have an issue that breaks deployment of MongoDB replica set when:

  • TLS is enabled
  • Replica set was deployed using the operator with version <=0.7.2

If above conditions are met, it is strongly advised to upgrade the MongoDB Kubernetes Operator to version 0.7.5 or higher.

Kubernetes Operator

  • Changes
    • The Operator can correctly scale arbiters up and down. When arbiters are
      enabled (this is, when spec.arbiters > 0), a new StatefulSet will be
      created to hold the Pods that will act as arbiters. The new StatefulSet will
      be named <mongodb-resource>-arb.
    • Add support for exposing Prometheus metrics from the ReplicaSet
  • Bug fixes
    • The operator will watch for changes in the referenced CA certificates as well as server certificates

MongoDBCommunity Resource

  • Changes
    • Exposing Prometheus metrics is now possible by configuring spec.prometheus.

Updated Image Tags

  • mongodb-kubernetes-operator:0.7.3
  • mongodb-agent:11.12.0.7388-1
  • mongodb-kubernetes-readinessprobe:1.0.8
  • mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.4

All the images can be found in:

https://quay.io/mongodb

Assets 2