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

Failed to update endpoint cert-manager/cert-manager-webhook #5297

Closed
AuqW9cQ opened this issue Jul 12, 2022 · 5 comments
Closed

Failed to update endpoint cert-manager/cert-manager-webhook #5297

AuqW9cQ opened this issue Jul 12, 2022 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@AuqW9cQ
Copy link

AuqW9cQ commented Jul 12, 2022

I have a MicroK8s 1.24 single Node installation, cert-manager(1.8.2) deployed via helm3.

deploy my ClusterIssuer:

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    email: letsencrypt@domain.tld
    solvers:
    - selector: {}
      http01:
        ingress:
          class: public # ingress class is called public in MicroK8s, not nginx
                         # https://github.com/cert-manager/cert-manager/issues/2842
    privateKeySecretRef:
      name: letsencrypt-staging
    server: https://acme-staging-v02.api.letsencrypt.org/directory
---
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
spec:
  acme:
    email: letsencrypt@domain.tld
    solvers:
    - selector: {}
      http01:
        ingress:
          class: public # ingress class is called public in MicroK8s, not nginx
                         # https://github.com/cert-manager/cert-manager/issues/2842
    privateKeySecretRef:
      name: letsencrypt-prod
    server: https://acme-v02.api.letsencrypt.org/directory

Then i deploy nextcloud with the following ingress:

apiVersion: networking.k8s.io/v1 
kind: Ingress
metadata:
  name: nextcloud-ingress
  namespace: nextcloud
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-prod"

spec:
  tls:
  - hosts:
    - cloud.domain.tld
    secretName: nextcloud-secret
  rules:
  - host: cloud.domain.tld
    http:
      paths:
      - pathType: Prefix
        path: /
        backend:
          service:
            name: nextcloud-server
            port:
              number: 80

All thems to be good and i get a certificate:

kubectl get certificate -n nextcloud 
NAME               READY   SECRET             AGE
nextcloud-secret   True    nextcloud-secret   145m

But i cant reach my nextcloud and get a 404 error.

and this message:
cert-manager 5m15s Warning FailedToUpdateEndpoint endpoints/cert-manager-webhook Failed to update endpoint cert-manager/cert-manager-webhook: Operation cannot be fulfilled on endpoints "cert-manager-webhook": the object has been modified; please apply your changes to the latest version and try again

if more information is needed to find the reason of the problem please tell me.

@oSunnyo
Copy link

oSunnyo commented Jul 19, 2022

I have the same issue,maybe annotations:kubernetes.io/ingress.class: "nginx" is not work.

@jetstack-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

@jetstack-bot jetstack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2022
@jetstack-bot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

@jetstack-bot jetstack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 16, 2022
@jetstack-bot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

@jetstack-bot
Copy link
Collaborator

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/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
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants