- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for same (0.12 sec)
-
cni/README.md
- CNI installer will try to look for the config file under the mounted CNI net dir based on file name extensions (`.conf`, `.conflist`) - the file name can be explicitly set by `CNI_CONF_NAME` env var - the program inserts `CNI_NETWORK_CONFIG` into the `plugins` list in `/etc/cni/net.d/${CNI_CONF_NAME}` - the actual code is in pkg/install - including a readiness probe, monitoring.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
operator/README.md
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K bytes - Viewed (0) -
manifests/charts/ztunnel/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/charts/README.md
`istioctl kube-inject` or the automatic sidecar injector are used to select the environment. In the case of the sidecar injector, the namespace label `istio-env: <NAME_OF_ENV>` is used instead of the conventional `istio-injected: true`. The name of the environment is defined as the namespace where the corresponding control plane components (config, discovery, auto-injection) are running.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
meshConfig: accessLogFile: /dev/stdout ``` #### Revisions Control plane revisions allow deploying multiple versions of the control plane in the same cluster. This allows safe [canary upgrades](https://istio.io/latest/docs/setup/upgrade/canary/) ```yaml revision: my-revision-name
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2K bytes - Viewed (0) -
manifests/charts/istio-cni/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 - 2.5K bytes - Viewed (0) -
manifests/charts/gateway/README.md
An existing helm release can be `helm upgrade`d to this chart by using the same release name. For example, if a previous installation was done like: ```console helm install istio-ingress manifests/charts/gateways/istio-ingress -n istio-system ``` It could be upgraded with ```console
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/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)