feat: add active node validation with nodeadm init #779
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.
Issue #, if available: N/A
Description of changes:
Add active node validation with nodeadm init command.
Description: Nodeadm init command performs hybrid node initialization process. However, there is no guarantee that the node is successfully registered with the Kubernetes cluster and is in "Ready" state. This change adds the Post-Initialization steps in nodeadm init command and validates if kubernetes client on node is able to fetch the required status from kubernetes api-server.
This validation is enabled by default and users can disable or update the validation wait-timeout duration. Default timeout is 10 minutes.
nodeadm int command update:
-w / --wait-timeout (optional flag) to disable or change the nodeadm init validation timeout
Internally it perform the validation in three steps:
Node Registration Validation - Verifies node is registered with the cluster
CNI Detection - Detects CNI plugin type (Cilium, Calico, or none)
Node Readiness Validation - Ensures node is in Ready state with proper network configuration
Testing (if applicable):
Added unit tests and tested on hybrid node
Successful case
Failed case when CNI supported binary not found
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.