feat(docs): added KubeVIP installation path - #76
Open
frabru99 wants to merge 3 commits into
Open
Conversation
✅ Deploy Preview for goyaki ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
frabru99
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull request significantly expands the
guides/advanced.mddocumentation to provide a comprehensive, side-by-side guide for setting up a high availability Kubernetes cluster using eitherkeepalivedorkube-vipas the control plane virtual IP solution. The guide is reorganized to clearly present both approaches, their pros and cons, and step-by-step instructions for each path, including setup, bootstrap, and cleanup procedures.Major documentation enhancements:
keepalivedandkube-vip, including a summary table and pros/cons for each. [1] [2]keepalived) and Path B (kube-vip), with clear navigation and resumption points for common steps. [1] [2]Expanded instructions for both approaches:
For
keepalived:kubelivedtokeepalived.For
kube-vip:Additional improvements:
curlandjqare needed on the bootstrap machine for thekube-vippath.References:
[1] [2] [3] [4] [5] [6] [7] [8]