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

certificate resource has no owner. refusing to update non-owned certificate resource for object #11313

Closed
illegalbae opened this issue Apr 25, 2024 · 3 comments
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@illegalbae
Copy link

Encountering errors during certificate renewal in cert-manager.io, specifically certificate resource has no owner. refusing to update non-owned certificate resource for object.

Details:
Right now this does not effect us directly since we use cloudflare proxy and all our connections are proxied. If it was not proxied then this would be a larger error but for now its not really a major issue.

We currently use cert-manager.io to handle certificate generation and renewals but we've been having issues with the renewal process.

@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Apr 25, 2024
@longwuyuan
Copy link
Contributor

Click on the new bug report button and answer the questions you see in the template of a new bug report, in the prescribed md format. This will make it possible to know if there is a problem with the ingress-nginx controller and then maybe reproduce it in a minikube or a kind cluster.

/close

@k8s-ci-robot
Copy link
Contributor

@longwuyuan: Closing this issue.

In response to this:

Click on the new bug report button and answer the questions you see in the template of a new bug report, in the prescribed md format. This will make it possible to know if there is a problem with the ingress-nginx controller and then maybe reproduce it in a minikube or a kind cluster.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

3 participants