- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for foo (0.13 sec)
-
istioctl/pkg/workload/testdata/vmconfig/ipv6/meshconfig.yaml
# should be overridden by the command ISTIO_META_DNS_CAPTURE: "false" # should be overridden by the annotation on the WorkloadGroup PROXY_CONFIG_ANNOT_VALUE: "foo" # should be in the final cluster.env/mesh.yaml
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 300 bytes - Viewed (0) -
manifests/charts/istiod-remote/templates/configmap.yaml
{{- end }} {{- end }} {{/* We take the mesh config above, defined with individual values.yaml, and merge with .Values.meshConfig */}} {{/* The intent here is that meshConfig.foo becomes the API, rather than re-inventing the API in values.yaml */}} {{- $originalMesh := include "mesh" . | fromYaml }} {{- $mesh := mergeOverwrite $originalMesh .Values.meshConfig }} {{- if .Values.pilot.configMap }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 4.9K bytes - Viewed (0) -
istioctl/pkg/workload/testdata/vmconfig/ipv4/meshconfig.yaml
# should be overridden by the command ISTIO_META_DNS_CAPTURE: "false" # should be overridden by the annotation on the WorkloadGroup PROXY_CONFIG_ANNOT_VALUE: "foo" # should be in the final cluster.env/mesh.yaml
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 300 bytes - Viewed (0) -
istioctl/pkg/workload/testdata/vmconfig-nil-proxy-metadata/workloadgroup.yaml
kind: WorkloadGroup metadata: name: foo namespace: bar spec: metadata: annotations: {} labels: {} template: ports: {} serviceAccount: vm-serviceaccount probe: httpGet:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 215 bytes - Viewed (0) -
istioctl/pkg/workload/testdata/vmconfig/ipv4/workloadgroup.yaml
kind: WorkloadGroup metadata: name: foo namespace: bar spec: metadata: annotations: proxy.istio.io/config: |- proxyMetadata: # this should override the value from the global meshconfig PROXY_CONFIG_ANNOT_VALUE: bar labels: {} template: ports: {} serviceAccount: vm-serviceaccount probe: httpGet:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 377 bytes - Viewed (0) -
istioctl/pkg/workload/testdata/vmconfig/ipv6/workloadgroup.yaml
kind: WorkloadGroup metadata: name: foo namespace: bar spec: metadata: annotations: proxy.istio.io/config: |- proxyMetadata: # this should override the value from the global meshconfig PROXY_CONFIG_ANNOT_VALUE: bar labels: {} template: ports: {} serviceAccount: vm-serviceaccount probe: httpGet:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 377 bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/configmap.yaml
{{- end }} {{- end }} {{/* We take the mesh config above, defined with individual values.yaml, and merge with .Values.meshConfig */}} {{/* The intent here is that meshConfig.foo becomes the API, rather than re-inventing the API in values.yaml */}} {{- $originalMesh := include "mesh" . | fromYaml }} {{- $mesh := mergeOverwrite $originalMesh .Values.meshConfig }} {{- if .Values.pilot.configMap }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 4.9K bytes - Viewed (0) -
operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz
doesn't follow these names, you can override them. For example, if you have resources named `my-custom-gateway` with `selector` labels `foo=bar,istio=ingressgateway`: ```yaml name: my-custom-gateway # Override the name to match existing resources labels: app: "" # Unset default app selector label istio: ingressgateway # override default istio selector label foo: bar # Add the existing custom selector label ``` #### Migrating an existing Helm release An existing helm release can be `helm upgrade`d...
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 198.1K bytes - Viewed (1)