kubernetes-sigs/cluster-api

Consider if to add more on KCP checks on machine status

Open

#10,949 opened on Jul 26, 2024

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
area/provider/control-plane-kubeadmhelp wantedkind/featurepriority/important-longtermtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added (User Story)?

As an operator, I need as much as possible info about the status of my control plane machines

Detailed Description

KCP implements checks for components status on controlled machines: API Server, Scheduler, Controller Manager, etcd

We should consider if to add more to the list of components, e.g. kube-proxy, kubelet (node). This could provide an interesting signal to catch problems that could happen during upgrades when e.g. the control plane comes up because it is implemented via static pod, but other "regular" pods scheduled on the control plane node might not come up.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature /area provider/control-plane-kubeadm

Contributor guide

Research direction
Investigate the current KCP controller implementation that checks component statuses (API Server, Scheduler, Controller Manager, etcd). Identify which additional components (e.g., kube proxy, kubelet, node) could be monitored to detect upgrade issues where static pods start but regular pods fail. Consider the impact on KCP status conditions and how to add checks without breaking existing behavior. Look at existing test files and PRs for similar status additions.
Tech stack
go
Domain
backendinfrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesCluster APIKubeadmControlPlane
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50