- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 24 for Scharf (0.21 sec)
-
Makefile.core.mk
warning=$$(cat manifests/helm-profiles/warning-edit.txt | sed ':a;N;$$!ba;s/\n/\\n/g') ; \ for chart in $(CHARTS) ; do \ for profile in manifests/helm-profiles/*.yaml ; do \ sed "1s|^|$${warning}\n\n|" $$profile > manifests/charts/$$chart/files/profile-$$(basename $$profile) ; \ done; \ cp manifests/zzz_profile.yaml manifests/charts/$$chart/templates ; \ done
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 08 20:25:15 GMT 2024 - 22.5K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/templates/deployment.yaml
template: metadata: labels: {{ $gateway.labels | toYaml | indent 8 }} {{- if eq .Release.Namespace "istio-system"}} heritage: Tiller release: istio chart: gateways {{- end }} service.istio.io/canonical-name: {{ $gateway.name }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 12.1K bytes - Viewed (1) -
manifests/charts/base/crds/crd-all.gen.yaml
apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: annotations: "helm.sh/resource-policy": keep labels: app: istio-pilot chart: istio heritage: Tiller release: istio name: wasmplugins.extensions.istio.io spec: group: extensions.istio.io names: categories: - istio-io - extensions-istio-io
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 20:20:47 GMT 2024 - 606.1K bytes - Viewed (0) -
manifests/addons/dashboards/istio-performance-dashboard.json
dashboard are intended to show Istio main components cost in terms of resources utilization under steady load.\n\n- **vCPU / 1k rps:** shows vCPU utilization by the main Istio components normalized by 1000 requests/second. When idle or low traffic, this chart will be blank. The curve for istio-proxy refers to the services sidecars only.\n- **vCPU:** vCPU utilization by Istio components, not normalized.\n- **Memory:** memory footprint for the components. Telemetry and policy are normalized by 1k rps, and...
Json - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Mar 27 03:47:04 GMT 2024 - 39.6K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/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: "IngressGateways" 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/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/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)