We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The namespace that can be passed as Helm value isn't picked up in the Service resources part of the chart:
apiVersion: v1 kind: Service metadata: name: {{ $root.Values.oldNamingStyle | ternary $endpoint.name (printf "%s-%s" (include "yugabyte.fullname" $root) $endpoint.name) | quote }} annotations: ...
=>
apiVersion: v1 kind: Service metadata: name: {{ $root.Values.oldNamingStyle | ternary $endpoint.name (printf "%s-%s" (include "yugabyte.fullname" $root) $endpoint.name) | quote }} namespace: "{{ $root.Release.Namespace }}" annotations: ...
I was expecting all resources to be part of the namespace I'm specifying in the chart.
Similar to #64
The text was updated successfully, but these errors were encountered:
Workaround in my case:
--- apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization helmCharts: - name: yugabyte releaseName: yugabytedb repo: https://charts.yugabyte.com version: 2.17.0 namespace: yugabytedb-system valuesInline: replicas: master: 1 tserver: 1 resource: master: requests: cpu: 0.5 memory: 0.5Gi tserver: requests: cpu: 0.5 memory: 0.5Gi patches: - patch: |- - op: add path: /metadata/namespace value: yugabytedb-system target: version: v1 kind: Service name: yb-.*
Sorry, something went wrong.
@carhartl : Thanks for letting us know. Please feel free to send over a PR, otherwise, we will include this in our bug prioritization.
No branches or pull requests
The namespace that can be passed as Helm value isn't picked up in the Service resources part of the chart:
=>
I was expecting all resources to be part of the namespace I'm specifying in the chart.
Similar to #64
The text was updated successfully, but these errors were encountered: