-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
using-auto-tls & using-cert-manager-on-gcp need (at least) a create namespace #1365
Comments
Issues go stale after 90 days of inactivity. Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra. /lifecycle stale |
Stale issues rot after 30 days of inactivity. Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra. /lifecycle rotten |
/remove-lifecycle stale |
Rotten issues close after 30 days of inactivity. Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra. /close |
@knative-housekeeping-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Expected Behavior
Follow the instructions and everything just works.
Actual Behavior
Error when trying to create a secret step #3 has
--namespace cert-manager
for the first time.At the very least it needs:
I've also tried changing the namespace to
knative-serving
, either way, when I apply the ClusterIssuer`, I see no status. So something else is wrong on these two pagesI'll try to figure it out and comment here.
The text was updated successfully, but these errors were encountered: