tweise opened a new pull request #46: URL: https://github.com/apache/flink-kubernetes-operator/pull/46
The PR is a sketch for handling a deployment that results in a permanent error state (invalid service account) that would require a CR update to resolve. I do not particularly like the exception based flow, but this scenario requires access to the k8s client. The event logged looks like this (kubectl describe): ``` ReplicaFailure FailedCreate 4h48m JobManagerDeployment pods "basic-example-d5c476cb6-" is forbidden: error looking up service account default/invalid-flink-operator: serviceaccount "invalid-flink-operator" not found ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
