- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 31 for Scharf (0.23 sec)
-
manifests/charts/gateways/istio-egress/templates/injected-deployment.yaml
template: metadata: labels: {{ $gateway.labels | toYaml | indent 8 }} {{- if eq .Release.Namespace "istio-system"}} heritage: Tiller release: istio chart: gateways {{- end }} install.operator.istio.io/owning-resource: {{ .Values.ownerName | default "unknown" }} operator.istio.io/component: "EgressGateways" sidecar.istio.io/inject: "true"
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 5K bytes - Viewed (0) -
manifests/charts/base/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`. When configuring the chart, you should not include this.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
manifests/profiles/default.yaml
ingressGateways: - name: istio-ingressgateway enabled: true egressGateways: - name: istio-egressgateway enabled: false # Most default values come from the helm chart's values.yaml # Below are the things that differ values: defaultRevision: "" global: istioNamespace: istio-system configValidation: true gateways: istio-ingressgateway: {}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Feb 23 00:16:21 GMT 2024 - 744 bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/gateway/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`. When configuring the chart, you should not include this.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
manifests/charts/default/templates/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/templates/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/istiod-remote/templates/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/ztunnel/templates/zzz_profile.yaml
However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that. Finally, we can set all of that under .Values so the chart behaves without awareness. */}} {{- $defaults := $.Values.defaults }} {{- $_ := unset $.Values "defaults" }} {{- $profile := dict }} {{- with .Values.profile }} {{- with $.Files.Get (printf "files/profile-%s.yaml" .)}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0)