Skip to content

fix: Make serviceAccount.name and serviceAccount.create work - #736

Merged
lfrancke merged 2 commits into
mainfrom
push-pyrlwwslmutu
Aug 17, 2026
Merged

fix: Make serviceAccount.name and serviceAccount.create work#736
lfrancke merged 2 commits into
mainfrom
push-pyrlwwslmutu

Conversation

@lfrancke

@lfrancke lfrancke commented Aug 10, 2026

Copy link
Copy Markdown
Member

Please see stackabletech/listener-operator#418 for the details.

Same fix as hive-operator#742 and listener-operator#418, applied to the two
workloads this chart ships.

serviceAccount.name had no effect: the ServiceAccount, the controller Deployment
and the CSI node driver DaemonSet all hardcoded <fullname>-serviceaccount, so the
value was silently ignored. They now resolve the name through
operator.serviceAccountName.

With serviceAccount.create=false the helper fell back to "default", giving pods
running as the namespace default ServiceAccount without the operator's
ClusterRole. It now requires serviceAccount.name, so the chart fails to render
instead of installing something that cannot work.

Rendered output is unchanged for the default values.

_helpers.tpl and serviceaccount.yaml are generated from operator-templating and
are ahead of the template until the matching change lands there.
@lfrancke
lfrancke added this pull request to the merge queue Aug 17, 2026
Merged via the queue into main with commit ff190e9 Aug 17, 2026
18 checks passed
@lfrancke
lfrancke deleted the push-pyrlwwslmutu branch August 17, 2026 08:34
@lfrancke lfrancke moved this from Development: Waiting for Review to Development: Done in Stackable Engineering Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Done

Development

Successfully merging this pull request may close these issues.

2 participants