-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
nixos/kubernetes: add extraSANs to kubelet TLS cert. #104408
Conversation
Looks good to me. |
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.
@saschagrunert I'm good with this. You? :)
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.
LGTM
extraSANs = mkOption { | ||
description = "Extra x509 Subject Alternative Names to be added to the kubelet tls cert."; | ||
default = []; | ||
type = listOf str; |
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.
can you add an example
, please? like I did in #74094
I marked this as stale due to inactivity. → More info |
Not stale..... |
Motivation for this change
Allow adding extra (IP) SANs to the kubelet TLS cert. Running services
like metrics-server in secure mode tries to access kubelet over https
using the node IP. If the the certificate does not contain the correct
IP SANs, metrics server fails (unless started with--kubelet-insecure-tls).
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)