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

HTTP01 Request not working anymore #6859

Closed
zadjadr opened this issue Mar 15, 2024 · 0 comments
Closed

HTTP01 Request not working anymore #6859

zadjadr opened this issue Mar 15, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@zadjadr
Copy link

zadjadr commented Mar 15, 2024

Describe the bug:

When creating a HTTP01 certificate request the following resources will be created:

  • Ingress with name cm-acme-http-solver-6wqfb pointing to "backend" with cm-acme-http-solver-gpf59:8089
  • Pod with name cm-acme-http-solver-hrlvr

Hence, the backend used in the ingress resource is non existent.

Expected behaviour:

Ingress name, backend name and pod name should all be the same.

Steps to reproduce the bug:

Create an ingress resource that uses a HTTP 01 challenge.

Anything else we need to know?:

Environment details::

  • Kubernetes version: 1.28.6
  • Cloud-provider/provisioner: -
  • cert-manager version: 1.14.4
  • Install method: e.g. helm/static manifests: helm
installCRDs: true

replicaCount: 1

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 1
    maxUnavailable: 1

prometheus:
  enabled: true
  servicemonitor:
    enabled: true

/kind bug

@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 15, 2024
@zadjadr zadjadr closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants