Skip to content
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

feat(kube-system): monitor kube-controller-manager and kube-scheduler #222

Closed
uhthomas opened this issue Jul 25, 2023 · 1 comment
Closed

feat(kube-system): monitor kube-controller-manager and kube-scheduler #222

uhthomas opened this issue Jul 25, 2023 · 1 comment
Labels
enhancement New feature or request monitoring

Comments

@uhthomas
Copy link
Owner

uhthomas commented Jul 25, 2023 •
edited
Loading

They both listen on localhost only by default, which means they cannot be connected to from within the cluster. The service scrape configs were removed in 8e1e45e. The nodes will need to be reconfigured to listen on 0.0.0.0 and then these service scrapes can be added back.
@uhthomas uhthomas added enhancement New feature or request monitoring labels Jul 25, 2023
@uhthomas
Copy link
Owner Author

uhthomas commented Feb 3, 2024

siderolabs/talos#3765

uhthomas added a commit that referenced this issue Jul 30, 2024
@uhthomas
feat(k8s/amour/kube-system): monitor kube-controller-manager and kube…
7c3e6c0 
…-scheduler

This also required changing the `bind-address` for both of them in Talos
to 0.0.0.0.

Fixes: #222
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request monitoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@uhthomas