search

kubernetes-sigs / sig-windows-tools

Repository for tools and artifacts related to the sig-windows charter in Kubernetes. Scripts to assist kubeadm and wincat and flannel will be hosted here.
Apache License 2.0
123 stars 123 forks source link

guides/flannel.md FLANNEL_VERSION/v0.21.5 is error #350

Closed 808Mak1r closed 3 months ago

808Mak1r commented 9 months ago

Describe the bug guides/flannel.md FLANNEL_VERSION/v0.21.5 is error tag is v0.21.5 not found in docker hub

image

To Reproduce Steps to reproduce the behavior:

Expected behavior A clear and concise description of what you expected to happen.

Kubernetes (please complete the following information):

Additional context Add any other context about the problem here.

Mik4sa commented 9 months ago

Have a look at #319 :)

808Mak1r commented 9 months ago

Does that mean that this version number can be filled in arbitrarily when you build it yourself, according to your own settings? Can I just use version v0.14.0 then? I see that this one has

Mik4sa commented 9 months ago

That might be to old. I'm not sure. v0.21.5 works for sure (we are using it for months already)

808Mak1r commented 8 months ago

I used v0.21.5, but two pods always to Pulling image and restart container

image image image
Mik4sa commented 8 months ago

I'm not sure. Your Kubernetes version might be too old too. I'm using 1.27.x Also, you need containerd 1.7.x

808Mak1r commented 8 months ago

我不确定。您的 Kubernetes 版本也可能太旧。我正在使用 1.27.x 另外，你需要containerd 1.7.x

Previously I used v1.24 or v1.25 and tried the error: cni plugin not initialised. Now I have successfully built it using v1.23.6 using docker.

image
k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 3 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/sig-windows-tools/issues/350#issuecomment-2117032149): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.