Make api and well known ingresses have configurable hosts

[Sovietaced]

Why are the changes needed?

With ingress-nginx you cannot have multiple ingresses with the same hosts and the same routes. The http ingress and the api-jwt conflict in that regard.

ie.

one or more synchronization tasks completed unsuccessfully, reason: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: host "<redacted>" and path "/flyteidl2.workflow.RunService" is already defined in ingress flyte-v2/flyte-v2-flyte-binary-http

Additionally, it may be nice to have ingresses on different hosts (ie. api.flyte2.internal.com, flyte2.internal.com, oauth.flyte2.internal.com)

What changes were proposed in this pull request?

This pull request allows each ingress to have a configurable host such that you can run them on different sub domains (ie. different hosts).

Empty strings are falsy in helm so this change is completely backwards compatible and does not change the default behavior.

How was this patch tested?

Untested but pretty straightforward...

Labels

Please add one or more of the following labels to categorize your PR:

• added: For new features.
• changed: For changes in existing functionality.
• deprecated: For soon-to-be-removed features.
• removed: For features being removed.
• fixed: For any bug fixed.
• security: In case of vulnerabilities

This is important to improve the readability of release notes.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Stack

If you do use git town to manage PR Stacks, the stack relevant to this PR
will show below. Otherwise, you can ignore this section.

Docs link

[pingsutw]

Looks good. Let’s wait for GitHub Actions to recover.