The openmetadata Service selects on app.kubernetes.io/name + app.kubernetes.io/instance, which matches both server and OMJob operator pods. This means the operator pods are included in the service's endpoint set despite serving different ports and having a different role.
This causes issues with anything that targets the service — load balancers, network policies, service mesh routing, readiness gates, etc. The operator serves on ports 8080/8081, not 8585, so it shouldn't be part of the server's service.
The operator deployment already sets app.kubernetes.io/component: omjob-operator on its pods, but the service doesn't filter on component.
Suggested fix: Add app.kubernetes.io/component: server to the server deployment's pod template and include it in the service selector.
- Chart version: 1.12.3
omjobOperator.enabled: true
The
openmetadataService selects onapp.kubernetes.io/name+app.kubernetes.io/instance, which matches both server and OMJob operator pods. This means the operator pods are included in the service's endpoint set despite serving different ports and having a different role.This causes issues with anything that targets the service — load balancers, network policies, service mesh routing, readiness gates, etc. The operator serves on ports 8080/8081, not 8585, so it shouldn't be part of the server's service.
The operator deployment already sets
app.kubernetes.io/component: omjob-operatoron its pods, but the service doesn't filter oncomponent.Suggested fix: Add
app.kubernetes.io/component: serverto the server deployment's pod template and include it in the service selector.omjobOperator.enabled: true