Skip to content

[release-1.18] ACME + HTTP01 + Ingress-Nginx: "Error: Path cannot be used with pathType Exact" when strict-validate-path-type is enabled #7791

@Nelfimov

Description

@Nelfimov

ℹ This issue has been addressed in https://github.com/cert-manager/cert-manager/releases/tag/v1.18.1

ℹ Read release-notes-1.18 to learn more about the problem and the work arounds.

Describe the bug:

After v1.18 when issuing a new certificate I got an error:

4m36s Warning PresentError challenge/cms-tls-1-3184104856-2172708158 Error presenting challenge: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: ingress contains invalid paths: path /.well-known/acme-challenge/oTw4h9_WsobTRn5COTSyaiAx3aWn0M7_aYisoz1gXQw cannot be used with pathType Exact

Expected behaviour:

Certificate should be issued.

Steps to reproduce the bug:

  • cert-manager v1.18
  • Simple ingress
    apiVersion: networking.k8s.io/v1
    kind: Ingress
    metadata:
      name: example-ingress
      namespace: example
      annotations:
        kubernetes.io/ingress.class: nginx
        cert-manager.io/cluster-issuer: letsencrypt-prod
    spec:
      tls:
        - hosts:
            - example.com
          secretName: example-tls
      rules:
        - host: example.com
          http:
            paths:
              - path: /
                pathType: Prefix
                backend:
                  service:
                    name: example
                    port:
                      name: http

Anything else we need to know?:

Environment details:

  • Kubernetes version: 1.31.2
  • cert-manager version: 1.18
  • Install method: helm

/kind bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions