so that users don't need to download istio archive.
confirmed these files exist for me:
```
~/istio-fetch/istio ⌚ 13:55:51
$ ls
Chart.yaml templates values-istio-remote.yaml
README.md values-istio-demo-auth.yaml values-istio-sds-auth.yaml
charts values-istio-demo-common.yaml values.yaml
example-values values-istio-demo.yaml
requirements.yaml values-istio-minimal.yaml
```
* Implement consitent term for installation related flows
Replaced "paths", "instructions", and other similar terms
with the term "flow" to ensure readers from different
Geos are not confused by multiple meanings or idiomatic use.
Signed-off-by: Rigs Caballero <grca@google.com>
* Implement consistent term for installation related flows
Replaced "paths", "instructions", and other similar terms
with the term "flow" to ensure readers from different
Geos are not confused by multiple meanings or idiomatic use.
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix typos and lint issue.
Signed-off-by: Rigs Caballero <grca@google.com>
* Clarify that egress gateway isn't present with Helm
Values.yaml has been updated to disable the egress gateway if the Helm installation option is used. Currently, we don't indicate that egress gateway should not be present if you used Helm.
* Clarify that egress gateway is disabled by default in Helm
* CR comments. Also moved notice up since it covers both services and podsw
* Cleand up wording
* Added links to relevant installer sections for egress gateway
* Added links to appropriate sections
* added blank line
* Paths have changed. Updated link
* Removed section as per code review comments
* add access log task
* change config map to configuration map to prevent spelling errors
* add an empty line between two boilerplates
seems to be required, otherwise a redundant <p> tag is generated
* make the task's title Getting Envoy's Access Logs
* mind escaping -> be sure to escape
* check the log of sleep, httpbin -> check sleep's, httpbin's log
* change -> customize
* to do it, edit -> by editing
* use a separate gateway for bookinfo in the case of multiple hosts
* set the name parameter to be "istio" instead of "istio-ingressgateway"
Since the original istio-ingressgateway was deployed with the name parameter "istio".
Otherwise, the following error will be received:
The Deployment "istio-ingressgateway" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"chart":"gateways", "heritage":"Tiller", "istio":"ingressgateway", "release":"istio-ingressgateway", "app":"istio-ingressgateway"}: `selector` does not match template `labels`
The problem is that the "release" label contains the name parameter of helm template,
and if this label will not match in the new and the original deployments of istio-ingressgateway,
kubectl apply will fail.
* add ingress troubleshooting section
* it does not arrive to the Istio -> it does not arrive to the ingress gateway
* fix a link
* remove checking the log since access log will be removed in 1.1
* you have no other Kubernetes Ingress resources -> you have no Kubernetes Ingress resources
Andra Cismaru