Conversation
* clarify the release note due to change in auto protocol detection yesterday * add link
* manual PR for 4976 * fix lint
Signed-off-by: Douglas Reid <dougreid@google.com>
* fix multi cluster dns docs * fix multi cluster dns docs * ignore multicast spelling check
Signed-off-by: Venil Noronha <veniln@vmware.com>
* Remove usages of curl inside istio-proxy Distroless builds of Istio do not contain curl, so we should not tell users to use it. Pilot-agent handles this functionality for us
* Added blog for monitoring external service traffic In release 1.3 we added support for monitoring traffic to external services which are allowed or get blocked. This blog explains how to use these metrics to get the host names/IP addresses for these external services.
* manual merge of #5025 * fix link to Envoy's access logging
* release announcement and blog * fix lint * update version
* fix link issue * space * use the link frank suggested * Update content/en/news/2019/istio-security-2019-005/index.md
cc @lambdai who pointed out this is not accurate
* Istioctl describe op guide * Fix lint * spelling * small corrections * wording tweak
* Clarify relationship between pods and workloads * Update content/en/docs/reference/glossary/pod.md Co-Authored-By: Martin Taillefer <geeknoid@users.noreply.github.com>
In release this is changed to below: ```yaml global: # Default hub for Istio images. # Releases are published to docker hub under 'istio' project. # Daily builds from prow are on gcr.io hub: docker.io/istio # Default tag for Istio images. tag: 1.3.2 ``` Not sure how to fix, but having the dev defaults here may be misleading.
* 1.3.3 release notes * 1.3.3 release notes * Apply suggestions from code review Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info> * Added note regarding Envoy crash
|
@rlenglet: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
istio-testing
added
needs-rebase
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
googlebot
added
the
cla: no
rlenglet
force-pushed
the
release-1-3-3
branch
from
40e2979 to
a992280
Compare
|
@rlenglet: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
11 participants
Cherry-pick 1.3.3 release notes from #5122.
Update the
full_version.[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure