MongoDB Kubernetes Operator
MongoDB Kubernetes Operator 0.8.0
Kubernetes Operator
-
Changes
- The Operator now uses the official MongoDB Community Server images.
It is still possible to use the Docker Inc. images by altering the JSON configuration file:Alternatively, it is possible to the Operator environmental variables to:mongodb_image_name=mongo mongodb_image_repo_url=docker.ioThe upgrade process for the official MongoDB images is automatic when using the default settings provided by both,MONGODB_IMAGE=mongo MONGODB_REPO_URL=docker.io
kubectl and Helm
operator installation methods. Once the Operator boots up, it will replaceimagetags in the StatefulSets. If however,
you're using customized deployments (by modifyingMONGODB_IMAGEorMONGODB_REPO_URLenvironment variable in the Operator
Deployment), please check if your settings are correct and if they are pointing to the right coordinates. The Operator
still provides basic backwards compatibility with previous images (docker.io/mongo).
- The Operator now uses the official MongoDB Community Server images.
-
mongodb-readiness-hookandmongodb-version-upgrade-hookimages are now rebuilt daily, incorporating updates to system packages and security fixes. The binaries are built only once during the release process and used without changes in daily rebuilt
Updated Image Tags
- mongodb-kubernetes-operator:0.8.0
- mongodb-agent:12.0.21.7698-1
- mongodb-kubernetes-readinessprobe:1.0.14
- mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.7
All the images can be found in:
https://quay.io/mongodb
https://hub.docker.com/r/mongodb/mongodb-community-server