Skip to content

Ingress routes for challenges created with pathType: ImplementationSpecific not working with Cilium #6805

@RealKelsar

Description

@RealKelsar

Describe the bug:
Basically the opposite of #4371

Not sure if BUG or Feature Request

With Cilium and l2announcer one need to use the edit inline feature, because otherwise it will create new LoadBalancers with new IPs.

But with pathType: ImplementationSpecific the Ingress will not give precedence to the challenge over other Paths, making the challenge never resolve. Editing it to Exact makes the challenge resolve.

Expected behaviour:
pathType should be configurable

Steps to reproduce the bug:
Use the HTTP01 acme solver with the Cilium ingress. There is currently no way to make this work.

Anything else we need to know?:

Environment details::

  • Kubernetes version:
  • Cloud-provider/provisioner: Cilium
  • cert-manager version: v1.14.3
  • Install method: Helm
    /kind bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions