stevenpyzhang opened a new pull request, #468:
URL: https://github.com/apache/flink-kubernetes-operator/pull/468
## What is the purpose of the change
Delete the Job manager resources first when deleting a standalone Flink
cluster as part of an upgrade in order to prevent HA configmaps from getting
cleaned up. As described in the ticket, I was seeing job HA data getting
deleted between cluster upgrades.
## Brief change log
Changed the resource clean up order from TM then JM to JM then TM for
standalone clusters.
## Verifying this change
Manually verified when upgrading a standalone session cluster with a
SessionJob running on it, configmaps didn't get cleaned up after switching
operator to deleting JM resources first.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changes to the `CustomResourceDescriptors`:
no
- Core observer or reconciler logic that is regularly executed: no
## Documentation
- Does this pull request introduce a new feature? no
--
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]
