Remove SelfSigned issuer from released transport-encryption
artifacts
#7905
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.
Using a SelfSigned issuer is not recommended by cert-manager and currently we're shipping it in the tranport-encryption feature artifact.
Moving forward, we will not ship a SelfSigned issuer in the
eventing-tls-networking.yaml
artifacts and we will document, as a prerequisite, how to create aClusterIssuer
for eventing components so that by users can bring their own choosen issuer [1].[1] https://cert-manager.io/docs/concepts/issuer/
Fixes #
Proposed Changes
transport-encryption
artifactsPre-review Checklist
Release Note
Docs