-
Notifications
You must be signed in to change notification settings - Fork 0
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
allow for custom domain in k8s-nameserver #3
Conversation
@@ -75,6 +75,10 @@ type DNSConfigSpec struct { | |||
// Tailscale Ingresses. The operator will always deploy this nameserver | |||
// when a DNSConfig is applied. | |||
Nameserver *Nameserver `json:"nameserver"` | |||
// Domain is the domain for which DNS entries will be resolved. | |||
// Defaults to ts.net if empty. |
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.
The flag in the nameserver defaults to ts.net
but here it does not so this comment is not super accurate. Maybe a kubebuilder default here would make sense?
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 was thinking about this, but I didn't see any kubebuilder default annotation used in any other type file. That is why I went without. I could change the comment to
If left empty, the default of the k8s-nameserver will be used.
?
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.
Furthermore the domain is currently defined by the control-server and by the k8s-nameserver, but the k8s-operator is quite domain agnostic. The "ts.net" domain is only used in test files.
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.
If left empty, the default of the k8s-nameserver will be used.
Fine with 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.
I changed it.
Pull Request Test Coverage Report for Build 12138963348Details
💛 - Coveralls |
This allows for a custom domain in the k8s-nameserver application. It can be set via an argument to the binary and will default to ts.net if not set.
7698ffa
to
1658054
Compare
This allows to have a custom magicDNS domain for the k8s-nameserver.