Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
8 results found
-
Do not require Project Custom Resource for managing other Resources
We would like to adopt the Atlas Operator without managing our entire Atlas Project in Kubernetes, or we would like to manage the Project elsewhere, maybe in another namespace, in another k8s cluster or in Terraform.
It does not make sense that the
AtlasDatabaseUserrequires aAtlasProjectresource to exist. We want to manage users separately from the Project as those can be owned by different users in our system.Also the API and Terraform resources do not have this requirement so it breaks convention when the Atlas Operator has this unique requirement https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/database_user
To work around this we would…
1 vote -
Use kubernetes Atlas operator to create and manage only users
We are already managing the Atlas project using terraform and do not want to have two separate tools managing the same resource. We would still like to generate atlas users automatically through the operator. If there was a method of just providing the project ID as a string like we are able to in the terraform resource definition, this would not be a problem.
1 vote -
Create an AtlasRole custom resource
Currently roles are configured as a list inside the AtlasProject resource. I propose managing these as individual AtlasRole custom resources instead.
Consider a typical microservice based application with several microservices deployed by individual Helm charts, each sharing the same project and cluster. In this scenario the app developer may want to create custom roles for each app / group of apps with access to certain collections, eg to stop them from being able to read collections with sensitive data
Currently it is possible for apps to create their own users, but those users must assume one or more existing roles.…
1 vote -
Kubernetes AtlasDeployment snapshot persistence flag
When AtlasDeployment resources are deleted, the cluster is immediately terminated without the opportunity to enable snapshot persistence after deletion as there is in the Atlas UI. An option in the spec should be added to opt-into this behavior from a Kubernetes perspective.
1 vote -
Kubernetes AtlasProject backup compliance
Extending the AtlasProject Kubernetes resource to allow management of a backup compliance policy, including setting project-wide backup schedules and enabling backup persistence after termination by default, would be a major improvement over the current experience.
1 vote -
Kubernetes reconcilation interval
Kubernetes resources generally should be reconciled on a sensible schedule to prevent configuration drift between k8s and Atlas API.
AtlasProject is a critical one that can have widespread impact if API configuration drifts from Kubernetes and is not promptly corrected.
1 vote -
Reference a db user from namespace A to a project in a different namespace
We need to ability to reference db user in namespace A to an Atlas project in a different namespace.
1 vote -
Enable setting encryption at rest details for project
Please allow us to set the encryption at rest KMS details for the project when we create the project
1 vote
- Don't see your idea?