- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for exports (0.13 sec)
-
manifests/charts/istio-control/istio-discovery/values.yaml
# - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. # # Within a multicluster mesh, each cluster must be (manually or auto)
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 22:00:40 GMT 2024 - 20.3K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/values.yaml
revision: "" # For Helm compatibility. ownerName: "" global: # set the default set of namespaces to which services, service entries, virtual services, destination # rules should be exported to. Currently only one value can be provided in this list. This value # should be one of the following two options: # * implies these objects are visible to all namespaces, enabling any sidecar to talk to any other sidecar.
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Feb 27 16:55:16 GMT 2024 - 12.4K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/values.yaml
gateways: istio-ingressgateway: name: istio-ingressgateway labels: app: istio-ingressgateway istio: ingressgateway ports: ## You can add custom gateway ports in user values overrides, but it must include those ports since helm replaces. # Note that AWS ELB will by default perform health checks on the first port
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Feb 27 16:55:16 GMT 2024 - 13K bytes - Viewed (0)