Description
Is your feature request related to a problem? Please describe.
Currently, when creating a Clillium Ingress Gateway, the Citrix Ingress Controller (CIC) does not automatically create the required load balancer (LB) if the Kubernetes Service object lacks necessary label selectors and endpoint slices. This limitation can hinder the deployment of ingress resources in certain scenarios.
Describe the solution you'd like
We need the Citrix Ingress Controller to be more flexible in its handling of Kubernetes Service objects. Specifically, even when the Kubernetes Service lacks label selectors and endpoint slices, the CIC should still create the corresponding load balancer. This would ensure better compatibility and ease of use in varying cluster configurations.
Additional context
By supporting this enhancement, we can improve the flexibility of deploying ingress resources and ensure that services are properly exposed even in the absence of detailed Kubernetes Service configurations. This would be particularly beneficial for users in dynamic environments or when using alternative CNI solutions like Cilium.