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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/08/18 13:29:00 UTC

[jira] [Resolved] (FLINK-28218) Add readiness and liveness probe to k8s operator

     [ https://issues.apache.org/jira/browse/FLINK-28218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora resolved FLINK-28218.
--------------------------------
    Resolution: Fixed

merged to main 199ed194f81502d3e146265c1694eddaf07e838e

> Add readiness and liveness 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.1.0
>            Reporter: Márton Balassi
>            Assignee: Peter Vary
>            Priority: Major
>              Labels: pull-request-available
>
> 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.10#820010)