-
Notifications
You must be signed in to change notification settings - Fork 91
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
Support AtlasProject using not local but global AKO secret -api-key in the "atlas-cluster" chart. #93
Labels
Comments
denist-huma
added a commit
to denist-huma/helm-charts
that referenced
this issue
Dec 3, 2021
…f in the "atlas-cluster" chart. mongodb#93 Signed-off-by: Denis Trofimov <[email protected]>
denist-huma
changed the title
Add an option to create AtlasProject without connectionSecretRef in the "atlas-cluster" chart.
Support AtlasProject using not local but global AKO secret -api-key in the "atlas-cluster" chart.
Dec 3, 2021
denist-huma
added a commit
to denist-huma/helm-charts
that referenced
this issue
Jan 14, 2022
…f in the "atlas-cluster" chart. mongodb#93 Signed-off-by: Denis Trofimov <[email protected]>
leo-ri
pushed a commit
that referenced
this issue
Feb 24, 2022
…f in the "atlas-cluster" chart. #93 Signed-off-by: Denis Trofimov <[email protected]>
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days. |
This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the expected behavior?
My use case is to create AtlasProject without connectionSecretRef.
I use a global secret and it works as expected. https://docs.atlas.mongodb.com/atlas-operator/#ak8so-workflow
I need my result to be like:
It should be the case of values equals:
What is the current behavior?
What we have now is inconsistent. This command creates a reference to a non-existing secret.
The text was updated successfully, but these errors were encountered: