baremetal: Expand on networking documentation. #1981
Conversation
The baremetal VM actually has a higher VRRP priority than the control plane nodes. This ensures that the VIP does not move until the API is fully functional on the control plane nodes. The signal for this is when the bootstrap VM is stopped. That will leave only the lower priority keepalived instances running that reside on the control plane nodes.
openshift-ci-robot
added
the
size/L
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, russellb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
@russellb: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
4 participants
This patch continues to expand the networking documentation for the
baremetalplatform. The most significant additions in this PR are to describe the internal DNS automation, API load balancing, and high availability for ingress.