fredthomsen opened a new pull request #18542: URL: https://github.com/apache/airflow/pull/18542
This allows the ingress to specify multiple hosts with multiple different secrets, rather than being contrainted to one secret for all hosts specified. Doing this now avoids what is likely some painful backwards compatability work to resolve this later. @jedcunningham apologizes for messing up your cadence. I know the 1.2.0 helm chart release will be going out soon, and looking back on some issues with TLS certs I noticed after #18257 was merged, I wondered if this change would be considered before that release goes out. If so, I can clean up these failures. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
