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

Ability to access http k8s via multiple hostnames #18257

Merged
merged 1 commit into from Sep 17, 2021

Conversation

fredthomsen
Copy link
Contributor

Template the airflow ui and flower ingress in the helm chart to enable them
to be accessed via multiple hostnames. Also quote hostnames so that
wildcard hostnames can be used.

The old field specifying a single hostname has been marked as deprecated, but can still be used maintaining backwards compatibility. This does not allow different paths to be associated with different hosts. I was concerned about increasing the complexity too much here while trying to keep backwards compatability.

closes: #18216.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

Copy link
Member

@jedcunningham jedcunningham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need tests for this change.

chart/values.schema.json Show resolved Hide resolved
chart/templates/webserver/webserver-ingress.yaml Outdated Show resolved Hide resolved
chart/templates/webserver/webserver-ingress.yaml Outdated Show resolved Hide resolved
chart/values.schema.json Show resolved Hide resolved
chart/values.schema.json Outdated Show resolved Hide resolved
@fredthomsen fredthomsen force-pushed the multipleHostnameIngress branch 3 times, most recently from b1c3011 to c3696bf Compare September 16, 2021 04:19
@fredthomsen
Copy link
Contributor Author

We also need tests for this change.

I've added some tests. Looking at the other tests, I think this is what we're looking for but wasn't too sure of myself.

@fredthomsen fredthomsen force-pushed the multipleHostnameIngress branch 3 times, most recently from ec5440d to dfb28d4 Compare September 17, 2021 04:34
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.
@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Sep 17, 2021
@github-actions
Copy link

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:helm-chart Airflow Helm Chart okay to merge It's ok to merge this PR as it does not require more tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Helm chart ingress support multiple hostnames
3 participants