Skip to content

Releases: mongodb/mongodb-atlas-kubernetes

v2.0.1

04 Dec 14:21
2aeee6a
Compare
Choose a tag to compare

What's Changed

!!! Warning, this release contains breaking changes !!!

Breaking changes

  • Improve snapshot distribution management by @helderjs in #1168
    To enable an AtlasBackupSchedule custom resource to be reused by multiple deployments managed by the operator, we have removed replicationSpecId from the AtlasBackupSchedule custom resource. It will now be automatically set for every deployment that references it. As a result of this change, replicationSpecId is no longer configurable in an AtlasBackupSchedule and should be removed.
  • Add deletion protection feature by @helderjs in #1173 See: https://www.mongodb.com/docs/atlas/atlas-operator/#new-default--deletion-protection-in-ak8so-2.0
    With Atlas Kubernetes Operator 2.0, custom resources you delete in Kubernetes are no longer deleted in Atlas by default. Instead, Atlas Kubernetes Operator simply stops managing those resources - avoiding destructive change. The old behavior can be reverted. More info https://www.mongodb.com/docs/atlas/atlas-operator/#new-default--deletion-protection-in-ak8so-2.0
  • Remove legacy deployment by @igor-karpukhin in #1182
    In order to standardize on one deployment type (for non-serverless deployments), we have removed the notion of advancedDeploymentSpec. All deployment options are now supported as part of the deploymentSpec. For the AtlasDeployment resource, the following things were changed:
    spec.deploymentSpec - now contains all fields from the spec.advancedDeploymentSpec.
    spec.advancedDeploymentSpec - is gone. If you used advancedDeploymentSpec before, the only change you need to make is to rename the advancedDeploymentSpec to deploymentSpec in the AtlasDeployment resource. If you used deploymentSpec, you will need to rewrite it to advancedDeploymentSpec format.
  • Force secretRef fields for EncryptionAtREST and AlertConfiguration features by @roothorp in #1203 . This forces use of secrets for all credentials to promote security best practices.
    The following API secrets and credentials were moved from the AtlasProject custom resource to Secrets. Credentials and API secrets should now be stored in Secrets and referenced from the AtlasProject custom resource. The following fields were replaced:
    For the .spec.alertConfiguration.notifications:
    APIToken -> APITokenRef
    DatadogAPIKey -> DatadogAPIKeyRef
    FlowdockTokenAPI -> FlowdockTokenAPIRef
    OpsGenieAPIKey -> OpsGenieAPIKeyRef
    VictorOpsAPIKey -> VictorOpsSecretRef
    VictorOpsRoutingKey -> VictorOpsSecretRef (expected to have both VictorOps values)
    For the .spec.encryptionAtRest:
    • For AWS:
      AccessKeyID, SecretAccessKey, CustomerMasterKeyID and RoleID -> secretRef (expected to contain all those fields with values). Note: although there are fields AccessKeyID, SecretAccessKey they can only be provided for AtlasProject resources that had them before. New projects required to configure CloudProviderAccessRoles feature to enable the Encryption at REST for AWS.
    • For Azure:
      SubscriptionID, KeyVaultName, KeyIdentifier, Secret -> secretRef (expected to contain all those fields with values)
    • For GCP:
      ServiceAccountKey, KeyVersionResourceID -> secretRef (expected to contain all those fields with values)

Fixes

New Contributors

Full Changelog: v1.9.0...v2.0.0

MongoDB Atlas Operator v1.9.1

26 Oct 15:42
Compare
Choose a tag to compare

Fixes

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.9.0

09 Oct 12:50
6a6dd37
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.9.0

Attention

Fixes

  • Fixed a bug duplicating Projects listed in Teams Status (#1139).
  • Refactor IPAccessList reconciliation flow to avoid unneeded recreation (#1121)
  • Fixed backup schedule repeatedly updating (#1136).

New

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.8.2

24 Aug 09:23
1985c85
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.8.2

Operator Changes

AtlasProject Resource

  • Fixed a problem with constant Auditing reconciliations (#1081)
  • Fixed a problem with incorrect reconciliation for CustomRoles (#1096)

AtlasDeployment Resource

  • Fixed a problem with removing AtlasBackupSchedule resources that were referenced by AtalsDeployment resources (#1082)

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.8.1

10 Aug 08:09
7d95e9f
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.8.1

Operator Changes

  • Atlas client version bumped up to v0.32.0 (#1077)

AtlasProject Resource

  • Fixed missing watchers for Integrations secrets (#1021)
  • Encryption at REST feature: credentials for cloud providers can now be stored in secrets instead of the AtlasProject CR (#1045)
  • Encryption at REST feature: fixed GCP credentials validation (#1008)

AtlasDeployment Resource

AtlasDatabaseUser Resource

  • Fixed missing PE connection string for SHARDED clusters (#1062)

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.8.0

27 Jun 12:36
75c9489
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.8.0

Operator Changes

  • Fix encryption at REST aws.roleID (#987)
  • Support optional secrets for Alerts Configuration (#1002)

AtlasDataFederation Resource

  • Support to manage Data Federation deployments (#943)

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.7.2

18 Apr 17:30
69f7728
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.7.2

Operator Changes

  • Internally use only Atlas Advanced Cluster API (#825)

AtlasDeployment Resource

  • Fix connection secret generation for different namespaces (#914)
  • Fix Backup Auto Export configuration (#923)

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.7.1

24 Mar 11:07
763db17
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.7.1

Operator Changes

  • Atlas operator now won't print credentials in logs #907

Fixes CVE-2023-0436: Secret logging may occur in debug mode of Atlas Operator

The affected versions of MongoDB Atlas Kubernetes Operator may print sensitive information like GCP service account keys and API integration secrets while DEBUG mode logging is enabled. This issue affects MongoDB Atlas Kubernetes Operator versions: 1.5.0, 1.6.0, 1.6.1, 1.7.0.
Please note that this is reported on an EOL version of the product, and users are advised to upgrade to the latest supported version.
Required Configuration:

DEBUG logging is not enabled by default, and must be configured by the end-user. To check the log-level of the Operator, review the flags passed in your deployment configuration (eg. https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27)

CVSS: 4.5
CWE-532 Insertion of Sensitive Information into Log File

AtlasBackupSchedule Resource

  • Fixed broken export field #897

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.7.0

24 Feb 18:44
5755aa9
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.7.0

Operator Changes

  • Added Openshift 4.12 compatibility

AtlasProject Resource

  • Project can refer to a connection secret in a different namespace (#866)
  • Support for multiple private endpoints per single provider and region & Store all private endpoints connection strings (#877)
  • Fix for not working Encryption at REST for Google KMS #838

AtlasDeployment Resource

  • autoIndexingEnabled field marked as deprecated (#874)
  • Snapshot distribution (#870)

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

v1.6.1

27 Jan 13:55
4246aa9
Compare
Choose a tag to compare

MongoDB Atlas Operator v1.6.1

AtlasProject Resource

  • Remove ip access list validator #852 (#851)

AtlasDeployment Resource

  • Fixed BackupSchedule reconciliation #854

The images can be found in:
https://quay.io/mongodb/mongodb-atlas-kubernetes-operator