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

[WIP] improve ipv6-only cluster function #319

Closed
wants to merge 1 commit into from

Conversation

uablrek
Copy link

@uablrek uablrek commented Apr 10, 2019

This PR is a partial fix for #284 .

This PR adds the ipv6 localhost address [::1]:6445 to be used on an ipv6-only cluster instead of the ipv4 127.0.0.1.

It also adds the ipv6 localhost [::1] to the certificates, both in genTLS and genTokenTLS. This is done always, even in an ipv4-only cluster. Since it is localhost I did not think there will be any security issues(?).

Remaining problem

Access to the k8s api does not work from within a pod. The service endpoint for the kubernetes service is;

# kubectl get service kubernetes
NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   fd00:4000::1   <none>        443/TCP   2m16s
# kubectl get endpoints kubernetes
NAME         ENDPOINTS    AGE
kubernetes   [::1]:6445   49s

which I think is correct but from within a pod it is not possible to connect to the kubernetes service ip (connection hangs). From main netns it works fine.

I am a bit stuck so I publish this PR with hope of aid from others.

@deniseschannon deniseschannon changed the title improve ipv6-only cluster function [WIP] improve ipv6-only cluster function Apr 11, 2019
@uablrek
Copy link
Author

uablrek commented Nov 21, 2019

Obsolete due to dual-stack support in k8s

@uablrek uablrek closed this Nov 21, 2019
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

Successfully merging this pull request may close these issues.

1 participant