-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add delay for monitor deletion #306
Comments
would you like to make for this feature @twardnw? ideally it should be a configuration that user can pass to IMC e.g.
|
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Reopening issues that inadvertently were closed as stale |
This issue is stale because it has been open for 60 days with no activity. |
We have a scenario where an ingress is "moved" across two namespaces as part of a blue/green deployment. However, to accomplish this, it requires deleting the ingress from one namespace, and recreating it on the other. Currently, the ICM deletes the monitor immediately when the ingress is removed, and then creates a new monitor as soon as the creationDelay passes. It would be good to have a configurable deleteDelay to prevent this from occurring.
The text was updated successfully, but these errors were encountered: