- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for policy (0.19 sec)
-
manifests/charts/README.md
It is strongly recommended that different namespaces are used, with different service accounts. In particular access to the security-critical production components (root CA, policy, control) should be locked down and restricted. The new installer allows multiple instances of policy/control/telemetry - so testing/staging of new settings and versions can be performed by a different role than the prod version.
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/gateway/README.md
Note: this does mean that the namespace the gateway is deployed in must not have the `istio-injection=disabled` label. See [Controlling the injection policy](https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#controlling-the-injection-policy) for more info. ### Examples #### Egress Gateway
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) -
README.md
between services in the cluster and from a service to external services. The proxies form a _secure microservice mesh_ providing a rich set of functions like discovery, rich layer-7 routing, circuit breakers, policy enforcement and telemetry recording/reporting functions. > Note: The service mesh is not an overlay network. It > simplifies and enhances how microservices in an application talk to each
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jan 26 15:28:59 GMT 2024 - 6.6K bytes - Viewed (0)