Flink applications are not 'http services', so they don't need any tls certs or Service listeners defined. Our current mesh module will always use the mesh.public_port to set up a k8s Service and other resources.
We should make a new version of mesh templates that don't deploy Service etc. if mesh.public_port is not defined.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | lbowmaker | T324578 [EPIC] Flink Applications on Kubernetes | |||
| Resolved | bking | T326409 Migrate the wdqs streaming updater flink jobs to flink-k8s-operator deployment model | |||
| Resolved | Ottomata | T324576 Flink on Kubernetes Helm charts | |||
| Resolved | Ottomata | T326252 k8s deployment-charts mesh module should allow use of mesh without public_port Service |
Change 875387 had a related patch set uploaded (by Ottomata; author: Ottomata):
[operations/deployment-charts@master] [WIP] modules/mesh - Support mesh service proxy without exposing a Service for public_port
Change 875387 merged by jenkins-bot:
[operations/deployment-charts@master] modules/mesh - Support mesh service proxy without exposing a Service for public_port