Lack of extended validation for resyncPeriod about grafana-operator HOT 4 CLOSED

@cnCloXie the problem is that 30d is not a valid duration, see here. You could write it as hours: resyncPeriod: 720h

from grafana-operator.

After internal discussion, we decided that we should add additional validation rules for resyncPeriod to our CRDs to make sure k8s API server accepts only those values that can be parsed by Go runtime.

from grafana-operator.

So let's solve this by making use of CRD validation, we can see an example on how to make sure you can't use anything above h

from grafana-operator.

Thank you guys !
Ah yes adding validation in the CR, complaining to the operator's logs or translating d/m/y into hours, either way will work for me which could make me myself be aware of my input mistake explicitly. Thank U for reply and the operator !

from grafana-operator.