- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for balance (0.15 sec)
-
manifests/charts/install-OpenShift.md
```console helm install -n istio-system istiod manifests/charts/istio-control/istio-discovery --set profile=openshift ``` 4) `gateways` charts install a load balancer with `ingress` and `egress`. Ingress secrets and access should be separated from the control plane. ```console helm install -n istio-system istio-ingress manifests/charts/gateways/istio-ingress --set profile=openshift
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Apr 12 16:01:31 GMT 2024 - 1.8K bytes - Viewed (0) -
manifests/charts/README.md
--set policy.enable=false \ --set global.istioNamespace=istio-master ``` ### Gateways A cluster may use multiple Gateways, each with a different load balancer IP, domains and certificates. Since the domain certificates are stored in the gateway namespace, it is recommended to keep each gateway in a dedicated namespace and restrict access.
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/gateways/istio-egress/NOTES.txt
- the new chart uses the default namespace service account, and doesn't require additional RBAC permissions. - simplified label structure. Label change is not supported on upgrade. - for 'internal load balancer' you should deploy a separate gateway, in a different namespace. All ingress gateway have a "app:ingressgateway" label, used to identify it as an ingress, and an "istio: ingressgateway$SUFFIX" label of Gateway selection.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 15 21:29:06 GMT 2020 - 1.5K bytes - Viewed (0)