mongodb / mongodb-atlas-kubernetes

MongoDB Atlas Kubernetes Operator - Manage your MongoDB Atlas clusters from Kubernetes
http://www.mongodb.com/cloud/atlas
Apache License 2.0
146 stars 75 forks source link

Serverless AtlasDeployment on GCP fails #821

Closed pabloromeo closed 1 year ago

pabloromeo commented 1 year ago

What did you do to encounter the bug? Steps to reproduce the behavior: Attempted to create a Serverless Deployment on GCP using:

apiVersion: atlas.mongodb.com/v1
kind: AtlasDeployment
metadata:
  name: some-name
spec:
  projectRef:
    name: some-name
  serverlessSpec:
    name: some-name
    providerSettings:
      providerName: GCP
      regionName: CENTRAL_US

The Database is in fact created correctly in Atlas without issues, however, the Operator fails to finish the creation process, showing the following status:

Status:
  Conditions:
    Last Transition Time:  2023-01-03T03:13:31Z
    Status:                False
    Type:                  Ready
    Last Transition Time:  2023-01-03T03:13:31Z
    Status:                True
    Type:                  ValidationSucceeded
    Last Transition Time:  2023-01-03T03:13:32Z
    Message:               serverless private endpoints are only supported for AWS and Azure
    Reason:                InternalError
    Status:                False
    Type:                  DeploymentReady
  Observed Generation:     2
  State Name:              IDLE

What did you expect? I expected to be able to provision a Serverless Deployment on GCP without using private endpoints

What happened instead? The Operator just continues to loop on the Internal Error, when the DB has already been deployed and the Secret with the connection string should have been created (which hasn't).

Screenshots The Deployment is actually created, but for some reason the Operator thinks I attempted to use private endpoints.

image

Operator Information

Kubernetes Cluster Information

Additional context Add any other context about the problem here.

If possible, please include:

Sugar-pack commented 1 year ago

Hi @pabloromeo. Thank you for creating the issue. This issue has been fixed in this PR: #822