Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServerlessSpec is not optional and fails validation with schema #364

Closed
Sufian22 opened this issue Nov 26, 2024 · 3 comments · Fixed by #365
Closed

ServerlessSpec is not optional and fails validation with schema #364

Sufian22 opened this issue Nov 26, 2024 · 3 comments · Fixed by #365

Comments

@Sufian22
Copy link

What did you do to encounter the bug?
Steps to reproduce the behavior:

  1. Generate the K8s template files (with helm template) for mongodb/atlas-deployment helm chart

What did you expect?
I expected no serverlessSpec field in the AtlasDeployment if none has been specified in the values.yaml file.

What happened instead?
It generates a spec.serverlessSpec with null value inside the AtlasDeployment which doesn't satisfy the schema definition.

Screenshots
The if condition should be added also to the serverlessSpec too:

Kubernetes Cluster Information

  • Distribution
  • Version
  • Image Registry location (quay, or an internal registry)

Additional context

  • Atlas-Operator and Atlas-Deployment helm charts both in version 2.4.1
@josvazg
Copy link
Collaborator

josvazg commented Nov 27, 2024

Thanks for the report @Sufian22 , spot on!
@igor-karpukhin has already posted #365 to solve this

@Sufian22
Copy link
Author

Sufian22 commented Nov 27, 2024

@josvazg I'm finding more incompatibilities with the generated AtlasDeployment resource and it's schema definition, do you want me to create another issue for that? 🤔

@josvazg
Copy link
Collaborator

josvazg commented Nov 27, 2024

@josvazg I'm finding more incompatibilities with the generated AtlasDeployment resource and it's schema definition, do you want me to create another issue for that? 🤔

Yes, please. If the issues are not related to this same exact fix, it is better to be separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants