[
https://issues.apache.org/jira/browse/FLINK-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129121#comment-17129121
]
Yang Wang commented on FLINK-17976:
-----------------------------------
Thanks for the further testing. Address your comments inline.
* If you mean the jobmanager web dashboard are public accessible when service
exposed type is {{LoadBalancer}}, then it is true. Just as you say, maybe we
need to add a warning for users. However, providing a separate LB for each
Flink cluster is too expensive, users usually use customized ingress.
* Currently, if the TaskManager is launched successfully, it could be released
after idle timeout. However, it seems that your cluster does not have enough
resource, then all the pods are pending. It is an expected behavior just like
YARN.
* If you kill/delete an active pod, it will be terminated and a new one will
be allocated. So the pending pods increase. Once it is launched and register to
Flink ResourceManager, the pending pods will decrease.
* Flink on K8s should work for all versions greater than 1.9.
* I think it is a K8s cluster specific behavior. I have asked some K8s
experts. In alicloud K8s, usually rescaling the K8s cluster will not affect the
running applications. If the current region does not have enough machines, then
the running app could not be guaranteed. It seems we could not do anything in
Flink side.
> Test native K8s integration
> ---------------------------
>
> Key: FLINK-17976
> URL: https://issues.apache.org/jira/browse/FLINK-17976
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Till Rohrmann
> Assignee: Robert Metzger
> Priority: Critical
> Labels: release-testing
> Fix For: 1.11.0
>
> Attachments: enough_tm_wait_5min.txt
>
>
> Test Flink's native K8s integration:
> * session mode
> * application mode
> * custom Flink image
> * custom configuration and log properties
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
