Skip to content
logo
Percona Operator for MongoDB
Percona Distribution for MongoDB Operator 1.9.0 (2021-07-29)
Initializing search
    percona/k8spsmdb-docs
    percona/k8spsmdb-docs
    • Welcome
      • Design and architecture
      • Comparison with other solutions
      • Install with Helm
      • Install with kubectl
      • System requirements
      • Install on Minikube
      • Install on Google Kubernetes Engine (GKE)
      • Install on Amazon Elastic Kubernetes Service (AWS EKS)
      • Install on Microsoft Azure Kubernetes Service (AKS)
      • Generic Kubernetes installation
      • Install on OpenShift
      • Application and system users
      • Changing MongoDB options
      • Anti-affinity and tolerations
      • Labels and annotations
      • Exposing the cluster
      • Local storage support
      • Arbiter and non-voting nodes
      • MongoDB sharding
      • Transport encryption (TLS/SSL)
      • Data at rest encryption
      • Telemetry
        • About backups
        • Configure storage for backups
        • Making scheduled backups
        • Making on-demand backup
        • Storing operations logs for point-in-time recovery
        • Restore from a previously saved backup
        • Delete the unneeded backup
      • Upgrade MongoDB and the Operator
      • Horizontal and vertical scaling
      • Multi-cluster and multi-region deployment
      • Monitor with Percona Monitoring and Management (PMM)
      • Add sidecar containers
      • Restart or pause the cluster
      • Initial troubleshooting
      • Exec into the container
      • Check the logs
      • Special debug images
      • OpenLDAP integration
      • How to use private registry
      • Creating a private S3-compatible cloud for backups
      • Restore backup to a new Kubernetes-based environment
      • How to use backups to move the external database to Kubernetes
      • Install Percona Server for MongoDB in multi-namespace (cluster-wide) mode
      • Upgrade Percona Server for MongoDB manually
      • Monitor Kubernetes
      • Custom Resource options
      • Percona certified images
      • Operator API
      • Frequently asked questions
      • Old releases (documentation archive)
      • Copyright and licensing information
      • Trademark policy
      • Release notes index
      • Percona Operator for MongoDB 1.14.0 (2023-03-13)
      • Percona Operator for MongoDB 1.13.0 (2022-09-15)
      • Percona Operator for MongoDB 1.12.0 (2022-05-05)
      • Percona Distribution for MongoDB Operator 1.11.0 (2021-12-21)
      • Percona Distribution for MongoDB Operator 1.10.0 (2021-09-30)
      • Percona Distribution for MongoDB Operator 1.9.0 (2021-07-29)
        • Release Highlights
        • New Features
        • Improvements
        • Bugs Fixed
        • Deprecation and Removal
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.8.0 (2021-05-06)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.7.0 (2021-03-08)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.6.0 (2020-12-22)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.5.0 (2020-09-07)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.4.0 (2020-03-31)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.3.0 (2019-12-11)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.2.0 (2019-09-20)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.1.0 (2019-07-15)
      • Percona Kubernetes Operator for Percona Server for MongoDB 1.0.0 (2019-05-29)

    • Release Highlights
    • New Features
    • Improvements
    • Bugs Fixed
    • Deprecation and Removal

    Percona Distribution for MongoDB Operator 1.9.0¶

    • Date

      June 29, 2021

    • Installation

      For installation please refer to the documentation page

    Release Highlights¶

    • Starting from this release, the Operator changes its official name to Percona Distribution for MongoDB Operator. This new name emphasizes graduate changes which incorporated a collection of Percona’s solutions to run and operate MongoDB Server, available separately as Percona Distribution for MongoDB.

    • It is now possible to restore backups from S3-compatible storage to a new Kubernetes-based environment with no existing Backup Custom Resources

    • You can now customize Percona Server for MongoDB by storing custom configuration for Replica Set, mongos, and Config Server instances in ConfigMaps or in Secrets

    New Features¶

    • K8SPSMDB-276: Restore backups to a new Kubernetes-based environment with no existing Backup Custom Resource

    • K8SPSMDB-444, K8SPSMDB-445: Allow storing custom configuration in ConfigMaps and Secrets

    Improvements¶

    • K8SPSMDB-365: Unblock backups even if just a single Replica Set node is available by setting allowUnsafeConfigurations flag to true

    • K8SPSMDB-453: It is now possible to see the overall progress of the provisioning of MongoDB cluster resources and dependent components in Custom Resource status

    • K8SPSMDB-451, K8SPSMDB-398: MongoDB cluster resource statuses in Custom Resource output (e.g. returned by kubectl get psmdb command) have been improved and now provide more precise reporting

    • K8SPSMDB-425: Remove mongos.expose.enabled option from Custom Resource and always expose mongos (with the ClusterIP exposeType by default)

    • K8SPSMDB-421: Secret object containing system users passwords is now deleted along with the Cluster if delete-psmdb-pvc finalizer is enabled

    • K8SPSMDB-411: Added options to specify custom memory and CPU requirements for Arbiter instances

    • K8SPSMDB-329: Reduced the number of various etcd and k8s object updates from the operator to minimize the pressure on the Kubernetes cluster

    Bugs Fixed¶

    • K8SPSMDB-437: Fixed a bug where Labels were not set on Persistent Volume Claim objects when set on the respective Pods

    • K8SPSMDB-435: Fixed a bug that prevented adding custom Labels to mongos Pods

    • K8SPSMDB-423: Fixed a bug where unpause of a cluster did not work when replsets.expose = LoadBalancer because of provisioning new Load Balancers with different names (Thanks to Aliaksandr Karavai for reporting this issue)

    • K8SPSMDB-494: When upgrading MongoDB clusters with Smart Update, the statuses reported in Custom Resource are now reflecting the real state

    • K8SPSMDB-489: Fixed a bug where the status of successful backups could be set to error in case of a cluster crash

    • K8SPSMDB-462: Fixed a bug where psmdb-backup object could not be deleted if the backup was not successful

    • K8SPSMDB-456: Fixed a bug where Smart Update was not upgrading a MongoDB deployment with a replica set consisting of one node

    • K8SPSMDB-455: Fixed a bug that prevented major version downgrade to a specific version number when upgradeOptions.setFCV Custom Resource option was not updated to the new version

    • K8SPSMDB-485: Fixed TLS documentation that referenced incorrect Secrets names from the cr.yaml configuration file

    Deprecation and Removal¶

    • We are simplifying the way the user can customize MongoDB components such as mongod and mongos. It is now possible to set custom configuration through ConfigMaps and Secrets Kubernetes resources. The following options will be deprecated in Percona Distribution for MongoDB Operator v1.9.0+, and completely removed in v1.12.0+:

      • sharding.mongos.auditLog.\*

      • mongod.security.redactClientLogData

      • mongod.security.\*

      • mongod.setParameter.\*

      • mongod.storage.\*

      • mongod.operationProfiling.mode

      • mongod.auditLog.\*

    • The mongos.expose.enabled option has been completely removed from the Custom Resource as it was causing confusion for the users

    Contact Us

    For free technical help, visit the Percona Community Forum.

    To report bugs or submit feature requests, open a JIRA ticket.

    For paid support and managed or consulting services , contact Percona Sales.


    Last update: 2023-09-29
    Percona LLC and/or its affiliates, © 2009 - 2023
    Made with Material for MkDocs

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better. Read more about Percona Cookie Policy.