New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

💉 Talos/Omni Doctor #8682

Open

smira opened this issue May 1, 2024 · 1 comment · May be fixed by #8797

Assignees

Member

smira commented May 1, 2024

Proposal: have a somewhat simple rule system that evaluates current state against common pitfalls and provides solutions.

Two problems:

enabling kubelet server certificate rotation and not approving CSRs (gate: check number of not approved certificates for the kubelet)
overlapping Talos host address and K8s pod/service CIDRs

Report such issues e.g. to the resource (in Omni? Talos?) and show it using Talos dashboard/Omni dashboard

smira mentioned this issue

Warn user when node's IP overlaps pod and/or service subnet(s) siderolabs/omni#54

Open

runningman84 commented May 3, 2024

One other pitfall is that you do not easily see that a given node is bootet from the install media instead of the internal install disk.

smira self-assigned this

smira linked a pull request

that will close this issue

feat: implement Talos doctor #8797

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment