When validators clients access the charon nodes that are created using the charon-cluster chart they need to have direct access using their IPs, this is inconvenient for a k8s-native environment. We need to use k8s services endpoints.
🛠️ Proposed solution
Change the charon-cluster k8s service from clusterIP type to headless so the charon cluster pods can be accessed individually using their internal DNS names: http://statefulset-instance-name.headlessServiceName.namespace.svc.cluster.local:port
i.e http://charon-cluster-0.charon-cluster.charon-cluster.svc.cluster.local:3600
🧪 Tests
[ ] Test steps and automation scripts are provided
🎯 Problem to be solved
When validators clients access the charon nodes that are created using the charon-cluster chart they need to have direct access using their IPs, this is inconvenient for a k8s-native environment. We need to use k8s services endpoints.
🛠️ Proposed solution
Change the charon-cluster k8s service from clusterIP type to headless so the charon cluster pods can be accessed individually using their internal DNS names:
http://statefulset-instance-name.headlessServiceName.namespace.svc.cluster.local:porti.ehttp://charon-cluster-0.charon-cluster.charon-cluster.svc.cluster.local:3600🧪 Tests