[ https://issues.apache.org/jira/browse/FLINK-26538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503179#comment-17503179 ]
Thomas Weise commented on FLINK-26538: -------------------------------------- In this case operator should restart the deployment; it's not for dealing with reconciliation issue but for problems with the Flink deployment itself. > Ability to restart deployment w/o spec change > --------------------------------------------- > > Key: FLINK-26538 > URL: https://issues.apache.org/jira/browse/FLINK-26538 > Project: Flink > Issue Type: Sub-task > Components: Kubernetes Operator > Reporter: Thomas Weise > Priority: Major > > Operator should allow restart of the Flink deployment w/o any other spec > change. This provides the escape hatch for an operator to recover a > deployment that has gone into a bad state (for whatever reason including > memory leaks, hung JVM etc.) without direct access to the k8s cluster. This > can be addressed by adding a restartNonce to the CRD. > -- This message was sent by Atlassian Jira (v8.20.1#820001)