atlas kubernetes config generate
Parent: MongoDB Atlas Infrastructure as Code · Published reference · snapshot 2026-10-24 · skill mongodb-cohort-32c3803915b5
↓ Facts as markdownall context files
Source-anchored research for atlas kubernetes config generate. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- The current Atlas CLI command reference lists --operatorVersion default as 2.13.0, while the current operator import guide says generated files default to Operator v1.5.1 when the flag is omitted. Because the pages disagree, set --operatorVersion explicitly and confirm installed CLI/plugin behavior; these pages do not establish one runtime default for every installation. (medium confidence) (verified as of 2026-10-14) [source]
- Explicitly choose the intended Operator version when repeatable export compatibility matters: MongoDB documents both a version selector and version-dependent output, while its command reference and import guide disagree about the default. (medium confidence) [source]
How-to and procedures
- Use --clusterName to select deployments, --targetNamespace to set the namespace of generated resources, and --operatorVersion to target an Operator version. The import guide says omitting --clusterName exports all clusters in the selected project. (medium confidence) [source]
Comparisons and alternatives
- The command reference exposes --dataFederationName and --independentResources. The latter uses external IDs instead of Kubernetes references where independent usage is supported. The plugin changelog records that config apply gained these previously available generate flags in plugin 1.1.1. (medium confidence) [source]
- The --independentResources flag makes resources that support independent usage use external IDs instead of Kubernetes references. The plugin changelog confirms this flag existed in generate before it was added to apply. (high confidence) [source]
Facts and statements
- atlas kubernetes config generate exports existing Atlas projects, deployments, and database users as resources compatible with Atlas Kubernetes Operator. It provides an adoption workflow for existing Atlas infrastructure. (high confidence) [source]
- generate writes YAML to stdout. Operators can redirect that output to a file or pipe it into kubectl apply -f -. The separate config apply command sends the generated configuration directly to a target Kubernetes cluster. (low confidence) [source]
- --includeSecrets populates generated secrets with credential data. Without it, the import guide says the generated credentials secret is not populated. Exported credential data is plain text, so review and protect any saved YAML before using it in a repository. (high confidence) [source]
- --clusterName selects a comma-separated subset of project clusters; omitting it exports all project clusters. --targetNamespace sets metadata.namespace on exported entities. (medium confidence) [source]
- The import guide lists AtlasDeployment, AtlasBackupSchedule, AtlasBackupPolicy, AtlasProject, AtlasDatabaseUser, and AtlasTeam, but this list is not exhaustive for all releases: the CLI 1.34.0 changelog, dated 2024-12-18, adds AtlasCustomRole and AtlasPrivateEndpoint generation. (medium confidence) [source]
- Atlas CLI 1.39.0, released 2025-02-18, moved Kubernetes commands to an automatically installed plugin. The official plugin repository identifies itself as the Atlas CLI Kubernetes Plugin. (medium confidence) [source]
- Atlas CLI 1.5.1, released 2023-02-16, fixed generate producing AtlasDatabaseUser resources with the same resource name for different users. This is a historical defect, not evidence that current releases still have the bug. (low confidence) [source]
- The command reference describes Kubernetes resource export and does not document billing-event selection or alert-configuration flags. Its relevance to billing alerts is therefore a possible configuration migration workflow, not a verified billing-alert API operation; billing-alert round-trip coverage remains unproven. (low confidence) (verified as of 2026-10-14) [source]
- The command reference also offers --dataFederationName to select federated database instances by name; the plugin changelog records that generate supported this flag before apply gained it. (high confidence) [source]
- Inference for generated Atlas manifests: omit populated credential values from Git commits. The Atlas Operator import guide says --includeSecrets renders the Atlas credentials secret in plain text. Kubernetes warns that checking a base64 Secret manifest into a source repository exposes its values to manifest readers. Red Hat OpenShift GitOps 1.21 also says not to store plain-text secrets in Git and recommends secret-management solutions. (high confidence) [source]
Children
- Operator-compatible resource export (frontier)
- Generated manifest credential handling (frontier)
- Operator version compatibility (frontier)
Frontier under this node: Generated manifest credential handling, Operator version compatibility, Operator-compatible resource export