[WIP] improve ipv6-only cluster function #319
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ingenTLS
andgenTokenTLS
. 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;
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.