Skip to content

Conversation

@rmvangun
Copy link
Contributor

Add windsor check node-health subcommand to verify cluster node health status.

  • Implement ClusterClient interface with base and Talos-specific implementations

  • Add node health checking with configurable timeout and version validation

  • Support multiple node addresses and custom timeout via CLI flags

  • Integrate cluster client resolution into controller dependency injection

  • Add Talos gRPC client with proper resource management and connection handling

  • Update existing commands to use 'Cluster' requirement instead of 'Kubernetes'

The subcommand requires --nodes flag and optionally accepts --timeout and --version for comprehensive cluster health validation.

Add `windsor check node-health` subcommand to verify cluster node health status.

- Implement ClusterClient interface with base and Talos-specific implementations

- Add node health checking with configurable timeout and version validation

- Support multiple node addresses and custom timeout via CLI flags

- Integrate cluster client resolution into controller dependency injection

- Add Talos gRPC client with proper resource management and connection handling

- Update existing commands to use 'Cluster' requirement instead of 'Kubernetes'

The subcommand requires --nodes flag and optionally accepts --timeout and --version for comprehensive cluster health validation.
@rmvangun rmvangun self-assigned this Jun 19, 2025
@rmvangun rmvangun merged commit fd40251 into main Jun 19, 2025
12 checks passed
@rmvangun rmvangun deleted the feature/cluster-node-health-check branch June 19, 2025 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants