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

add individual ingress configuration per service #2183

Merged
merged 13 commits into from
May 14, 2024

Conversation

pgvishnuram
Copy link
Contributor

@pgvishnuram pgvishnuram commented Apr 25, 2024

Description

This PR segreagates the common ingress rules to individual rules per service to avoid policy issues

Related Issues

Testing

Yet to update

Merging

NA

@pgvishnuram pgvishnuram marked this pull request as ready for review April 25, 2024 13:51
@pgvishnuram pgvishnuram requested a review from a team as a code owner April 25, 2024 13:51
@rishkarajgi rishkarajgi marked this pull request as draft May 7, 2024 14:30
@pgvishnuram pgvishnuram marked this pull request as ready for review May 12, 2024 14:12
Comment on lines +125 to +126
enablePerHostIngress: false

Copy link
Member

Choose a reason for hiding this comment

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

I think this per-host ingress configuration should be the only way to do it. I don't think we should allow the old way of doing it. If we switch to this new method then we reduce the amount of code we have to maintain and test while still providing the same features, just in a different way that is compatible with more environments.

Is there some reason we should keep the old way as an option?

Copy link
Member

Choose a reason for hiding this comment

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

Slack thread https://astronomer.slack.com/archives/C02J8JT58CC/p1715623166453439

We agreed to keep the old way in, behind a feature flag, and run it through a deprecation phase.

Copy link
Contributor

Choose a reason for hiding this comment

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

We can default this to true @pgvishnuram

@pgvishnuram pgvishnuram merged commit 4358b56 into master May 14, 2024
7 of 8 checks passed
@pgvishnuram pgvishnuram deleted the feat/single-ingress-per-service branch May 14, 2024 13:08
pgvishnuram added a commit that referenced this pull request May 14, 2024
* add individual ingress per service

* update templating

* added feature flag

* fix pre-commit

* re-work test cases

* rework ingress template

* update test cases

* fix pre-commit

* update test cases

* Generalize some tests, add some test cases.

---------

Co-authored-by: Daniel Hoherd <daniel.hoherd@gmail.com>
@rishkarajgi rishkarajgi changed the title add individual ingress per service add individual ingress configuration per service May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants