weave icon indicating copy to clipboard operation
weave copied to clipboard

Typo In weave latest release?

Open jamsman94 opened this issue 3 years ago • 4 comments

What you expected to happen?

Weave installed successfully.

What happened?

weave gave me a yaml containing the wrong image, causing the probelm

How to reproduce it?

I got the yaml from https://cloud.weave.works/k8s/net?k8s-version=Q2xpZW50IFZlcnNpb246IHZlcnNpb24uSW5mb3tNYWpvcjoiMSIsIE1pbm9yOiIxOSIsIEdpdFZlcnNpb246InYxLjE5LjMiLCBHaXRDb21taXQ6IjFlMTFlNGEyMTA4MDI0OTM1ZWNmY2IyOTEyMjI2Y2VkZWFmZDk5ZGYiLCBHaXRUcmVlU3RhdGU6ImNsZWFuIiwgQnVpbGREYXRlOiIyMDIwLTEwLTE0VDEyOjUwOjE5WiIsIEdvVmVyc2lvbjoiZ28xLjE1LjIiLCBDb21waWxlcjoiZ2MiLCBQbGF0Zm9ybToibGludXgvYW1kNjQifQpTZXJ2ZXIgVmVyc2lvbjogdmVyc2lvbi5JbmZve01ham9yOiIxIiwgTWlub3I6IjE5IiwgR2l0VmVyc2lvbjoidjEuMTkuMyIsIEdpdENvbW1pdDoiMWUxMWU0YTIxMDgwMjQ5MzVlY2ZjYjI5MTIyMjZjZWRlYWZkOTlkZiIsIEdpdFRyZWVTdGF0ZToiY2xlYW4iLCBCdWlsZERhdGU6IjIwMjAtMTAtMTRUMTI6NDE6NDlaIiwgR29WZXJzaW9uOiJnbzEuMTUuMiIsIENvbXBpbGVyOiJnYyIsIFBsYXRmb3JtOiJsaW51eC9hbWQ2NCJ9Cg== , which is generated from the https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n'). This yaml contains a file with an image: 'ghcr.io/weaveworks/launcher/weave-kube:2.8.1', which simply does not exist

Anything else we need to know?

Versions:

$ weave version
$ docker version
$ uname -a
$ kubectl version

Logs:

$ docker logs weave

or, if using Kubernetes:

$ kubectl logs -n kube-system <weave-net-pod> weave

Network:

$ ip route
$ ip -4 -o addr
$ sudo iptables-save

jamsman94 avatar Nov 16 '21 14:11 jamsman94

It seems that images of weave-kube and weave-npc on GitHub container registry have no tag 2.8.1 but git-34de0b10a69c. They have 2.8.1 tag on DockerHub.

Package of weave-kube: https://github.com/weaveworks/launcher/pkgs/container/launcher%2Fweave-kube Package of weave-npc: https://github.com/weaveworks/launcher/pkgs/container/launcher%2Fweave-npc

https://cloud.weave.works/k8s/net may need to correct container registry or tag.

flyer103 avatar Nov 16 '21 20:11 flyer103

it is critical as many of our workload start getting failed when new image try to pull of weave in K8 cluster

nvermalulu avatar Nov 17 '21 10:11 nvermalulu

+1

workaround:

curl -L https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n') -o weave.yaml

sed -i 's/ghcr.io\/weaveworks\/launcher/docker.io\/weaveworks/g' weave.yaml

kubectl -f weave.yaml apply

wuestkamp avatar Nov 17 '21 16:11 wuestkamp

Or

sed -e 's/:2.8.1/:git-34de0b10a69c/'

pohly avatar Nov 17 '21 18:11 pohly