Feature request: ability to specify multiple aliases for different ingresses

[dcherniv]

Hello,

Currently i have a multiple ingresses on same domain but different paths. For example.
Ingress1:
domain.com/blah
Ingress2:
domain.com/blahblah

They route to different services. We want to be able to individually set aliases for them via annotation:
nginx.ingress.kubernetes.io/server-alias: domain2.com domain3.com

Unfortunately it doesn't look like nginx ingress supports this. When i setup the above alias for Ingress1 AND Ingress2 (the same aliases) and then try to modify Ingress2 to add another alias domain4.com, nginx skips over it with:
Aliases already configured for server "domain.com", skipping (Ingress "dev/Ingress2")

Not sure if that's intentional, but it seems counter-intuitive to allow aliases in annotations because one would expect that you can mix and match so to speak.

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.