Skip to content
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.

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

Helm chart ingress support multiple hostnames #18216

Closed
2 tasks done
fredthomsen opened this issue Sep 13, 2021 · 1 comment · Fixed by #18257
Closed
2 tasks done

Helm chart ingress support multiple hostnames #18216

fredthomsen opened this issue Sep 13, 2021 · 1 comment · Fixed by #18257
Assignees
Labels
kind:feature Feature Requests

Comments

@fredthomsen
Copy link
Contributor

Description

When the official airflow helm chart is used to install airflow in k8s, I want to be able to access the airflow UI from multiple hostnames. Currently given how the ingress resource is structured it doesn't seem possible, and modifying it needs to take into account backwards compatibility concerns.

Use case/motivation

Given my company's DNS structure, I need to be able to access the airflow UI running in kubernetes from multiple hostnames.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@fredthomsen fredthomsen added the kind:feature Feature Requests label Sep 13, 2021
@mik-laj
Copy link
Member

mik-laj commented Sep 13, 2021

@fredthomsen Assigned. I know some corporations have complex DNS configurations.

fredthomsen added a commit to Opus-Interactive/airflow that referenced this issue Sep 17, 2021
Add support for accessing the airflow ui and the flower ui (if
applicable) from multiple hostnames when install via helm chart onto a
kubernetes cluster.

closes: apache#18216.
jedcunningham pushed a commit that referenced this issue Sep 17, 2021
Add support for accessing the airflow ui and the flower ui (if
applicable) from multiple hostnames when install via helm chart onto a
kubernetes cluster.

closes: #18216.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature Feature Requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants