search

cyclops-ui / cyclops

Developer Friendly Kubernetes 👁️
https://cyclops-ui.com
Apache License 2.0
2.48k stars 781 forks source link

Install manifest LoadBalancer question #222

Closed kosmoz closed 6 months ago

kosmoz commented 6 months ago

Hi!

Due to a user report at https://github.com/glasskube/glasskube/issues/518, we noticed that the services included in the cyclops install manifest are created with type LoadBalancer by default.

While load balancers can be useful for a lot of circumstances, I'm not sure if it's the right solution here. Wouldn't most users rather expose the service via an Ingress (or similar), if they want to do that at all?

Or is there another reason why the service has to be of type LoadBalancer (rather than the default, ClusterIP)?

petar-cvit commented 6 months ago

Hey @kosmoz! Yeah, you are right. I even put ClusterIP in the Cyclops Helm chart but forgot to update the install manifest. If you want, you can update it yourself, but I can do it by the end of the day

Sheikh-Abubaker commented 6 months ago

@petar-cvit if you want I can help with this issue

Sheikh-Abubaker commented 6 months ago

@kosmoz I was also facing an issue due to this as it prompted that port 3000 was already occupied.

petar-cvit commented 6 months ago

Thanks @Sheikh-Abubaker. I already pushed the fix and will build the new version which you can use

petar-cvit commented 6 months ago

@kosmoz can you check now? Release v0.3.3 should have ClusterIP service type for both services

kosmoz commented 6 months ago

Thanks a lot, using services with type ClusterIP should fix this issue.