tillrohrmann commented on pull request #13644: URL: https://github.com/apache/flink/pull/13644#issuecomment-714303198
Concerning trying to cover the case where the configMaps are accidentally deleted or modified by the user, I think that in the general case our approach won't work. In the current implementation only the leader is allowed to re-create the configMap. This won't work if the configMap deletion coincides with the leader death. Even if any leader contender is allowed to re-create the configMap, then we still risk to lose all persisted information because only the dead leader knew the state. Hence, I believe we should rather fail hard if we detect a modification or deletion and tell the user because we cannot guarantee that we didn't lose relevant information. In particular to test these kind of scenarios (how does the system behave in corner cases), I believe that an integration test with K8s is actually required. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
