[Doc] Deprecate ServiceUnhealthySecondThreshold
and DeploymentUnhealthySecondThreshold
#1685
Labels
docs
Improvements or additions to documentation
As per #1664 and #1665, the latest kuberay operator will not respect
DeploymentUnhealthySecondThreshold
andServiceUnhealthySecondThreshold
fields at all.Ideally, we should inform users that these fields are deprecated, and we thought that the kubebuilder could do this for us by using the
+kubebuilder:deprecatedversion
marker. However, it turns out that this marker doesn't work for us because it only works at the CRD root level, and no similar marker works at the field level.Here, in this issue, I'd like to discuss alternatives to kubebuilder code generation:
I believe the first option is trivial, and the second option is a must.
How about the third and the fourth? Are they good to have?
cc @kevin85421
The text was updated successfully, but these errors were encountered: