You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ConradJam (Jira)" <ji...@apache.org> on 2022/06/23 12:46:00 UTC

[jira] [Commented] (FLINK-28218) Add readiness and liveliness probe to k8s operator

    [ https://issues.apache.org/jira/browse/FLINK-28218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558049#comment-17558049 ] 

ConradJam commented on FLINK-28218:
-----------------------------------

Hi [~mbalassi] , I have idea for readiness and liveliness probe to k8s operator

We can judge the job Rest address of SessionCluster or JobCluster and test its connectivity by requesting its overview, such as localhost:8081/overview 

What do you think ？

 

> Add readiness and liveliness probe to k8s operator
> --------------------------------------------------
>
>                 Key: FLINK-28218
>                 URL: https://issues.apache.org/jira/browse/FLINK-28218
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.0.0
>            Reporter: Márton Balassi
>            Priority: Major
>
> Let us add readiness and liveness probes to the operator, we could expose relevant HTTP endpoints for this.
> I have observed cases recently where even though the operator pod was running it could not do its job due to missing rolebindings or misconfigured dynamic namespaces.
> https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)