mirror of https://github.com/istio/istio.io.git
fix profiles links (#15970)
This commit is contained in:
parent
e8c8e211bf
commit
8041a22ee2
|
@ -13,7 +13,7 @@ This page describes the built-in configuration profiles that can be used when
|
|||
[installing Istio](/docs/setup/install/istioctl/).
|
||||
The profiles provide customization of the Istio control plane and of the sidecars for the Istio data plane.
|
||||
|
||||
You can start with one of [Istio’s built-in configuration profiles]({{< github_file >}}/manifests/profiles) and then further
|
||||
You can start with one of [Istio’s built-in configuration profiles]({{< github_tree >}}/manifests/profiles) and then further
|
||||
[customize the configuration](/docs/setup/additional-setup/customize-installation/)
|
||||
for your specific needs. The following built-in configuration profiles are currently available:
|
||||
|
||||
|
|
|
@ -159,7 +159,7 @@ consistent, is validated, and follows the [community graduation process](https:/
|
|||
Gateways are a special type of component, since multiple ingress and egress gateways can be defined. In the
|
||||
[`IstioOperator` API](/docs/reference/config/istio.operator.v1alpha1/), gateways are defined as a list type.
|
||||
The `default` profile installs one ingress gateway, called `istio-ingressgateway`. You can [inspect the default values
|
||||
for this gateway]({{< github_file >}}/manifests/charts/gateways/istio-ingress/values.yaml). The built-in gateways can be customized just like any other component.
|
||||
for this gateway]({{< github_tree >}}/manifests/charts/gateways/istio-ingress/values.yaml). The built-in gateways can be customized just like any other component.
|
||||
|
||||
{{< warning >}}
|
||||
From 1.7 onward, the gateway name must always be specified when overlaying. Not specifying any name no longer
|
||||
|
|
Loading…
Reference in New Issue