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

Additional certSANs for scheduler and controller-manager #9481

Open
maxpain opened this issue Oct 9, 2024 · 1 comment
Open

Additional certSANs for scheduler and controller-manager #9481

maxpain opened this issue Oct 9, 2024 · 1 comment

Comments

@maxpain
Copy link
Contributor

maxpain commented Oct 9, 2024 •
edited
Loading

How do we add additional certSANs for the scheduler and controller-manager?
Currently, only 127.0.0.1 is allowed, but I want to add node IP as well to be able to monitor it using Prometheus without using insecureSkipVerify: true
@smira
Copy link
Member

smira commented Oct 16, 2024

Talos doesn't provide a TLS certificate to both of these pods, so they act based on default configuration:

if HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smira @maxpain