-
Notifications
You must be signed in to change notification settings - Fork 608
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.
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
initial version for Talos metric scraping How To #10094
base: main
Are you sure you want to change the base?
Conversation
- op: add | ||
path: /cluster/etcd/extraArgs | ||
value: | ||
listen-metrics-urls: https://0.0.0.0:2379 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say probably it might be easier to listen for metrics on a separate non-https url, e.g. http://0.0.0.0:10003
(whatever port), so that drops the requirement to extract etcd certs and put them into the cluster (which I think a security risk on its own).
Instead, the port can be blocked from the outside via https://www.talos.dev/v1.9/talos-guides/network/ingress-firewall/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thats interesting and indeed an easier / better way! Thanks, I will give that a try and update the how to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry and I really hate to say this but I am preparing to move away from Talos, which means I cannot properly test and finish this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Hr46ph any chance you could share to what and why you are moving? I just moved to talos...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talos is amazing and my reasons to move away is an edge case requiring usb-c nic drivers (homelab) that arent loading properly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you try the USB modem extension? I found this worked for my USB-c network adapters https://github.com/siderolabs/extensions/tree/main/drivers/usb-modem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I did. I tried a lot of things, I even compiled the kernel and custom images with drivers included, but got stuck on including assets at which point I gave up. Been at it for weeks spent most of my free time for something that should be trivial.
Pull Request
What? (description)
Added new file
website/content/v1.10/talos-guides/howto/monitoring.md
as requested here:#7214 (comment)
Why? (reasoning)
The steps will help the community to succesfully monitor Talos Linux Kubernetes parts.
Acceptance
Please use the following checklist:
make conformance
)make fmt
)make lint
)make docs
)make unit-tests
)