Conversation
|
Can you also update the |
|
Sure. This is the PR to master though, which is already updated to 1.4. Will add that in the cherry pick branch. |
Sure, you're right. |
Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
|
/test lint_istio.io |
|
Added do not merge label in this PR so we can merge it on release. |
|
@brian-avery Note that this will need to be merged into release-1.3 in order to be published to istio.io. And note that as part o merging the PR to that branch, you also need to update the full_version field in data/args.yaml. |
|
@geeknoid Understood. Thanks. Added the cherry-pick to 1.3 label already, so as soon as this merges, that PR will open. Master already has data/args updated for 1.4 so I'm going to update the cherry-pick branch with the change. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
@googlebot I fixed it |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
kyessenov
left a comment
There was a problem hiding this comment.
nothing from policy&telemetry
|
The tests on 1.3.3 look good. We can go ahead with the release. |
* 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
* 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
* 1.3.3 release notes (#5122) * 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 * Update full_version to 1.3.3
* 1.3.3 release notes (istio#5122) * 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 * Update full_version to 1.3.3
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ x] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure