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

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/05/04 16:57:25 UTC

[GitHub] [flink-kubernetes-operator] tweise commented on pull request #195: [FLINK-27468] Recover missing deployments and other cancel/upgrade improvements for 1.15

tweise commented on PR #195:
URL: https://github.com/apache/flink-kubernetes-operator/pull/195#issuecomment-1117586637

   @gyfora one question regarding the motivations to delete a deployment externally: This could be used as escape hatch by users that want to term a misbehaving deployment and have problems removing the CR (which we discussed in the past). I wonder if by default we should or should not try to bring back deployments? And if the default is to try that, what do we advise in the case where a CR update isn't possible (for example due to incompatible CRD update or issue with the operator)?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org