Skip to content

Conversation

@willholley
Copy link
Member

What this PR does / why we need it:

We utilize Helm's lookup command to store a generated uuid in an "internal" secret in Kubernetes. This allows generating the uuid, making it persistent, and notifying the user (in NOTES.txt) that this auto-generation happened. We also tell the user how to disable the message by making that value persistent in values.

Which issue this PR fixes

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.

  • Chart Version bumped
  • e2e tests pass
  • Variables are documented in the README.md
  • NEWS.md updated

@willholley willholley force-pushed the colearendt-close-39 branch 4 times, most recently from 31349c2 to 5299ffe Compare December 31, 2025 09:54
We utilize Helm's `lookup` command to store a generated `uuid` in an "internal" secret in Kubernetes. This allows generating the `uuid`, making it persistent, and notifying the user (in `NOTES.txt`) that this auto-generation happened. We also tell the user how to disable the message by making that value persistent in values.

close #39
@willholley
Copy link
Member Author

I don't think this approach is going to work as-is because there is a race between the configmap where the uuid is used and the secret which persists it for the helper. We'll need to put all the components referencing the generated value in the same file (helm/helm#6456).

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.

A value for couchdbConfig.couchdb.uuid must be set

2 participants