Skip to content

chore: Namespace the Helm defined templates with the chart name - #645

Open
lfrancke wants to merge 1 commit into
mainfrom
helm/namespace-defined-templates
Open

chore: Namespace the Helm defined templates with the chart name#645
lfrancke wants to merge 1 commit into
mainfrom
helm/namespace-defined-templates

Conversation

@lfrancke

@lfrancke lfrancke commented Sep 1, 2026

Copy link
Copy Markdown
Member

Part of stackabletech/issues#882 to make everything namespaced.

After rollout ALL (or some?) of these PRs should fail because some files in the operators will still reference the old defines and we now have a helm lint step in CI 🥳

So, I'd like to merge this, roll it out and I'll then amend each PR manually.

Helm shares one namespace for defined templates between a chart and all of
its subcharts, so identically named ones collide under an umbrella Chart.
A define name is fixed when Helm parses the template, so the chart name has
to be substituted at generation time. That makes the three helper files and
service.yaml Jinja templates.
The call sites in the files each operator owns are not templated, so every
generated PR needs a follow-up commit renaming them before it can merge.
stackabletech/issues#882
@lfrancke lfrancke self-assigned this Sep 1, 2026
@lfrancke lfrancke moved this to Development: Waiting for Review in Stackable Engineering Sep 1, 2026
@Techassi Techassi moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Sep 2, 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.

I generally approve, but I want to make sure we are happy with the choice of prefix:

  • The current prefix (operator name), will result in keys like airflow-operator.fullname
  • A different viable option would be to use "pretty string", which will result in keys like airflow.fullname

I have no strong preference, I just wanted to bring it up.

@lfrancke

lfrancke commented Sep 2, 2026

Copy link
Copy Markdown
Member Author

Thanks.

The prefix is purely internal, right? That's the whole point as far as I understand. So I'm fine with the current one but also have no strong preference.

If I don't hear any different I'd like to merge it tonight so I can prepare the rollout.

@Techassi

Techassi commented Sep 2, 2026

Copy link
Copy Markdown
Member

The prefix is purely internal, right?

Yeah it is (at least for 99% of use-cases). People could customize the Helm chart on their own, but then again, they can do whatever they want at this point.

So I'm fine with the current one but also have no strong preference.

Alright, then I wall call it done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

2 participants