Releases: mongodb/mongodb-atlas-kubernetes
Releases · mongodb/mongodb-atlas-kubernetes
v1.1.0
MongoDB Atlas Operator v1.1.0
AtlasProject Resource
- Maintenance Windows are now supported
- Fixed missing fields in condition status for Private Endpoints
- Unused condition statuses are now dynamically removed
Operator
- Fixed missing secure connection string in the secrets
The images can be found in:
https://quay.io/repository/mongodb/mongodb-atlas-kubernetes-operator
v1.0.0
MongoDB Atlas Operator v1.0.0
Breaking changes
AtlasCluster
CRD renamed toAtlasDeployment
spec.clusterSpec
renamed tospec.deploymentSpec
spec.advancedClusterSpec
renamed tospec.advancedDeploymentSpec
New features
AtlasProject Resource
- Added 3rd-Party Integrations support
- Added Prometheus Integration support via 3rd party integrations
- Added GCP Private Endpoints support
AtlasDeployment Resource
- Added Serverless Instances support via new
spec.serverlessSpec
field - Added an ability to schedule backups for AtlasDeployments
- Added an ability to upgrade shared-tier clusters M0/M2/M5 to M10+ by just changing
spec.deploymentSpec.providerSettings.instanceSizeName
forAtlasDeployment
CRs - Added
processArgs
section for theAtlasDeployment
CRD - Added an ability to omit
providerName = TENANT | SERVERLESS
when creatingAtlasDeployment
CRs
Operator
- Added log levels and JSON log output for the operator. Log level can be changed by providing
—log-level=debug | info | warn | error | dpanic | panic | fatal
flag. Output format can be changed by providing—log-encoder=json | console
flag
Fixes
- Fixed a bug when
AtlasProject
CR couldn’t be deleted if credentials secret has been deleted: #425 - Resolved missing epoch timestamps in log messages: #470
- Fixed a bug with incorrect user-agent version
- Fixed a CVE with
golang.org/x/crypto/ssh
module
The images can be found in:
https://quay.io/repository/mongodb/mongodb-atlas-kubernetes-operator
v0.8.1
MongoDB Atlas Operator v0.8.1
Atlas Operator
- Changes
- Fixed Go CVE https://security.snyk.io/vuln/SNYK-GOLANG-GOLANGORGXCRYPTOSSH-551923
- Fixed incorrect
User-Agent
https://jira.mongodb.org/browse/CLOUDP-119550
The images can be found in:
https://quay.io/repository/mongodb/mongodb-atlas-kubernetes-operator
v0.8.0
MongoDB Atlas Operator v0.8.0
- The Atlas Operator is now in Beta
- Deploying Advanced Atlas Clusters is now supported
- x.509 User Authentication is now supported
- Warning: This release contains breaking changes to the AtlasCluster Resource. See below for details on how to update to the new format. This also applies to the "atlas" section of the atlas-cluster Helm chart.
Atlas Operator
- Changes
- When installing a cluster using the helm chart, helm will not exit until the cluster is ready if
postInstallHook.enabled
is set to true. - The operator now only watches secrets with the label
atlas.mongodb.com/type=credentials
to avoid watching unnecessary secrets. - It is possible to configure the Operator to skip reconciliations on specific resources by adding the annotation
mongodb.com/atlas-reconciliation-policy=skip
. - Upgrade Controller Runtime to v0.11.0
- Upgraded to Go 1.17
- When installing a cluster using the helm chart, helm will not exit until the cluster is ready if
- Bug fixes
- Fixed an issue where errors would be logged upon resource deletion.
AtlasProject Resource
- Changes
- The AtlasProject will not be marked as ready until the Project IP Access List is successfully created.
- Enable User Authentication using X.509 Certificates
AtlasCluster Resource
- Changes
- The AtlasCluster now has two main configuration options. You must specify exactly one of
spec.clusterSpec
orspec.advancedClusterSpec
.clusterSpec
uses the regular Atlas Cluster API whileadvancedClusterSpec
uses the Atlas Advanced Cluster API- Note: in order to migrate an existing resource to use the
spec.clusterSpec
structure, you must move all fields currently underspec.*
tospec.clusterSpec.*
with the exception ofspec.projectRef
- The AtlasCluster now has two main configuration options. You must specify exactly one of
The images can be found in:
v0.7.0
v0.6.1
Fixes:
- Remove required namespace field from CRD
v0.6.0
Changes:
- Support global secret configuration (#222)
- Remove dots from connection secret fields (#241)
- Reference project from another namespace (#254)
- Do not try to delete non-existing Atlas projects (#240)
- Add annotations to avoid removing resources from Atlas (#213)
- Improve DB user cleanup (#283)
- Pass git version to the binary on build (#195)
- Remove kube-proxy from deployment (#249)
v0.5.0
Changes
- Support for
AtlasDatabaseUser
Custom Resource - Atlas cluster connection Secrets are created on updates to
AtlasCluster
,AtlasDatabaseUser
resources - Deployment configuration improvements: using non-default
ServiceAccount
, common labels for all deployment configs - Decreased reconciliation
syncPeriod
to 3 hours
Bug Fixes
- Fixed an issue with
AtlasCluster
replicationSpecs
configuration
v0.4.0
Changes
- Support for OLM bundles generation
- Support namespace and clusterwide deployment modes
- Support for
AtlasCluster
replicationSpecs
configuration
Bug Fixes
- Fixes an issues with Operator Connection Secret name format
v0.3.0
Changes
- Support for IP Access List in
AtlasProject
- Support the Operator-level Connection Secret
- Handling deletion of the
AtlasProject
- Connection Secret for
AtlasProject
is watched by the Operator - Handling
AtlasCluster
pause/unpause