-
Bug
-
Resolution: Unresolved
-
Normal
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
CLOUD Sprint 276
-
1
-
In Progress
-
Bug Fix
-
* Previously the MachineHealthCheck CR did not show the default value for the maxUnhealthy field. With this update, the CR also documents the value it defaults to when not set.
-
None
-
None
-
None
-
None
Description of problem:
The command oc explain machinehealthchecks.machine.openshift.io.spec.maxUnhealthy does not show the default maxUnhealthy value:
Version-Release number of selected component (if applicable):
openshift 4.19+
$ oc explain machinehealthchecks.machine.openshift.io.spec.maxUnhealthy
GROUP: machine.openshift.io
KIND: MachineHealthCheck
VERSION: v1beta1
FIELD: maxUnhealthy <Object>
DESCRIPTION:
Any farther remediation is only allowed if at most "MaxUnhealthy" machines
selected by
"selector" are not healthy.
Expects either a postive integer value or a percentage value.
Percentage values must be positive whole numbers and are capped at 100%.
Both 0 and 0% are valid and will block all remediation.
Only documentation has the default value mentioned.
Customer or support engineers who rely on CLI documentation, will not get complete idea.Shall I raise BUG or RFE to address this gap?
Actual results:
The default value is missing
Expected results:
Expecting default value i.e. 100%
Additional info:
Only official documentation has the default value mentioned. Customer or support engineers who rely on CLI documentation, will not get complete idea.
- blocks
-
-
- POST
-
- is cloned by
-
-
- POST
-
-
-
- Closed
-
-
-
- Closed
-
- links to
