.0.8 latest can't pull the docker image

[bfleming-ciena]

I'm sorry if I'm just missing something here but I pulled the 0.8.0 branch and trying to install with helm and getting.

Failed to pull image "docker.io/istio/proxyv2:0.8.latest": rpc error: code = Unknown desc = Error response from daemon: manifest for istio/proxyv2:0.8.latest not found

[ymesika]

You probably already figured it out but you need to provide --set global.tag=latest to your helm install/template command.

It probably should've hold the latest nightly build tag but we still don't have such since 0.8.0 release.

[bfleming-ciena]

Nope, had no clue I needed that. Thanks.

[bfleming-ciena]

Hmm, I trried this for the master branch and got this error.

Warning Failed 10s (x2 over 31s) kubelet, realdev-kube-worker-2 Failed to pull image "docker.io/istio/proxyv2:latest": rpc error: code = Unknown desc = Error response from daemon: manifest for istio/proxyv2:latest not found

helm template install/kubernetes/helm/istio --set global.tag=latest --name istio --namespace istio-system --set tracing.enabled=true | kubectl create -f -

[bfleming-ciena]

Didn't work. I can't remember how I installed htis originally. But when trying to use the github repo I can't install from master or 0.8 now.

helm template install/kubernetes/helm/istio --set global.tag=latest --name istio --namespace istio-system --set tracing.enabled=true | kubectl create -f -

Warning Failed 11s kubelet, realdev-kube-worker-2 Failed to pull image "docker.io/istio/proxyv2:latest": rpc error: code = Unknown desc = Error response from daemon: manifest for istio/proxyv2:latest not found

[bfleming-ciena]

Ok, got it.

Did I miss something somewhere in the docs that indicated I had to set this global.tag option?

helm template install/kubernetes/helm/istio --set global.tag=0.8.0 --name istio --namespace istio-system | kubectl create -f -

[ymesika]

Sorry, right, 0.8.0 tag.

The docs are referring to the released packages.
I believe that there the global.tag is set correctly. Isn't it?

[costinm]

The released packages (0.8.0) need to be labeled with 0.8.latest as well. Unfortunately the release scripts don't do this yet - someone needs to manually label the packages until scripts are updated. The default install from each branch should be able to pick the latest images - the published release is pinned to a version (and may by old/out of date). Master should point to the automatically nightly builds.

…

On Sun, Jun 10, 2018 at 10:40 PM Yossi Mesika ***@***.***> wrote: Sorry, right, 0.8.0 tag. The docs are referring to the released packages <https://github.com/istio/istio/releases>. I believe that there the global.tag is set correctly. Isn't it? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#387 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFI6jK-Iu4P3WgED3F09cTKjCdAgg4Eks5t7gLngaJpZM4UhKzq> .

[ymesika]

@costinm I think it's the images in the docker hub that needs to be tagged with 0.8.latest.
I would do it but I don't think I have permissions.

[costinm]

Yes, someone in rel team needs to do it ( or write a script so this is done automatically for releases )

…

On Mon, Jun 11, 2018 at 9:25 AM Yossi Mesika ***@***.***> wrote: @costinm <https://github.com/costinm> I think it's the images in the docker hub that needs to be tagged with 0.8.latest. I would do it but I don't think I have permissions. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#387 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFI6qmZxwIErVNUV87LoYoFGNt72UtDks5t7pn8gaJpZM4UhKzq> .

[sakshigoel12]

cc @hklai

[hklai]

I doubt anyone had given much thought about installing from a release branch instead of using the release artifacts.

It is unclear to me if 0.8.latest is latest cutting edge build or latest stable build. If former, we currently do not even push to docker hub.

Similarly, we do not label "latest" in the daily release on master either.

[costinm]

We do label latest in nightly builds in circleci - and we did put quite a bit of thought into this. And for master using the helm has worked for quite a while, based on the nightly label from circleci. The 'release artifacts' will probably not include helm charts - the plan for 1.0 is to have the helm charts in the helm repositories, so helm users can install Istio without having to download a release, with just "helm install", as any other helm application. Users who use 'helm template' or 'istioctl gen-deploy' may still need to download the release, so will users who manually inject.

…

On Tue, Jun 12, 2018 at 7:07 PM Andy Lai ***@***.***> wrote: I doubt anyone had given much thought about installing from a release branch instead of using the release artifacts. It is unclear to me if 0.8.latest is latest cutting edge build or latest stable build. If former, we currently do not even push to docker hub. Similarly, we do not label "latest" in the daily release on master either. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#387 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFI6jbBZ5-yFbqtO3DtRbeZKHNJ_BXSks5t8HPdgaJpZM4UhKzq> .

[costinm]

Sorry - helm charts will be included in release artifacts for helm tempate users only - users of tiller (full helm) will not require the templates from the release.

…

On Tue, Jun 12, 2018 at 11:25 PM Costin Manolache ***@***.***> wrote: We do label latest in nightly builds in circleci - and we did put quite a bit of thought into this. And for master using the helm has worked for quite a while, based on the nightly label from circleci. The 'release artifacts' will probably not include helm charts - the plan for 1.0 is to have the helm charts in the helm repositories, so helm users can install Istio without having to download a release, with just "helm install", as any other helm application. Users who use 'helm template' or 'istioctl gen-deploy' may still need to download the release, so will users who manually inject. On Tue, Jun 12, 2018 at 7:07 PM Andy Lai ***@***.***> wrote: > I doubt anyone had given much thought about installing from a release > branch instead of using the release artifacts. > > It is unclear to me if 0.8.latest is latest cutting edge build or latest > stable build. If former, we currently do not even push to docker hub. > > Similarly, we do not label "latest" in the daily release on master either. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#387 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAFI6jbBZ5-yFbqtO3DtRbeZKHNJ_BXSks5t8HPdgaJpZM4UhKzq> > . >

[hklai]

I can't say it is well thought of when something depends on circle nightly builds that is different from the regular daily releases maintained by the release team.

If we continue that approach circle should probably build nightly from release-0.8 (and other release branches) and label 0.8.latest (and newer releases later).

Otherwise we should kill circle nightly and make sure daily releases label accordingly as well.

And with Tiller, I suppose it can just take the release label (i.e. 0.8.0) without requiring the templates from the release, right?