Eric Xiao created FLINK-31941:
---------------------------------
Summary: Not backwards compatible naming for some kubernetes
resources
Key: FLINK-31941
URL: https://issues.apache.org/jira/browse/FLINK-31941
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Reporter: Eric Xiao
We are in the process of migrating all our workloads over to the Kubernetes
operator and noticed that some of the Kubernetes resources in the operator are
hardcoded and not consistent with how Flink previously defined them. This is
leading to us some downstream incompatibilities and some migration toil in our
monitoring and dashboards that have queries depending on the previous naming
schema.
I couldn't find exact definitions a task-manager or job-manager in the flink
repo, but this is what I have noticed, I may be wrong on my interpretations 😅.
h3. Deployment Names
Previously:
{code:java}
NAME READY UP-TO-DATE AVAILABLE AGE
trickle-job-manager 2/2 2 2 13d
trickle-task-manager 10/10 10 10 13d {code}
New (Flink Operator):
{code:java}
NAME READY UP-TO-DATE AVAILABLE AGE
trickle 2/2 2 2 6h25m
trickle-taskmanager 4/4 4 4 6h25m {code}
[1]
[https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-standalone/src/main/java/org/apache/flink/kubernetes/operator/utils/StandaloneKubernetesUtils.java#L29-L38]
h3. Pod Names
Previously:
{code:java}
NAME READY STATUS RESTARTS AGE
trickle-job-manager-65d95d4854-lgmsm 1/1 Running 0 13d
trickle-job-manager-65d95d4854-vdzl8 1/1 Running 0 5d
trickle-task-manager-86c85cf647-46nxh 1/1 Running 0 5d
trickle-task-manager-86c85cf647-ct6c5 1/1 Running 0 5d
trickle-task-manager-86c85cf647-h894q 1/1 Running 0 5d
trickle-task-manager-86c85cf647-kpr5x 1/1 Running 0 5d{code}
New (Flink Operator):
{code:java}
NAME READY STATUS RESTARTS AGE
trickle-58f895675f-9m5wm 1/1 Running 0 25h
trickle-58f895675f-n4hhv 1/1 Running 0 25h
trickle-taskmanager-6f9f64b9b9-857lv 1/1 Running 0 25h
trickle-taskmanager-6f9f64b9b9-cnsrx 1/1 Running 0 25h{code}
----
The pod names stem from the deployment names, so a fix to update the deployment
names may also fix the pod names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
