Skip to content

fix: prevent silent MongoDB provisioning failure with existingSecretName (issue #116) - #128

Open
alix-graylog wants to merge 1 commit into
mainfrom
c-06
Open

fix: prevent silent MongoDB provisioning failure with existingSecretName (issue #116)#128
alix-graylog wants to merge 1 commit into
mainfrom
c-06

Conversation

@alix-graylog

Copy link
Copy Markdown
Collaborator

Resolves #116

Summary

Adds template-time validation to prevent silent MongoDB provisioning failures when users accidentally combine global.existingSecretName with chart-managed MongoDB.

Changes

  • Add fail guard in secrets.yaml to detect dangerous configuration
  • Gate test-mongodb-connectivity hook on chart-managed mode
  • Add comprehensive example for GitOps + external MongoDB pattern

Testing

  • Template renders error immediately when invalid config detected
  • Example values file documented with all prerequisites

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 this pull request may close these issues.

global.existingSecretName + chart-managed MongoDB = silently broken install

1 participant