-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Clean up the kubeadm high availability instructions. Fixes Issue 15284 #15411
Conversation
Welcome @rcythr! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Deploy preview for kubernetes-io-master-staging ready! Built with commit a586b71 https://deploy-preview-15411--kubernetes-io-master-staging.netlify.com |
… specific method for setting up a load balancer. Removed extra space. Fixed indentation.
/sig cluster-lifecycle |
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.
@rcythr Thanks for this PR!
I'm ok with the change, with only a minor nit
|
||
- Make sure the address of the load balancer always matches | ||
the address of kubeadm's `ControlPlaneEndpoint`. | ||
- Check if your deployment environment has a highly available load balancer, and use that if possible. Otherwise, setup a TCP forwarding load balancer (such as [HAProxy](http://www.haproxy.org/)). Make sure to follow the documentation to properly setup this load balancer in a highly-available configuration. Otherwise, your load balancer becomes a single point of failure. |
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.
After re-reading, I think this sentence should become the first point (first check what you have, second create). Also, plese change "Otherwise, setup a TCP forwarding load balancer (such as HAProxy)" into Otherwise, "select a TCP forwarding load balancer such as HAProxy", in order to be more in line with the "check what you have" message
@rcythr Feedback reasonable to you? |
@fabriziopandini How about this? Sorry for the delay, I've been swamped this week. @tengqm Thanks for the reminder. |
@rcythr thanks for the updates! I'm ok with the changes, I leave to @neolit123 giving the final green light |
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
/assign @kbarnard10 |
/hold In light of kubernetes/kubeadm#1685 we should revise our advice to be more explicit about what kind of things the LB needs to be able to do. Azure's LB currently cannot fulfil those requirements. |
…want to get into details of specific LB implementation. Added HA LB as a required piece of infrastructure where it belongs.
New changes are detected. LGTM label has been removed. |
@neolit123 @fabriziopandini I modified the text to make the HA LB a requirement instead of trying to provide steps for setting it up -- we can't get into details about the specific implementations. I added a note about hairpin NAT in light of kubernetes/kubeadm#1685 What do you think? |
/hold cancel |
@@ -40,6 +40,7 @@ For both methods you need this infrastructure: | |||
the masters | |||
- Three machines that meet [kubeadm's minimum | |||
requirements](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#before-you-begin) for the workers | |||
- A highly available load balancer that operates at Layer 4 (such as one provided by a cloud provider, or [HAProxy](http://www.haproxy.org/)) with it's own name in DNS. The load balancer should be configured to forward the apiserver port (default: 6443) on the load balancer to the apiserver port on all control plane nodes. Before using a cloud provider provided load balancer, double check the documentation for [NAT hairpinning](https://en.wikipedia.org/wiki/Hairpinning) support. |
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.
we should probably mention HTTPS and health checks here.
@ereslibre @fabriziopandini how would you word that?
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.
I would say that even if it's a layer 4 LB it should have the ability to perform HTTPS health checks (even if the certificate chain is ignored) against every apiserver /healthz
endpoint. That way it will remove from the active pool unhealthy apiservers.
content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md
Outdated
Show resolved
Hide resolved
…h-availability.md Fixed it's vs its. Co-Authored-By: Rafael Fernández López <[email protected]>
@rcythr 👋 Any updates? |
@rcythr 👋 Please feel free to /close |
@zacharysarah: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes #15284
/assign @fabriziopandini @neolit123