- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for provider (0.17 sec)
-
manifests/charts/README.md
As an extreme, the goal is to be possible to run Istio workloads in a cluster without installing any Istio component in that cluster. Currently, the minimum we require is the security provider (node agent or citadel). ### Install Istio CRDs This is the first step of the installation. Please do not remove or edit any CRD - config currently requires
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/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) -
README.md
functions. > Note: The service mesh is not an overlay network. It > simplifies and enhances how microservices in an application talk to each > other over the network provided by the underlying platform. - **Istiod** - The Istio control plane. It provides service discovery, configuration and certificate management. It consists of the following sub-components: - **Pilot** - Responsible for configuring the proxies at runtime.
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)