In kubenetes env, if runtime pod number is big and akka.coordinated-shutdown.phases.actor-system-terminate_timeout is low(e.g default value is 30 s), this may lead to the runtime pods are not deleted completely after execute helm delete/uninstall xxx, because when timeout happens, the cleanup is not executed finished.
In such a case, need to increase relative timeout value, it is better to make these timeout value configurable.
Fix https://github.com/apache/openwhisk-deploy-kube/issues/652
In kubenetes env, if runtime pod number is big and
akka.coordinated-shutdown.phases.actor-system-terminate_timeoutis low(e.g default value is30 s), this may lead tothe runtime pods are not deleted completely after execute helm delete/uninstall xxx, because when timeout happens, thecleanupis not executed finished.In such a case, need to increase relative timeout value, it is better to make these timeout value configurable.
Another brother pr: https://github.com/apache/openwhisk/pull/5028