-
Notifications
You must be signed in to change notification settings - Fork 15
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
Tracking: Support human-readable duration format in CRDs #649
Comments
lfrancke
moved this from Refinement Acceptance: Waiting for
to Ready for Development
in Stackable Engineering
Sep 22, 2023
sbernauer
moved this from Ready for Development
to Development: In Progress
in Stackable Engineering
Sep 22, 2023
This was referenced Oct 9, 2023
Techassi
changed the title
Support human-readable duration format in CRDs
Tracking: Support human-readable duration format in CRDs
Oct 11, 2023
This was referenced Oct 11, 2023
Techassi
moved this from Development: In Progress
to Development: Done
in Stackable Engineering
Nov 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I AS A USER want to not put in random big integer numbers in CRDs such as
terminationgraceperiodseconds: 8763762374
, but instead want to have some human readable duration such asterminationgraceperiod: 42h
.I AS A STACKABLE DEVELOPER want to not implement this in all operators, so have it in operator-rs
Requirements
s,m,h,d,w
M,y
as the implementation is more complicated but we might need this for ca certificate lifetime.5seconds
or42minutes
. K8s does not support this as wellImplementation decisions
Duration
with inner typestd::time::Duration
impl Deref for Duration
withTarget = std::time::Duration
std::time::Duration
so that, for example, log messages are consistent to the k8s way of formatting durations.Implementation checklists
Tasks
Operator Tasks
The text was updated successfully, but these errors were encountered: