- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for switch (0.16 sec)
-
cni/README.md
- `install-cni` daemonset - main function is to install and help the node CNI, but it is also a proper server and interacts with K8S, watching Pods for recovery. - `istio-cni-config` configmap with CNI plugin config to add to CNI plugin chained config - creates service-account `istio-cni` with `ClusterRoleBinding` to allow gets on pods' info and delete/modifications for recovery. - `install-cni` container
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) -
manifests/helm-profiles/README.md
# Helm Profiles This folder provides a variety of "profiles" for helm installation. While a user can just explicitly pass this with `--values/-f`. However, Istio also provides a feature to bundle these with the charts, which is convenient when installing from remote charts. For details, see `copy-templates` Makefile target, and `manifests/zzz_profile.yaml`. Any changes to this folder should have a `make copy-templates` applied afterwards.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 708 bytes - Viewed (0) -
operator/README.md
### Controller (running locally) 1. Set env $WATCH_NAMESPACE (default value is "istio-system") and $LEADER_ELECTION_NAMESPACE (default value is "istio-operator") 1. Create the `WATCH_NAMESPACE` and `LEADER_ELECTION_NAMESPACE` if they are not created yet. ```bash kubectl create ns $WATCH_NAMESPACE --dry-run -o yaml | kubectl apply -f -
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/README.md
and understand each binary that gets deployed, and select which combination to use. Note: each component can be installed in parallel with an existing Istio 1.0 or 1.1 installation in `istio-system`. The new components will not interfere with existing apps, but can interoperate, and it is possible to gradually move apps from Istio 1.0/1.1 to the new environments and across environments ( for example canary -> prod )
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/ztunnel/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
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/istio-cni/README.md
- if deployed by manifest, add env `FELIX_WORKLOADSOURCESPOOFING` with value `Any` in `spec.template.spec.containers.env` for daemonset `calico-node`. (This will allow PODs with specified annotation to skip the rpf check. ) ### GKE notes On GKE, 'kube-system' is required. If using `helm template`, `--set cni.cniBinDir=/home/kubernetes/bin` is required - with `helm install`
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/istio-control/istio-discovery/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
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)