Praxis backend endpoints are currently configured statically in YAML. For Kubernetes deployments, endpoints change dynamically as pods scale, restart, or migrate.
Goal
Dynamically discover backend endpoints by watching Kubernetes Service and EndpointSlice resources.
Requirements
- Watch Kubernetes API for Service and EndpointSlice changes
- Map Kubernetes services to Praxis clusters by annotation or naming convention
- Support label selectors for filtering which services to watch
- Handle endpoint additions, removals, and address changes
- Reconnect and re-list on watch errors
- Configurable kubeconfig path or in-cluster auth
Praxis backend endpoints are currently configured statically in YAML. For Kubernetes deployments, endpoints change dynamically as pods scale, restart, or migrate.
Goal
Dynamically discover backend endpoints by watching Kubernetes Service and EndpointSlice resources.
Requirements