Skip to content

Introduce new parameter ingress.hosts to allow multiple ingresses #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
4 tasks done
akranga opened this issue Jan 31, 2023 · 0 comments
Closed
4 tasks done

Introduce new parameter ingress.hosts to allow multiple ingresses #24

akranga opened this issue Jan 31, 2023 · 0 comments
Assignees
@akranga
Labels
enhancement New feature or request

Comments

@akranga
Copy link
Contributor

akranga commented Jan 31, 2023 •
edited
Loading

Today we support only one ingress host. However commonly repeated feature when user wants to declare more than one ingress host for the components. Today since epam/hubctl/issues/21 scheduled for hubctl release v1.0.11

Rename parameter to ingress.host to ingress.hosts with default to myhost.${dns.domain}.
Replace ingresses with go templates to iterate over whitespace separated list of ingress.hosts

  • Update dex
  • Update istio-ingressgateway
  • Update minio
  • Update argo
@akranga akranga self-assigned this Jan 31, 2023
@akranga akranga added the enhancement New feature or request label Jan 31, 2023
@akranga akranga closed this as completed Jun 2, 2023
@akranga akranga mentioned this issue Jul 3, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akranga akranga

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akranga