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

CIC support cilium ingress gateway #671

Open
changhyuni opened this issue Oct 29, 2024 · 0 comments
Open

CIC support cilium ingress gateway #671

changhyuni opened this issue Oct 29, 2024 · 0 comments

Comments

@changhyuni
Copy link

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.

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

1 participant