> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Generated Custom Resources

Atlas Kubernetes Operator doesn't support Atlas Infinite Database clusters in public preview. To learn which features Atlas Infinite Database supports in public preview, see [Atlas Infinite Database Edition](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/). To learn more about preview features, see [Preview Features](https://www.mongodb.com/docs/preview-features/).

## Overview

Atlas Kubernetes Operator provides a set of custom resource definitions (CRDs) that are auto-generated from the MongoDB Atlas Administration API OpenAPI specification. These generated CRDs offer direct parity with the Atlas Administration API and are updated regularly as the API evolves. Over time, generated CRDs will replace the existing [custom resources](https://www.mongodb.com/docs/atlas/operator/current/custom-resources.md#std-label-custom-resources) as the standard interface for managing Atlas resources through Atlas Kubernetes Operator.

**Important: Incompatible with Existing Custom Resources**

Generated CRDs are **not** compatible with the existing set of [custom resources](https://www.mongodb.com/docs/atlas/operator/current/custom-resources.md#std-label-custom-resources). You cannot mix generated and existing CRDs to manage the same Atlas resource. Choose one set of CRDs for each resource you manage through Atlas Kubernetes Operator.

## Choosing Between CRD Sets

Because Atlas Kubernetes Operator currently offers a limited number of generated CRDs, you should evaluate which set best fits your needs:

| Existing Custom Resources | Generated Custom Resources |
| --- | --- |
| Full coverage of Atlas resource types. | Limited but expanding coverage of Atlas resource types. |
| Will be deprecated in a future release. | Will become the standard for managing Atlas resources through Atlas Kubernetes Operator. |
| Stable and well-established. | Closely tracks the Atlas Administration API OpenAPI specification. |

If the resource you need is available as a generated CRD, consider adopting it now to reduce the future effort of migrating from the existing CRDs. If a generated CRD is not yet available for your resource, continue to use the existing [custom resources.](https://www.mongodb.com/docs/atlas/operator/current/custom-resources.md#std-label-custom-resources)

## Available Generated CRDs

Atlas Kubernetes Operator currently supports the following generated CRDs:

| Resource | Description |
| --- | --- |
| [`Group` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/group-custom-resource.md#std-label-group-custom-resource) | Group in Atlas. |
| [`Cluster` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/cluster-custom-resource.md#std-label-cluster-custom-resource) | Cluster in Atlas. |
| [`DatabaseUser` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/databaseuser-custom-resource.md#std-label-databaseuser-custom-resource) | Database user in Atlas. |
| [`FlexCluster` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/flexcluster-custom-resource.md#std-label-flexcluster-custom-resource) | Flex cluster in Atlas. |
| [`IpaccessListEntry` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/ipaccesslistentry-custom-resource.md#std-label-ipaccesslistentry-custom-resource) | IP access list entry in Atlas. |

As the Atlas Administration API OpenAPI specification evolves, additional generated CRDs will become available. Check this page for updates.
