Istio 0.5.1 Tracker

[hklai]

Istio 0.5.0 is plagued by various bugs and we are likely going to cut a 0.5.1 to remedy the critical ones.

ATM the plan is only to cherrypick fixes into 0.5.0. Please add the PRs that must be cherrypicked into 0.5.0 in this issue. Note that only critical bugs will be addressed in patch releases.

A fine print: due to the still changing build system, it is possible that simple cherrypicks may not work. If that is the case, we may cut 0.5.1 at head which can include all fixes, but also increase the risk of opening doors to other bugs. This is only a fall back option.

[linsun]

#2965

#3008
#3010

#3175

[Stono]

Hey, sorry to be a pain in the arse but I don't see how #3099 doesn't fall into this list? Mixer is completely broken

[Stono]

Ah, you're referring to fixes already in place for an immediate cut. Sorry, i'm just at a lose end with a broken deployment.

[linsun]

another one: #3187

[hklai]

@Stono yes if you a think a fix is important enough to be included in 0.5.1, please add the PR here.

[Stono]

#3150

[hklai]

checked with @smawson. Cutting 0.5.1 at master/head is not an option. Only the PRs that can be merged back to the 0.5.0 branch will be included in 0.5.0.

We will carefully inspect the PRs added to this list to ensure their feasibility, and severity.

[rkpagadala]

#3183 is needed on top of #3150

[nmnellis]

Low impact: #3101

[alexkoturanov]

Restore Ingress metrics: #3142

[nmnellis]

Ingress controller not respecting route rules: #3218

[bobbytables]

^ Please.

[myidpt]

K8s workload cert rotation fix: #3155 (Sorry, I committed it to V0.5.1 branch, you can revert it if this doesn't meet the requirements) Fix already in 0.5 pull request #3242

[sureshvis]

Please include - Expose concurrency flag of envoy #3065

[jeffmendoza]

Servicegraph is broken: #3079

[douglas-reid]

I can't recall if #2901 was in 0.5.0, but I'd like to see it included in 0.5.1.

[ldemailly]

As it is feb 7th already we should consider making an early 0.6.0 ? (which would be ~Feb 15 anyway so 6 more days from Feb 9)

On the other hand, exercising and demonstrating our ability to make a patch release is useful

ps: can we call the release branch release-0.5 (like we did for release-0.1 and release-0.2) instead of 0.5.1 ? if we make a 0.5.2 it will likely be on that same branch, the patchlevel varies
(likewise this isn't critical for this but for LTS releases we need a long term multi patch protected branch)

[hklai]

0.6.0 is expected to be cut mid month but it won't be out for another week. There are some demand for fixing the critical bugs in 0.5.0. At the same time, this is a good exercise to test the release pipeline for creating a patch release. Krishna, the release branch should have been 0.5 like Laurent said.

…

On Wed, Feb 7, 2018 at 3:47 PM, Laurent Demailly ***@***.***> wrote: As it is feb 7th already we should consider making an early 0.6.0 ? (which would be Feb 15) On the other hand, exercising and demonstrating our ability to make a patch release is useful ps: can we call the release branch release-0.5 (like we did for 0.1 and 0.2) instead of 0.5.1 ? if we make a 0.5.2 it will likely be on that same branch, the patchlevel varies (likewise this isn't critical for this but for LTS releases we need a long term multi patch protected branch) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3179 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AeRtkBOw4ZnyRvEgKQtzG42AknBGzUkFks5tSjX1gaJpZM4R6AOK> .

[rkpagadala]

@nmnellis I am inclined to not pick up #3101 It is release critical? Why?

[costinm]

#2942

[GregHanson]

#3283
#2970

[nmnellis]

@rkpagadala #3101 can be ignored if you choose, its just that users who deploy 0.5.0 will have to recreate that crd

[rkpagadala]

#3078 * Update proxy SHA to almost latest.

[rlguarino]

What's the target release date for 0.5.1?

[hklai]

Targeting next Monday.

…

On Fri, Feb 9, 2018 at 11:20 AM, Ross Guarino ***@***.***> wrote: What's the target release date for 0.5.1? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3179 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AeRtkMNwqlEEaYD2kqN6C_C74urLaMlRks5tTJqTgaJpZM4R6AOK> .

[rlguarino]

Just to confirm that's Monday the 12th?

[hklai]

Yes

…

On Fri, Feb 9, 2018 at 11:26 AM, Ross Guarino ***@***.***> wrote: Just to confirm that's Monday the 12th? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3179 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AeRtkHZeO3eFUt3P74hK_am5ch0llwN4ks5tTJv1gaJpZM4R6AOK> .

[cmluciano]

docs for minikube setup istio/istio.io#921

[ldemailly]

0.5.1:
mixer's statsd-to-prometheus:
Image: prom/statsd-exporter:v0.5.0

[rkpagadala]

@ldemailly The tags for statsd exporter come from prometheus official docker releases and unrelated to our 0.5.1 version.

https://hub.docker.com/r/prom/statsd-exporter/tags/

[ldemailly]

oh nice coincidence, thanks @rkpagadala - @douglas-reid do you know why we are using the version from 3 months ago vs 1 month ago (0.6.0)

[rlguarino]

It this still happening today?

[hklai]

@rkpagadala is in the process of cutting 0.5.1. right now. Will update this bug when the release artifacts become available.

[douglas-reid]

@ldemailly because we added it ~3 months ago and have not since updated.

[hklai]

0.5.1 is released.
https://github.com/istio/istio/releases/tag/0.5.1

[bobbytables]

Thanks for all of the work on this Istio team. 🍻 We have 0.5.1 in our integration cluster now and we're seeing a few of the bugs we saw go away. Namely, the wildcard routing one is resolved.

[ayj]

FYI - I forgot to include #3036 in the 0.5.1 release cherry-pick list. I've updated the setup instructions to refer uses to download the missing scripts directly from github (see istio/istio.io#983)