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
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: ImplementationSpecificthe 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::
/kind bug