:wave: we're trying to migrate to the new Flink op...
# troubleshooting
e
πŸ‘‹ we're trying to migrate to the new Flink operator and we've noticed that both the pod ( and container names (
flink-main-container
for both TM and JM) have changed... to make the migration to the flink operator seamless we were hoping there was a way to make sure those could two values could remain consist but haven't been able to do some in the manifest file...
Copy code
apiVersion: <http://flink.apache.org/v1beta1|flink.apache.org/v1beta1>
kind: FlinkDeployment
metadata:
  labels:
    name: {{ .name }}
    app: {{ .appName }}
    env: {{ .env }}
    runtime-component: trickle
  annotations:
    <http://cloudplatform.shopify.io/scale-down-for-maintenance|cloudplatform.shopify.io/scale-down-for-maintenance>: "true"
spec:
  ...
  jobManager:
    ...
    podTemplate:
      spec:
        containers:
          - name: jobmanager
  taskManager:
    ...
    podTemplate:
      spec:
        containers:
        - name: taskmanager
  podTemplate:
    ...
    spec:
      ...
      containers:
        - name: flink-main-container
This is an example of what my manifest file looks like. We would also like to have some reusable configurations defined in the general outer
podTemplate
as well, instead of having duplicate configs for both TM and JM
podTemplate
.