You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quick ask about the seldon-core-operator helm chart. I'm using it as a dependency in another helm chart, and I would like to install it into a different namespace (seldon-system) from other dependencies.
This can be done using ambassador helm chart as a dependency because they use a namespaceOverride, in the values.yaml file and assign the namespace based on a template in the _helpers.tpl file like this:
{{/*Create chart namespace based on override value.*/}}{{- define "seldon-core.namespace" -}}{{- if .Values.namespaceOverride -}}{{- .Values.namespaceOverride -}}{{- else -}}{{- .Release.Namespace -}}{{- end -}}{{- end -}}
and then specifying the namespace in kubernetes manifests like this:
namespace: {{ include "seldon-core.namespace" . }}
It looks like it would be pretty quick to implement. I'm willing to create the PR if the team is open to this change.
Thanks!
The text was updated successfully, but these errors were encountered:
Hello!
Quick ask about the seldon-core-operator helm chart. I'm using it as a dependency in another helm chart, and I would like to install it into a different namespace (
seldon-system
) from other dependencies.This can be done using ambassador helm chart as a dependency because they use a
namespaceOverride
, in the values.yaml file and assign the namespace based on a template in the_helpers.tpl
file like this:and then specifying the namespace in kubernetes manifests like this:
It looks like it would be pretty quick to implement. I'm willing to create the PR if the team is open to this change.
Thanks!
The text was updated successfully, but these errors were encountered: