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 an option to deploy neither a LoadBalancer nor an Ingress #17

Open
zonque opened this issue Apr 28, 2024 · 4 comments
Open

Add an option to deploy neither a LoadBalancer nor an Ingress #17

zonque opened this issue Apr 28, 2024 · 4 comments

Comments

@zonque
Copy link

zonque commented Apr 28, 2024

In setups with Traefik Ingressroutes, a LoadBalancer is deployed by Traefik. When Cuber installs its own one next to it, is is ignored as long as the one that is already active has bound the external ports already. As soon as Traefik is restarted however, the dormant Cuber managed LoadBalancer pops to life which leads to all IngressRoutes being ignored.

Setting ingress: true in the Cuberfile leads to an Ingress living next to the Ingressroutes which then acts as a default catch for all requests that are not matched by Traefik, which is dangerous in case certain paths are protected by middlewares Ingressroutes rules.

For such setups, the only sane thing is not to touch the ingress side at all and deploy neither a LoadBalancer nor an Ingress, but there is currently no option to do that. Could that be added?

@collimarco
Copy link
Contributor

Do you have any special reasons to use Traefik?

Why can't you use a normal load balancer or ingress?

@zonque
Copy link
Author

zonque commented Apr 28, 2024

Traefik is the default shipped by k3s. I'm using many features of it and I would like to keep it.

@zonque
Copy link
Author

zonque commented May 13, 2024

FWIW, I am tracking the changes needed to make Cuber work with k3s here.

@asimmons91
Copy link

I actually ran into this too while getting my rails app deployed on a k3s cluster.

My workaround was to deploy it with a basic ClusterIP service and wire up the ingress myself outside of Cuber.

I opened a PR with the changes I made, #19. Let me know what you think and feel free to close it out if it doesn't make sense to add to the main project. 🙂

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

No branches or pull requests

3 participants