Open mblaschke-daimlertruck opened 2 months ago
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/sig cli
Doesn't this exist https://github.com/kubernetes/kubernetes/blob/32077a1c008a59d797e4f4ae8717a0dbbe3c3db7/staging/src/k8s.io/kubectl/pkg/cmd/version/version.go#L164-L167 prints warning if https://github.com/kubernetes/kubernetes/blob/32077a1c008a59d797e4f4ae8717a0dbbe3c3db7/staging/src/k8s.io/kubectl/pkg/cmd/version/skew_warning.go#L34-L54 detects skew?
Is the ask that there should be an option for kubectl to return an error instead of warning if the skew is greater than 1?
Is the ask that there should be an option for kubectl to return an error instead of warning if the skew is greater than 1?
Yes, that is correct. I missed that part.
/transfer kubectl
/triage accepted /good-first-issue It seems like there were a few plugins to address this in the past that have gone missing.
@mpuckett159: This request has been marked as suitable for new contributors.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
/assign
What would you like to be added?
add an flag for
kubectl version
which fails if the client version exceeds the supported minor version skew of +/-1--warnings-as-errors
isn't working as this only treats warnings as errors when received from the server. thekubectl version
warning is a client side warning.on the other side
--match-server-version
is too strict.or add
kubectl check-support
or something similarWhy is this needed?
avoid running unsupported kubectl versions