You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem are you trying to solve?
expireAfter field only support specifying number values in s,m,h unit and but if we want to expired node only during less peak hour at that time expireAfter isn't useful so if we add support for cron as well then we can specify cron expression which will expire node at less peak hour, eg every sunday night 1am How important is this feature to you?
this feature will help to expire node at the specified time only properly and will give fine grain control over node expiry
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
What problem are you trying to solve?
expireAfter field only support specifying number values in s,m,h unit and but if we want to expired node only during less peak hour at that time expireAfter isn't useful so if we add support for cron as well then we can specify cron expression which will expire node at less peak hour, eg every sunday night 1am
How important is this feature to you?
this feature will help to expire node at the specified time only properly and will give fine grain control over node expiry
The text was updated successfully, but these errors were encountered: