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

feat[common]: implement support for NGINX as primary ingress provider #31878

Open
2 tasks done
PrivatePuffin opened this issue Feb 10, 2025 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@PrivatePuffin
Copy link
Member

Is your feature request related to a problem?

Traefik depends heavily on CRDs, has became bloatware and has frequent non-semver breaking changes.
This gets worsened by the mediocre support for the new gateway-api that is going to replace ingress in due time

This makes it harder-and-harder to support and hence we should move elsewhere.

Describe the solution you'd like

We should implement NGINX as our standard and go-to ingress provider.

Describe alternatives you've considered

.

Additional context

Luckily this wont mean having to implement many new objects.

What it does entail:

  • R&D
  • Replacing it in clustertool defaults
  • Potentially adding an ingress integration

I've read and agree with the following

  • I've checked all open and closed issues and my request is not there.
  • I've checked all open and closed pull requests and my request is not there.
@PrivatePuffin PrivatePuffin added the enhancement New feature or request label Feb 10, 2025
@PrivatePuffin PrivatePuffin changed the title Common: implement support for NGINX as primary ingress provider feat[common]: implement support for NGINX as primary ingress provider Feb 10, 2025
@PrivatePuffin PrivatePuffin added this to the TrueCharts 2025-Q3 milestone Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant