Skip to content
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

Document eventing kafka broker tls resource dependency on eventing core tls resources #5606

Closed
Cali0707 opened this issue Jun 21, 2023 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Cali0707
Copy link
Member

What is changing? (Please include as many details as possible.)

We are working to include releasing the cert-manager tls resources required for Eventing TLS in the eventing kafka broker. These resources require eventing-tls-networking.yaml from Eventing core to be applied before they are. We should document this dependency.

How will this impact our users?

Users will have to apply eventing-tls-networking.yaml before they apply eventing-kafka-tls-networking.yaml

Context

Link to associated PRs or issues from other repos here.

  1. Release cert-manager certificates in eventing-kafka-tls-networking knative-extensions/eventing-kafka-broker#3155
  2. Update scripts to deploy/release cert manager resources knative-extensions/eventing-kafka-broker#3156
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 20, 2023
@Cali0707
Copy link
Member Author

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 20, 2023
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant