-
Notifications
You must be signed in to change notification settings - Fork 924
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
ingress-nginx does not support MCI derived-service #2172
Comments
Yes. karmada/pkg/controllers/mcs/service_export_controller.go Lines 158 to 163 in a50e31d
Can you give me a minimum reproduce step? |
@chaunceyjiang If you deploy MCI, you can directly modify the deployment of ingress-nginx and add the following configuration to args:
tcp-service configmap:
udp-service configmap:
For details, please refer to this article on the Internet:ingress-tcp-udp |
ingress-nginx(https://github.com/kubernetes/ingress-nginx) does not support endpointslices. you can modify ingerss-nginx to support endpointslices object. For details, see [multi-cluster-ingress-nginx](https://github.com/karmada-io/multi-cluster-ingress-nginx). See ingress-nginx‘s Support Kubernetes EndpointSlices issue |
I was wondering if it would be feasible to import the endpoint through karmada too |
Need to modify the mcs-controller to support endpoints. I don't think that's the right thing to do. |
Yes, Need to modify the mcs-controller , I am not sure if this is a good solution, I hope more people can discuss this problem |
ping @XiShanYongYe-Chang . Can mcs-controller support endpoints? what do you think? |
Yes, we could consider supporting endpoint in mcs-controller. |
What would you like to be added:
I don't know if other users in the community have this requirement, that is to do 4-layer load access through ingress.
I want derived-service to be able to add endpoint
Why is this needed:
When I load the tcp or udp layer 4 network of ingress, I find that it will look for the endpoint of the configuration service. The derived service of karmada mci has no endpoint, only endpoint slices, so the following error will be reported when doing layer 4 network load:
Service "default/derived-serve" does not have any active Endpoint for TCP port 80
The text was updated successfully, but these errors were encountered: