-
Notifications
You must be signed in to change notification settings - Fork 226
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(tls): support ca type issuer and v1alpha* version cert-manager api #561
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: ericsyh <ericshenyuhao@outlook.com>
Signed-off-by: ericsyh <ericshenyuhao@outlook.com>
Signed-off-by: ericsyh <ericshenyuhao@outlook.com>
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.
Good work! I added a question regarding backwards compatibility.
- "*.{{ template "pulsar.fullname" . }}-{{ .Values.proxy.component }}.{{ template "pulsar.namespace" . }}.svc.{{ .Values.clusterDomain }}" | ||
- "{{ template "pulsar.fullname" . }}-{{ .Values.proxy.component }}" |
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.
Is this removal a breaking change? Does this require release note instructions users that upgrade? Would it be possible to retain compatibility?
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.
Nope, it's not a breaking change cause i just move the position to make the format of proxy certificate dnsNames and broker certificate dnsNames to be consistent. It doesn't change the logic and technical this change is optional.
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.
replay the comment.
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
Fixes #
Motivation
The current chart only supports enable tls with self-signed issuer which is not possible for production users. This PR supports ca type issuser which allows users to bound a root certificate (in
Secret
) to issue required tls certificates for pulsar components.Modifications
certs.type
and add thecerts.issuers.ca.secretName
field for the root certificate reference.Verifying this change