-
Notifications
You must be signed in to change notification settings - Fork 234
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
Divert kube-api access via SSH tunnel #714
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
c413608
to
c87f5d2
Compare
/test pull-kubeone-test |
c869e48
to
40e4e0e
Compare
/retest |
40e4e0e
to
afca9a7
Compare
/retest |
/retest |
1 similar comment
/retest |
Signed-off-by: Artiom Diomin <[email protected]>
afca9a7
to
4ec0c60
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: b30a487a3a2c71c71bec45ee1c7ffe14e2a44711
|
Those look like some weird flakes. |
What this PR does / why we need it:
KubeOne operator may create kube-API loabdalancer as internal, only accessible from inside the VPC or internal-perimeter, so KubeOne will divert all kube-API access over SSH tunnel from the leader node which guaranteed to have direct kube-api access (since kubelet need to communicate with it).
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #659