Add support for configurable HTTP redirects

[hbagdi]

What would you like to be added:

On a per route basis, a user can configure HTTP redirects 301/302 (may be 307/308 too?) and the location of where to redirect to. It could be simply a redirect to HTTPS, in which case, redirect with the Location header matching the URL of the request being processed or it could be a redirect to a different location. The second part can get tricky because that can invovle path munging (we could consider that to be an extended/custom API).

Why is this needed:

This is a common requirement and most controllers already support this using annotations.

[jpeach]

@hbagdi One idea I had for this was a special syntax for route selectors (e.g. .wellknown namespace names). That can work for simple http->https cases, but probably doesn't scale for arbitrary redirects.

[hbagdi]

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jpeach]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[robscott]

/remove-lifecycle stale

[hbagdi]

/lifecycle frozen
/assign