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
Would it be possible to add a new value called extraManifests. As the name implies, it will provide means to deploy extra manifests as an array.
This is something which already exists in other charts such as the popular kube-prometheus-stack.
The use case for this is, for example, suppose you are using Istio on your cluster and you would like to be able to specify a Virtual Service definition to be deployed with the chart used for accessing your zipkin ui.
eg:
# Extra manifests to deploy as an arrayextraManifests:
- apiVersion: networking.istio.io/v1beta1kind: VirtualServicemetadata:
name: zipkin-vsnamespace: zipkinspec:
hosts:
- "some-host.com"gateways:
- some/gatewayhttp:
- match:
- uri:
prefix: "/zipkin"route:
- destination:
host: zipkinport:
number: 9411
Implementation should be simple:
# templates/extra-objects.yaml{{ range .Values.extraManifests }}
---
{{ tpl (toYaml .) $ }}{{ end }}
The text was updated successfully, but these errors were encountered:
Would it be possible to add a new value called
extraManifests
. As the name implies, it will provide means to deploy extra manifests as an array.This is something which already exists in other charts such as the popular kube-prometheus-stack.
The use case for this is, for example, suppose you are using
Istio
on your cluster and you would like to be able to specify a Virtual Service definition to be deployed with the chart used for accessing your zipkin ui.eg:
Implementation should be simple:
The text was updated successfully, but these errors were encountered: