Open rasticek opened 7 hours ago
In general native ingerss controller creates one listener for each service port and one backend set for all backends of that service. So have you tried creating 3 different services with respective listener port/backend configuration?
Hi, yes I've tried already. Unfortunately it keeps failing because within kube it has same target port and/or the service is not exposed for these controllers on this port, it is just endpoint (not service). I believe that this is because example from nginx uses config map approach in this case. Is it possible to get to the configuration I described using oci-native-ingress-controller please?
Hi,
I would like to setup OCI LB for Kafka deployment by utilizing ClusterIP services with Ingress (for Kafka I am using https://github.com/bitnami/charts/tree/main/bitnami/kafka/#installing-the-chart). I am using 3 controllers/brokers for Kafka. Such setup is documented/working with nginx LB using config maps but I'm not able to configure similar with oci-native-ingress-controller. Anyway, when I configure it manually (the LB on OCI) it is working as expected.
Brief description:
Nginx is using config maps on controller deployment and this is then propagated on Ingress and into LB afterwards . Sample config map
Is it possible to achieve this configuration using oci-native-ingress-controller with Ingress or is this functionality missing so far please?
Thank you.