feat(helm): add namespace override capability for multi-namespace deployments#1640
feat(helm): add namespace override capability for multi-namespace deployments#1640Slach merged 1 commit intoAltinity:0.25.0from
Conversation
Slach
left a comment
Slach
left a comment
There was a problem hiding this comment.
look to dev/generate_helm_chart.sh
all templates/generated shall be changed from this script
bwdmr
force-pushed
the
namespaceoverride
branch
from
db20c8a to
7c412fb
Compare
…loyments Adds a new helper template "altinity-clickhouse-operator.namespace" that allows overriding the release namespace via Values.namespaceOverride. Updates all resource templates to use this helper instead of directly referencing .Release.Namespace. This change enables multi-namespace deployments in combined charts while maintaining backward compatibility.
bwdmr
force-pushed
the
namespaceoverride
branch
from
7c412fb to
3aa503c
Compare
|
Sorry for disturbing you again Could you clarify? Do you want to install helm chart to some namespace but install rendered manifest to another namespace? Which behavior you try to achieve? If you want to change operator watched namespace for example and install operator in one namespace but watch custom resources in another namespaces just change files:
config.yaml:
# empty value will watch all namespaces
namespaces: [""] |
|
no, according to this issue: kubernetes-sigs/kustomize#5566 what i want is compatibility across all current tooling to respect the namespace set for the helm chart to install the resources to. the only change current users would be affected of, is to define the namespace the operator should be installed to in the values.yaml instead of using the not detectable variable {{Release.Namespace}} namespaceOverride: ""
operator:
... |
|
@bwdmr thanks for contribution |
2 participants
Adds a new helper template "altinity-clickhouse-operator.namespace" that allows overriding the release namespace via Values.namespaceOverride. Updates all resource templates to use this helper instead of directly referencing .Release.Namespace. This change enables multi-namespace deployments in combined charts while maintaining backward compatibility.