Support for the service has long graceful shutdown time.

[duong-se]

Is your feature request related to a problem? Please describe. My service currently has a graceful shutdown time of 24 seconds from the moment it receives a SIGTERM signal. However, if a rollout restart triggers a service restart before the secrets expire but within less than 24 seconds, the service doesn't have enough time to handle the final requests, leading to an 'invalid credentials' error.

Describe the solution you'd like The Vault secrets operator can support graceful shutdown parameters for the service so that when the service receives a restart, it can handle requests before the credentials are revoked.

Describe alternatives you've considered Or should we remove jitter by random number and let the user define graceful revoke time?

Additional context NA