Allow using public TLS certificates for Pandaproxy API #6637
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e the check on pandaproxy config was not effective)
…tls on pandaproxy and schema registry
nicolaferraro
force-pushed
the
pandaproxy-tls
branch
from
aa8d007
to
ff18ceb
Compare
RafalKorepta
approved these changes
Oct 5, 2022
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cover letter
This adds the possibility to specify a TLS issuer for Pandaproxy, like it happens for Kafka and Schema registry. It does so by adding two new fields (issuerRef, nodeSecretRef) to PandaproxyAPI spec.
Release notes
Features