Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After installing to Kubernetes v1.31.2 running on Talos 1.8.3, pods with the 'kube-system' namespace are still running #2124

Open
fabriziogiudici opened this issue Nov 28, 2024 · 3 comments

Comments

@fabriziogiudici
Copy link

fabriziogiudici commented Nov 28, 2024

I'm installing Flannel on Kubernetes v1.31.2 running on Talos 1.8.3.

Expected Behavior

I've followed the documentation (paragraph "Deploying Flannel with kubectl") and ran:

kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml

Flannel pods should run fine after this.

Current Behavior

The Flannel pods with the kube-flannel namespace started, but there were other three pods with the kube-system namespace already present on Kubernetes. They are still present after the step described above. This causes troubles and makes the new Flannel pods to randomly fail.

Possible Solution

THIS WAS EDITED - at first I thought the workaround fixed it and asked for a confirmation, but I later realized it is not working.

I tried to fix the problem by explicitly removing the old pods before the Flannel installation:

kubectl delete -n kube-system daemonset.apps/kube-flannel

Actually the bogus flannel elements are removed, but they reappear after a restart.

Your Environment

  • Flannel version: latest
  • Kubernetes version (if used): v1.31.2
  • Operating System and version: Talos v.1.8.3
@thomasferrandiz
Copy link
Contributor

It sounds like flannel was already installed in your cluster before you applied the manifest.

What method did you use to deploy the kubernetes cluster?

@fabriziogiudici
Copy link
Author

fabriziogiudici commented Nov 29, 2024

The Talos distribution already contains Kubernetes and, as far as I was able to investigate, flannel is already installed, v0.25.7. I suppose that v0.26.0 changed the namespace from kube-system to kube-flannel, hence the problem.
I think that at this point I can just skip the explicit installation of flannel, since I don't think I need the latest features. Probably the next version of Talos will align with a newer flannel.

@thomasferrandiz
Copy link
Contributor

We started using the kube-flannel namespace in v0.19.0 in 2022.
It looks like Talos is not following the upstream manifest closely.

In that case, you would need to manually uninstall flannel before installing it again but as you said there is no major new feature in v0.26.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants