Docs Menu
Docs Home
/ /
MongoDB Atlas Kubernetes Operator

Manage Private Endpoints

On this page

  • Prerequisites
  • Procedure


This feature is not available for M0 free clusters, M2, and M5 clusters. To learn more about which features are unavailable, see Atlas M0 (Free Cluster), M2, and M5 Limits.

Atlas Kubernetes Operator supports private endpoints to connect to dedicated clusters, serverless instances, and federated database instances.

When you use Atlas Kubernetes Operator to configure private links in Atlas, Atlas creates its own VPC or a Private Link service and places dedicated clusters or serverless instances within a region behind a load balancer in the Atlas VPC or Atlas VNet. To learn more, see the Private Endpoint Overview.

To manage your private endpoints with Atlas Kubernetes Operator, you can specify and update one of the following parameters:

Each time you change the spec field in any of the supported custom resources, Atlas Kubernetes Operator creates or updates the corresponding Atlas configuration.

Certain considerations and limitations apply to private endpoints. To learn more, see Configure Private Endpoints.

To enable connections with Atlas Kubernetes Operator to Atlas using private endpoints, you must:

To enable clients to connect to Atlas dedicated clusters or serverless instances using private endpoints, see the following procedures:

← Network Peering