HA K8s Docs #392
Open
HA K8s Docs #392
Conversation
This file contains 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
Signed-off-by: Stephen Reaves <[email protected]>
jepio
reviewed
Feb 14, 2025
content/docs/latest/container-runtimes/high-availability-kubernetes.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Stephen Reaves <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Documentation for running a highly available kubernetes cluster
This doc runs through a complex example using the kubernetes sysext. It involves multiple kubernetes configurations like swapping container runtimes and CNIs, as well as more advanced ignition configurations like running static pods via Quadlet and creating a hierarchy of configs. This also demonstrates how to use a make file to spin up multiple distinct flatcar VMs in a controlled manner.
This doc may need to be updated once flatcar/sysext-bakery#114 gets merged.
Also, this is my first time writing technical documentation of this nature so please feel free to critique this technically, grammatically, or in any other manner I may have missed.