tnozicka/openshift-acme

OpenShift's "haproxy.router.openshift.io/rewrite-target" gets copied to exposer route

andreasottosson opened this issue · 4 comments

What happened:
When issuing a certificate for a route that contains the annotation "haproxy.router.openshift.io/rewrite-target", this gets copied to the exposer route which makes the route inaccessible.

What you expected to happen:
The exposer route should not have the annotation from the original route.

How to reproduce it (as minimally and precisely as possible):
Add annotation "haproxy.router.openshift.io/rewrite-target" to a route and then issue a certificate. You need to add a value to this, for example "haproxy.router.openshift.io/rewrite-target: /". The exposer pod now rewrites the path to the backend pod and returns 404.

Anything else we need to know?: Not really :)

Environment:

  • OpenShift/Kubernetes version (use oc/kubectl version): OpenShift 4.6.12
  • Others:

@tnozicka

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.