mirror of https://github.com/istio/istio.io.git
Remove uses of istio-demo.yaml (#5311)
* Remove uses of istio-demo.yaml * broken link
This commit is contained in:
Frank Budinsky
Istio Automation
parent
cdd8d7f50f
commit
4bf2fb2e5e
|
|
@ -99,7 +99,7 @@ $ kubectl apply -f https://preliminary.istio.io/operator-profile-minimal.yaml
|
|||
{{< warning >}}
|
||||
This document is a work in progress. Expect verification steps for each of the profiles to
|
||||
vary from these verification steps. Inconsistencies will be resolved prior to the publishing of
|
||||
Istio 1.4. Until that time, these verification steps only apply to the `profile-istio-demo.yaml` profile.
|
||||
Istio 1.4. Until that time, these verification steps only apply to the `demo` profile.
|
||||
{{< /warning >}}
|
||||
|
||||
1. Ensure the following Kubernetes services are deployed and verify they all have an appropriate `CLUSTER-IP` except the `jaeger-agent` service:
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ sleep-64c6f57bc8-f5n4x 2/2 Running 0 24s
|
|||
### Automatic sidecar injection
|
||||
|
||||
Sidecars can be automatically added to applicable Kubernetes pods using a
|
||||
[mutating webhook admission controller](https://kubernetes.io/docs/admin/admission-controllers/) provided by Istio.
|
||||
[mutating webhook admission controller](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/) provided by Istio.
|
||||
|
||||
{{< tip >}}
|
||||
While admission controllers are enabled by default, some Kubernetes distributions may disable them. If this is the case, follow the instructions to [turn on admission controllers](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#how-do-i-turn-on-an-admission-controller).
|
||||
|
|
|
|||
|
|
@ -151,7 +151,7 @@ control plane with mutual TLS disabled installed, please delete it. For example,
|
|||
you followed the quick start:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete -f install/kubernetes/istio-demo.yaml
|
||||
$ istioctl manifest generate --set profile=demo | kubectl delete -f -
|
||||
{{< /text >}}
|
||||
|
||||
And wait for everything to have been deleted, i.e., there is no pod in the control plane namespace (`istio-system`):
|
||||
|
|
|
|||
|
|
@ -3,9 +3,12 @@ title: Why are my requests not being traced?
|
|||
weight: 30
|
||||
---
|
||||
|
||||
Since Istio 1.0.3, the default sampling rate for tracing has been reduced to 1% when installing Istio using the Helm chart. This means that only 1 out of 100 trace
|
||||
instances captured by Istio will be reported to the tracing backend. The sampling rate in the `istio-demo.yaml` is still set to 100%. See
|
||||
[this section](/docs/tasks/observability/distributed-tracing/overview/#trace-sampling) for more information on how to set the sampling rate.
|
||||
Since Istio 1.0.3, the sampling rate for tracing has been reduced to 1% in the `default`
|
||||
[configuration profile](/docs/setup/additional-setup/config-profiles/).
|
||||
This means that only 1 out of 100 trace instances captured by Istio will be reported to the tracing backend.
|
||||
The sampling rate in the `demo` profile is still set to 100%. See
|
||||
[this section](/docs/tasks/observability/distributed-tracing/overview/#trace-sampling)
|
||||
for more information on how to set the sampling rate.
|
||||
|
||||
If you still do not see any trace data, please confirm that your ports conform to the Istio [port naming conventions](/faq/traffic-management/#naming-port-convention) and that the appropriate container port is exposed (via pod spec, for example) to enable
|
||||
traffic capture by the sidecar proxy (Envoy).
|
||||
|
|
|
|||
|
|
@ -11,7 +11,8 @@ Citadel uses a flag `max-workload-cert-ttl` to control the maximum lifetime for
|
|||
workloads. The default value is 90 days. If `workload-cert-ttl` on Citadel or node agent is greater than
|
||||
`max-workload-cert-ttl`, Citadel will fail issuing the certificate.
|
||||
|
||||
Modify the `istio-demo.yaml` file to customize the Citadel configuration.
|
||||
You can modify a [generated manifest](/docs/setup/install/operator/#generate-a-manifest-before-installation)
|
||||
file to customize the Citadel configuration.
|
||||
The following modification specifies that the Istio certificates for workloads running in Kubernetes
|
||||
has 1 hours lifetime. Besides that, the maximum allowed Istio certificate lifetime is 48 hours.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,11 @@ weight: 95
|
|||
keywords: [mysql,mtls]
|
||||
---
|
||||
|
||||
You may find MySQL can't connect after installing Istio. This is because of `PERMISSIVE` mode which is enabled in `istio-demo.yaml` by default, does not work with MySQL. You may see error messages such as "ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0".
|
||||
You may find MySQL can't connect after installing Istio. This is because of `PERMISSIVE` mode,
|
||||
which is enabled in the `demo` [configuration profile](/docs/setup/additional-setup/config-profiles/),
|
||||
does not work with MySQL.
|
||||
You may see error messages such as `ERROR 2013 (HY000): Lost connection to MySQL server at
|
||||
'reading initial communication packet', system error: 0`.
|
||||
|
||||
There have two options to solve the problem.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue