* add envoy version info into troubleshooting guide
* add envoy version info into troubleshooting guide
* add envoy version info into troubleshooting guide
Remove warning that prior to Istio 0.8 Helm was unstable.
Since we are on 1.0, and can expect people to upgrade from 0.8,
this warning doesn't seem relevant.
Also, Helm upgrade from 0.8 to 1.0 has been validated. Also
remove that warning.
* Edit Kubernetes Quick Start for clarity.
This edit includes among other changes:
* Consistent use of markup, line length, and command formatting.
* Grammar, spelling, and other language fixes.
* Use of ordered lists for steps.
* New clear headings for installation options.
Signed-off-by: rcaballeromx <grca@google.com>
* Fix linter issues on Kubernetes QS edit.
Signed-off-by: rcaballeromx <grca@google.com>
* Fix indentation to fix ordered lists.
Trying to figure out the space in links issue. So far it looks like a false
positive.
Signed-off-by: rcaballeromx <grca@google.com>
* Fix links and code blocs for lint.
Signed-off-by: rcaballeromx <grca@google.com>
* Remove in-line markup from links.
Signed-off-by: rcaballeromx <grca@google.com>
* Fix code-block indentation and spelling lint.
Signed-off-by: rcaballeromx <grca@google.com>
* Rewrote link text to avoid spelling lint.
Signed-off-by: rcaballeromx <grca@google.com>
* Update index.md
* Delete "basic access control" and "secure access control" pages.
These pages were there before Istio RBAC was introduced. We should
remove them now to avoid confusion.
* Added aliases for deleted pages.
Istio intends to lead with automatic sidecar injection and
as such, there is no good rationale to document how to turn
sidecar injection off. Still, as a followon PR, it may make
sense to document 5-7 different customization scenarios.
ingress v1 is gone - no sense describing it here.
* add ./ to the script to generate certificates
* add a step to verify the subject of the ingress gateway certificate
* add a step to verify the subject of the CA certificate
put the mutual TLS troubleshooting into a separate subsection
* fix the level of the mutual TLS troubleshooting
* remove redundant empty lines
* verify the subject is correct -> verify that the subject is correct
* another case: verify the subject is correct -> verify that the subject is correct