In aSecure Kubernetes Gateway architecture you have integration with your existing K8s platform, using the XC node as the external load balancer for your K8s cluster. In this scenario, you create a ServiceAccount andkubeconfigfile to configure XC. The XC node then performs service discovery against your K8s API server. I've covered this process in aprevious article, but the advantage is that you can integrate with existingK8s platforms. One disadvantage is that this is true for NodePort services only (not ClusterIP).
However when it came to the revised version in Oct 2023, this changed to :
This allows exposing both NodePort and ClusterIP services via the XC node.
Could you please let me know how we can expose via Cluster IP , because Cluster IP is internal to the cluster and provides internal connectivity , what am i missing here ?