fix(cluster/talos): Add k8s endpoint health check #696
Conversation
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
Co-authored-by: rmvangun <85766511+rmvangun@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
The windsor command now supports including k8s api endpoints in its node health check. Leveraging this may help prevent issues when the cluster nodes are healthy but the API isn't yet accessible. In order to use this routine, the kubeconfig must have been created. It makes sense to perform the kubeconfig generation inside the machine module when `bootstrap = true`. Also sets parallelism to 1 in the template when building the talos cluster. This will be leveraged in the future for upgrades, but is appropriate to establish as part of the sequenced health checking routine.
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.
The windsor command now supports including k8s api endpoints in its node health check. Leveraging this may help prevent issues when the cluster nodes are healthy but the API isn't yet accessible.
In order to use this routine, the kubeconfig must have been created. It makes sense to perform the kubeconfig generation inside the machine module when
bootstrap = true.Also sets parallelism to 1 in the template when building the talos cluster. This will be leveraged in the future for upgrades, but is appropriate to establish as part of the sequenced health checking routine.