I am deploying a high-availability Flink job to Kubernetes in application
mode using Flink's standalone k8 deployment
https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/deployment/resource-providers/standalone/kubernetes/
All goes well when I deploy a job, but if I want to deploy a second
application-mode Flink job in the same K8s namespace I get a
"spec.ports[0].nodePort:
Invalid value: 30081: provided port is already allocated" error. Is there a
way that nodePort can be allocated dynamically, or other way around this
(using Loadbalancer or Ingress instead of NodePort in
jobmanager-rest-service.yaml?) besides hard-coding different nodePorts for
different jobs running in same namespace?

Thanks,

Javier Vegas

Reply via email to