Answer
Check kubectl get pods for the pod status, then kubectl logs <pod-name> on the OData pod specifically — a common cause is the database port (1521) being blocked by a firewall between your local kubectl session and the target database, which the OData pod's logs will surface clearly even when the deployment itself looks healthy.