> This page location: /docs.md > /docs/management.md > /docs/atlas/operator/current.md > /docs/atlas/operator/current/ak8so-get-started.md

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

# Migrate Parameters to Custom Resource Definitions

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/).

Beginning with Atlas Kubernetes Operator version 2.6, various resource configurations that previously took the form of parameters have transitioned to CRDs of their own. Support for the parameter-based parent resource configuration is deprecated. Existing parameter-based parent resource configurations will continue to work, but support for these configurations will be removed in a future release.

To continue managing these resources through Atlas Kubernetes Operator in the future, migrate to the appropriate CRD.

## Affected Configurations

The following configurations are affected:

| Parameter | CRD |
| --- | --- |
| [spec.customRoles](https://www.mongodb.com/docs/atlas/operator/current/atlasproject-custom-resource.md#std-label-atlasproject-spec-customroles) | [`AtlasCustomRole` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlascustomrole-custom-resource.md#std-label-atlascustomrole-custom-resource) |
| [spec.privateEndpoints](https://www.mongodb.com/docs/atlas/operator/current/atlasproject-custom-resource.md#std-label-atlasproject-spec-privateendpoints) | [`AtlasPrivateEndpoint` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlasprivateendpoint-custom-resource.md#std-label-atlasprivateendpoint-custom-resource) |
| [spec.projectIpAccessList](https://www.mongodb.com/docs/atlas/operator/current/atlasproject-custom-resource.md#std-label-atlasproject-spec-projectipaccesslist) | [`AtlasIPAccessList` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlasipaccesslist-custom-resource.md#std-label-atlasipaccesslist-custom-resource) |
| [spec.networkPeers](https://www.mongodb.com/docs/atlas/operator/current/atlasproject-custom-resource.md#std-label-atlasproject-spec-networkpeers) | [`AtlasNetworkPeering` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlasnetworkpeering-custom-resource.md#std-label-atlasnetworkpeering-custom-resource) |
| `spec.networkPeers.containerId` | [`AtlasNetworkContainer` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlasnetworkcontainer-custom-resource.md#std-label-atlasnetworkcontainer-custom-resource) |
| `spec.integrations` | [`AtlasThirdPartyIntegration` Custom Resource](https://www.mongodb.com/docs/atlas/operator/current/atlasthirdpartyintegration-custom-resource.md#std-label-atlasthirdpartyintegration-custom-resource) |

## Resource-Specific Considerations

Before you migrate parameters to resources, consider any implementation details specific to those parameters.

### Network Peering

The following considerations apply to `atlasNetworkPeering` resources:

- An `atlasNetworkPeering` CRD can refer to its corresponding `atlasNetworkContainer` by a Kubernetes name reference or ID.

- An `atlasNetworkPeering` CRD can refer to the `atlasProject` that hosts it by a Kubernetes name reference or ID.

- The [spec.networkPeers](https://www.mongodb.com/docs/atlas/operator/current/atlasproject-custom-resource.md#std-label-atlasproject-spec-networkpeers) parameter of an `atlasProject` CRD contains details of both the peering connection itself and the container that supports it. When you migrate from this parameter to an `atlasNetworkPeering` CRD, you might need to create an `atlasNetworkContainer` CRD for the container that supports it. To learn more, see [Network Container.](https://www.mongodb.com/docs/atlas/operator/current/migrate-parameter-to-resource.md#std-label-ak8so-migrate-ptr-considerations-networkcontainer)

### Network Container

The following considerations apply to `atlasNetworkContainer` resources:

- You don't need to create a new `atlasNetworkContainer` resource when you migrate the `atlasNetworkPeering` connection from a parameter to a resource if either:

  - You manage the network container supporting an `atlasNetworkPeering` connection outside of the Atlas Kubernetes Operator `atlasProject` in which you manage the `atlasNetworkPeering` connection

  - An `atlasNetworkContainer` resource for the `atlasNetworkPeering` connection's container already exists.

- An `atlasNetworkContainer` CRD can refer to its host `atlasProject` by a Kubernetes name reference or ID.

### Third-Party Integrations

The following considerations apply to `AtlasThirdPartyIntegration` resources:

- Each third-party integration requires its own `AtlasThirdPartyIntegration` resource. You can't define multiple integrations in the same resource.

- Each project can have only one instance of a particular type of third-party integration, whether configured by a `spec.integrations` entry of that type in your `AtlasProject` resource, or by an `AtlasThirdPartyIntegration` resource with a `spec.type` of that value.

  For example, if you have an `AtlasThirdPartyIntegration` CRD of `spec.type` `DATADOG`, you cannot declare a `spec.integrations.type` of `DATADOG` in your `AtlasProject` resource.

## Migration Procedure

To migrate from parameter-level resource management to CRD management:

1. Disable project reconciliation and edit subresource references.

   Add the `mongodb.com/atlas-reconciliation-policy: "skip"` annotation to the parent resource's `metadata`. This prevents Atlas Kubernetes Operator from attempting to reconcile the parent resource and its subresources.

   To prevent conflicts with the new CRD you create, you must delete the parameters corresponding to the resource you want to migrate from the parent resource.

   Consider the following example of an `atlasProject` with a `customRoles` configuration:

   ```text
   apiVersion: atlas.mongodb.com/v1
   kind: AtlasProject
   metadata:
     name: my-project
   spec:
     name: Test project
     connectionSecretRef:
       name: my-atlas-key
     customRoles:
       role:
         name: my-role
         actions:
           - name: getShardMap
             resources:
               cluster: true
           - name: shardingState
             resources:
               cluster: true
           - name: connPoolStats
             resources:
               cluster: true
           - name: getLog
             resources:
               cluster: true
           inheritedRoles:
             - name: operator-role-1
               role: backup
      projectIpAccessList:
        - cidrBlock: "203.0.113.0/24"
          comment: "CIDR block for Application Server B - D"
   ```

   Ensure that you have added the `annotations` block in lines 5 and 6 and remove the `customRoles` block shown in the previous example.

   ```text
   apiVersion: atlas.mongodb.com/v1
   kind: AtlasProject
   metadata:
     name: my-project
   annotations:
     mongodb.com/atlas-reconciliation-policy: "skip"
   spec:
     name: Test project
     connectionSecretRef:
       name: my-atlas-key
     projectIpAccessList:
       - cidrBlock: "203.0.113.0/24"
         comment: "CIDR block for Application Server B - D"
   ```

   **Warning:**

   If you do not apply this annotation, Atlas Kubernetes Operator will continue to attempt reconciliation as you modify your other resources. For users with [New Default: Deletion Protection in Atlas Kubernetes Operator 2.0](https://www.mongodb.com/docs/atlas/operator/current/index.md#std-label-deletion-protection) disabled, this can result in Atlas Kubernetes Operator removing the Atlas project when you remove the `atlasProject` resource, or entering a blocked state attempting to remove a project with active subresources such as database users or deployments.

2. Delete the parameters from the parent CRD.

   To prevent conflicts with the new CRD you create, you must first delete the parameters corresponding to the resource you want to migrate from the parent resource. For example, remove the `customRoles` parameter from the `atlasProject` CRD shown previously:

   ```text
   apiVersion: atlas.mongodb.com/v1
   kind: AtlasProject
   metadata:
    name: my-project
    annotations:
      mongodb.com/atlas-reconciliation-policy: "skip"
   spec:
     name: Test project
     connectionSecretRef:
       name: my-atlas-key
     projectIpAccessList:
       - cidrBlock: "203.0.113.0/24"
     comment: "CIDR block for Application Server B - D"
   ```

3. Create the new CRD.

   Create a CRD of the appropriate `kind` for the parameter you want to migrate, according to its syntax. For example, to migrate the `customRoles` parameter of the `atlasProject` CRD shown previously, create a [`AtlasCustomRole` Custom Resource.](https://www.mongodb.com/docs/atlas/operator/current/atlascustomrole-custom-resource.md#std-label-atlascustomrole-custom-resource)

   ```text
   apiVersion: atlas.mongodb.com/v1
   kind: AtlasCustomRole
   metadata:
     name: shard-operator-role
     namespace: mongodb-atlas-system
   labels:
     mongodb.com/atlas-reconciliation-policy: keep
   spec:
     projectRef:
       name: my-project
       namespace: my-operator-namespace
   role:
     name: my-role
     actions:
       - name: getShardMap
         resources:
           cluster: true
       - name: shardingState
         resources:
           cluster: true
       - name: connPoolStats
         resources:
           cluster: true
       - name: getLog
         resources:
           cluster: true
     inheritedRoles:
       - name: operator-role-1
         role: backup
   ```

4. Wait for Atlas Kubernetes Operator to sync the new resource status.

5. Remove the `atlas-reconciliation-policy: "skip"` annotation.

Additionally, you can now configure this resource as an [Independent CRD.](https://www.mongodb.com/docs/atlas/operator/current/ak8so-independent-crd.md#std-label-ak8so-independent-crd)
