mirror of https://github.com/istio/istio.io.git
removed istioctl profile cmd references (en) (#15913)
* removed istioctl profile cmd references (en) istioctl profile command was removed in PR https://github.com/istio/istio/pull/52468 updating docs with these changes. * link to ingress gateway values file Co-authored-by: Craig Box <craig.box@gmail.com> * link to built in profiles --------- Co-authored-by: Craig Box <craig.box@gmail.com>
This commit is contained in:
Adarsh K Kumar
GitHub
parent
0d13596023
commit
977fa70e26
|
|
@ -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 and then further
|
||||
You can start with one of [Istio’s built-in configuration profiles]({{< github_file >}}/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:
|
||||
|
||||
|
|
@ -22,7 +22,6 @@ for your specific needs. The following built-in configuration profiles are curre
|
|||
This profile is recommended for production deployments and for
|
||||
{{< gloss "primary cluster" >}}primary clusters{{< /gloss >}} in a
|
||||
[multicluster mesh](/docs/ops/deployment/deployment-models/#multiple-clusters).
|
||||
You can display the default settings by running the `istioctl profile dump` command.
|
||||
|
||||
1. **demo**: configuration designed to showcase Istio functionality with modest resource requirements.
|
||||
It is suitable to run the [Bookinfo](/docs/examples/bookinfo/) application and associated tasks.
|
||||
|
|
|
|||
|
|
@ -158,16 +158,8 @@ 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:
|
||||
|
||||
{{< text bash >}}
|
||||
$ istioctl profile dump --config-path components.ingressGateways
|
||||
$ istioctl profile dump --config-path values.gateways.istio-ingressgateway
|
||||
{{< /text >}}
|
||||
|
||||
These commands show both the `IstioOperator` and Helm settings for the gateway, which are used together to define the
|
||||
generated gateway resources. The built-in gateways can be customized just like any other component.
|
||||
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.
|
||||
|
||||
{{< warning >}}
|
||||
From 1.7 onward, the gateway name must always be specified when overlaying. Not specifying any name no longer
|
||||
|
|
|
|||
|
|
@ -106,83 +106,6 @@ to install the `demo` profile:
|
|||
$ istioctl install --set profile=demo
|
||||
{{< /text >}}
|
||||
|
||||
## Display the list of available profiles
|
||||
|
||||
You can display the names of Istio configuration profiles that are
|
||||
accessible to `istioctl` by using this command:
|
||||
|
||||
{{< text bash >}}
|
||||
$ istioctl profile list
|
||||
Istio configuration profiles:
|
||||
default
|
||||
demo
|
||||
empty
|
||||
minimal
|
||||
openshift
|
||||
preview
|
||||
remote
|
||||
{{< /text >}}
|
||||
|
||||
## Display the configuration of a profile
|
||||
|
||||
You can view the configuration settings of a profile. For example, to view the setting for the `demo` profile
|
||||
run the following command:
|
||||
|
||||
{{< text bash >}}
|
||||
$ istioctl profile dump demo
|
||||
components:
|
||||
egressGateways:
|
||||
- enabled: true
|
||||
k8s:
|
||||
resources:
|
||||
requests:
|
||||
cpu: 10m
|
||||
memory: 40Mi
|
||||
name: istio-egressgateway
|
||||
|
||||
...
|
||||
{{< /text >}}
|
||||
|
||||
To view a subset of the entire configuration, you can use the `--config-path` flag, which selects only the portion
|
||||
of the configuration under the given path:
|
||||
|
||||
{{< text bash >}}
|
||||
$ istioctl profile dump --config-path components.pilot demo
|
||||
enabled: true
|
||||
k8s:
|
||||
env:
|
||||
- name: PILOT_TRACE_SAMPLING
|
||||
value: "100"
|
||||
resources:
|
||||
requests:
|
||||
cpu: 10m
|
||||
memory: 100Mi
|
||||
{{< /text >}}
|
||||
|
||||
## Show differences in profiles
|
||||
|
||||
The `profile diff` sub-command can be used to show the differences between profiles,
|
||||
which is useful for checking the effects of customizations before applying changes to a cluster.
|
||||
|
||||
You can show differences between the default and demo profiles using these commands:
|
||||
|
||||
{{< text bash >}}
|
||||
$ istioctl profile diff default demo
|
||||
gateways:
|
||||
egressGateways:
|
||||
- - enabled: false
|
||||
+ - enabled: true
|
||||
...
|
||||
k8s:
|
||||
requests:
|
||||
- cpu: 100m
|
||||
- memory: 128Mi
|
||||
+ cpu: 10m
|
||||
+ memory: 40Mi
|
||||
strategy:
|
||||
...
|
||||
{{< /text >}}
|
||||
|
||||
## Generate a manifest before installation
|
||||
|
||||
You can generate the manifest before installing Istio using the `manifest generate`
|
||||
|
|
|
|||
Loading…
Reference in New Issue