Skip to content

docs: Add values.schema.json and NOTES.txt - #935

Merged
lfrancke merged 2 commits into
mainfrom
push-nuztxrqqyykm
Sep 11, 2026
Merged

lfrancke merged 2 commits into
mainfrom
push-nuztxrqqyykm

Conversation

@lfrancke

@lfrancke lfrancke commented Aug 28, 2026

Copy link
Copy Markdown
Member

This is mostly copied over from hive-operator since the files are not
templated.
Having a schema makes Helm validate values on install, upgrade, lint and
template AND shows as a nice reference on ArtifactHub.
One thing to note is that we include the "global" block even if it's not
used by us. This is due to https://helm.sh/de/docs/chart_template_guide/subcharts_and_globals/
In short: When used as a subchart Helm injects a "global" into every
subchart. If we don't declare it validation will fail when used as a
subchart.
This also documents all used values in values.yaml itself and adds a
NOTES.txt which is displayed automatically after an install.
@lfrancke lfrancke self-assigned this Aug 28, 2026
@lfrancke lfrancke moved this to Development: Waiting for Review in Stackable Engineering Aug 28, 2026

@Techassi Techassi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not templated on purpose.

I can see why the schema is not templated (because the values.yaml file it describes is also not templated), but why is the NOTES.txt file not templated? I don't see anything operator-specific in there (other than its name, which can easily be templated).

@Techassi Techassi moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Aug 28, 2026
@lfrancke

lfrancke commented Aug 28, 2026

Copy link
Copy Markdown
Member Author

Because it would require special handling for listener, secret and commons.

The text would otherwise not fit.

"This installs the Stackable operator for Trino only." -> "This installs the Stackable operator for Commons operator only" or similar.
It would have needed special casing in operator templating and I thought that's not worth it for something that hopefully doesn't change often.

@Techassi

Copy link
Copy Markdown
Member

It would have needed special casing in operator templating and I thought that's not worth it for something that hopefully doesn't change often.

I really hope that's the case, because otherwise it will be painful to rollout a particular change across all operators.

It would have needed special casing

Special casing is fine and in this particular instance it doesn't seem to be super complicated to do.

@lfrancke

Copy link
Copy Markdown
Member Author

I don't have a strong opinion, I can also try to put up a PR with the special casing of this so you/we can see what it'd look like if you prefer. Your call.

@lfrancke

lfrancke commented Sep 8, 2026

Copy link
Copy Markdown
Member Author

The templating PR has been merged. Can you still approve this for the schema?
The templating rollout will then be a no-op for the NOTES.txt file.

@lfrancke
lfrancke requested a review from Techassi September 8, 2026 09:09
@lfrancke
lfrancke enabled auto-merge September 8, 2026 09:09
@lfrancke lfrancke moved this from Development: In Review to Development: Done in Stackable Engineering Sep 11, 2026
@lfrancke
lfrancke added this pull request to the merge queue Sep 11, 2026
Merged via the queue into main with commit fa73ea7 Sep 11, 2026
22 of 24 checks passed
@lfrancke
lfrancke deleted the push-nuztxrqqyykm branch September 11, 2026 14:08
@lfrancke lfrancke moved this from Development: Done to Done in Stackable Engineering Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants