-
Notifications
You must be signed in to change notification settings - Fork 48
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
Update to Ubuntu 18.04 and Kubernetes 1.15.2 #50
Conversation
Thanks @pfisterer for the contribution, it was very welcome! I have successfully tested it in my environment. We can now continue to work on master to clean these kubenet issues. I read in a few places that kubenet was going to be deprecated but couldn't find how it was supposed to be replaced. |
Thanks @ctrlaltdel for accepting this PR. Regarding kubenet: as far as I know, kubenet is limited in terms of NetworkPolicies, etc. So, migrating to a CNI-based network (e.g., kube-router) might be interesting. |
Dear infraly team,
I've spent some time working on updating this Ansible playbook to use Ubuntu 18.04 and Kubernetes 1.15.2. As far as I can tell, everything works by now and I've successfully deployed Hadoop and Binderhub after running this playbook.
I hope you find these (batch full of) changes sensible as a starting point for improvements.
Best,
Dennis
Original text from the first PR:
Dear infraly team,
Here is my take on #49. This basically solves the issue that services of
Type: LoadBalancer
are not reachable from outside the cluster. Only after allowing ingress traffic in the sg-k8s-nodes security group, everything works as expected.However, this still does not resolve the issue that inter-pod communication does not work as expected (cf. #49 (comment)).