search

six-group / haproxy-operator

HAProxy Operator is a Kubernetes-native solution designed to automate the deployment, configuration, and management of HAProxy instances using Custom Resources to abstract the key components such as backends, frontends, and listens.
Apache License 2.0
15 stars 2 forks source link

Question: replacement for ingress controller or rather complementing it? #64

Open mike-code opened 2 weeks ago

mike-code commented 2 weeks ago

So I was thinking (based on how you use it internally) if the instances from the operator may be used as ingress controller(s).

Due to the fact that Backend crd does not have properties that bind it to k8s Services directly, would you still use it as ingress controller and set domains svc.namespace.cluster.domain or the use-case is that the haproxy instances here act as "regular" cluster services?

m-terra commented 2 weeks ago

hi @mike-code

it can and is used as ingress controller and was designed with this puprose in mind. the backend server can by any host, regardless of whether it's an internal service or and external one.

cheers, andy