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

Service of type ClusterIP timeouts on Ubuntu 22.04 using 1.23/stable #3149

Closed
usersina opened this issue May 13, 2022 · 3 comments
Closed

Service of type ClusterIP timeouts on Ubuntu 22.04 using 1.23/stable #3149

usersina opened this issue May 13, 2022 · 3 comments

Comments

@usersina
Copy link

Summary

Services pointing to Pods deployed to a worker node running on Ubuntu 22.04 always timeouts. Ubuntu 20.04 works without issues. See the screenshots below.

What Should Happen Instead?

Services pointing to Pods deployed Ubuntu 22.04 should resolve correctly.

Machines setup

I used 3 virtual machines on the same private network from a third party cloud provider for this setup, below is the hostname of each machine.

  • dev-kube-controller running Ubuntu 20.04
  • dev-kube-worker-1 running Ubuntu 20.04
  • dev-kube-worker-2 running Ubuntu 22.04

Reproduction Steps

  1. Install MicroK8s on each of the machines normally.
  2. Run the add command from dev-kube-controller
microk8s add-node --token <my-32-length-string> --token-ttl 300
  1. Execute the join command from dev-kube-worker-1 and dev-kube-worker-2
microk8s join <ip-of-dev-kube-controller>:25000/<my-32-length-string> --worker
  1. This is besides the point, but I always get this issue at this step no matter which version of Ubuntu I have, so I apply this fix for every node separately.
  2. Apply the following manifests (minus the ingress).

Introspection Report

inspection-report-20220513_114105.tar.gz

Additional context

I tried using Ubuntu 22.04 for all virtual machines. Running microk8s inspect this way shows a warning that I need to sudo iptables -P FORWARD ACCEPT which I did. I also did a sudo apt-get install iptables-persistent and a reboot for all virtual machines but the issue still persists. However, the warning doesn't show up anymore when running microk8s inspect.

Some screenshots

dev-kube-controller
dev-kube-worker-1
dev-kube-worker-2

Note that if I were to add a dev-kube-worker-3 running Ubuntu 20.04, it works without any issues.

Are you interested in contributing with a fix?

Sure, if I can help in any way!

@RobinJespersen
Copy link

sounds familiar to me, maybe one of the suggested solutions here work for you: #3133

@usersina
Copy link
Author

Here are some more details about how the network interfaces are configured

kube-worker-1 (the one that works)
2022-05-17_102902
kube-worker-2 (the one that doesn't work)
2022-05-17_102849

@usersina
Copy link
Author

Re-installing Ubuntu 22.04 as well as MicroK8s 1.24 solves this issue apparently. I'm not sure but I tried the setup from scratch and it all works now.

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