-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: only add non-FQDN variant of fully qualified domain names to SANs #564
Conversation
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 trust your experiments, so change looks good to me :)
But before we merge I would like to see some other reviewer on this.
- Can you please add a changelog entry? I think we should mark this as breaking, but note that it should be fine (tm)
Looking at #547, I also noticed the following things:
- Please also update
docs/modules/secret-operator/pages/scope.adoc
(mention the truncation) - Normally I would not require you to write tests, on the other hand it would be kind of sad if we would throw away the effort of fix: For cluster internal scopes also add variant without trailing dot #547 writing some tests.
Would you mind copying and adopting them into your PR?
@sbernauer Thanks for the feedback! I tried to address all your points. |
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.
Thanks! Noticed on minor thing
d5730f9
to
b5d59f4
Compare
Yeah i like this as the minimal change for experimental FQDNs. Fixed most of the problems i stumbled over. |
Yes, I tested both ZooKeeper and Kafka |
7900073
to
d84ab26
Compare
d84ab26
to
114343b
Compare
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
f8a7a82
to
12dcfb3
Compare
Description
Replaces #547
Extends FQDN support to improve DNS lookup performance, see stackabletech/issues#656
We experienced issues, especially with mTLS, when a client connects to a host via its FQDN (
pod.service.svc.cluster.local.
). Currently, only the FQDN (with the trailing dot) is added to the SANs. With this fix, only the non-FQDN version (without trailing dot) is added. This solves the problems in our tests.This fix should be backwards compatible and not break anything that works currently, it only improves support for FQDN cluster domains.
I tested the fix with several integration tests (including Zookeeper and Kafka mTLS tests) by setting the env var
KUBERNETES_CLUSTER_DOMAIN
tocluster.local.
for all operators.Without this fix, at least these tests failed for me:
tls_kafka-3.8.1_zookeeper-latest-3.9.2_use-client-tls-true_use-client-auth-tls-true_openshift-false
and
smoke_zookeeper-3.9.2_use-server-tls-true_use-client-auth-tls-true_openshift-false
Definition of Done Checklist
Author
Reviewer
Acceptance