Skip to content

Bug 1986453: Check for API server and node versions skew#2658

Merged
openshift-merge-robot merged 1 commit into
openshift:masterfrom
QiWang19:no-skew-check
Jul 27, 2021
Merged

Bug 1986453: Check for API server and node versions skew#2658
openshift-merge-robot merged 1 commit into
openshift:masterfrom
QiWang19:no-skew-check

Conversation

@QiWang19
Copy link
Copy Markdown
Member

@QiWang19 QiWang19 commented Jul 2, 2021

ref: https://issues.redhat.com/browse/OCPNODE-595
replace #2552

- What I did

Check for API server and node versions skew.
Update with the message the Kube API version is skew too far, but do not force
Upgradeable=False according to enhancement https://github.com/openshift/enhancements/pull/762/files

- How to verify it

- Description for the changelog

@QiWang19
Copy link
Copy Markdown
Member Author

QiWang19 commented Jul 2, 2021

/assign @sinnykumari

Copy link
Copy Markdown
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some initial questions/comments

Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Copy link
Copy Markdown
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a few more comments

/hold

Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 2, 2021
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

@QiWang19 I know that this PR is based on someone else's previous PR, but I think we can refine it. What most of my comments are asking for is: using that work as a baseline, how can we make this into an understandable & actionable status for a user. Also keep in mind a pool can be large, so the info needs to be easy to consume if we have, say, 50 nodes that have unsupported skew.

Users can get into this situation bc a pool is paused and so it did not upgrade to match the apiserver and is still at an older version. They will likely have to let those pools upgrade (to at a minimum a supported skew) before they can initiate another clusterwide upgrade (which would cause the kubeapiserver to get even further away). So we need to think about telling them the state in a meaningful way, but also give them some hint about what they need to do to remedy it.

Happy to discuss further if you have any questions. =)

@kikisdeliveryservice kikisdeliveryservice changed the title Check for API server and node versions skew [OCPNODE-595] Check for API server and node versions skew Jul 3, 2021
@QiWang19 QiWang19 force-pushed the no-skew-check branch 4 times, most recently from 4cf72ac to 3664ebe Compare July 6, 2021 20:25
@QiWang19
Copy link
Copy Markdown
Member Author

QiWang19 commented Jul 6, 2021

@kikisdeliveryservice Thanks for the explanation. I have cleaned up some reviews. PTAL.

@QiWang19
Copy link
Copy Markdown
Member Author

QiWang19 commented Jul 7, 2021

/retest

2 similar comments
@QiWang19
Copy link
Copy Markdown
Member Author

QiWang19 commented Jul 8, 2021

/retest

@QiWang19
Copy link
Copy Markdown
Member Author

QiWang19 commented Jul 9, 2021

/retest

@QiWang19
Copy link
Copy Markdown
Member Author

@kikisdeliveryservice Thanks for the explanation. I have cleaned up some reviews. Could you PTAL?

Copy link
Copy Markdown
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a few more comments

Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
Comment thread pkg/operator/status.go Outdated
@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

Just noting that when this is done, we need to get the commits updated so Qi is a co-author.

Comment thread pkg/operator/status.go Outdated
@rphillips
Copy link
Copy Markdown
Contributor

I tested this PR locally and it does report the skew, and go back to no skew as expected.

Copy link
Copy Markdown
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one last thing otherwise looks good

Comment thread pkg/operator/status.go Outdated
Co-authored-by: Qi Wang <qiwan@redhat.com>
Signed-off-by: Qi Wang <qiwan@redhat.com>
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
Copy link
Copy Markdown
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for all of the work on this. I think we've gotten it to a good state.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 27, 2021
@rphillips
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 27, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kikisdeliveryservice, QiWang19, rphillips

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [kikisdeliveryservice]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 27, 2021

@QiWang19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-disruptive 61c86bf43e472ef41b55fc826940026bebabb547 link /test e2e-aws-disruptive
ci/prow/okd-e2e-aws 1471d2c link /test okd-e2e-aws
ci/prow/e2e-aws-upgrade-single-node 1471d2c link /test e2e-aws-upgrade-single-node
ci/prow/e2e-aws-workers-rhel7 1471d2c link /test e2e-aws-workers-rhel7
ci/prow/e2e-ovn-step-registry 1471d2c link /test e2e-ovn-step-registry
ci/prow/e2e-aws-techpreview-featuregate 1471d2c link /test e2e-aws-techpreview-featuregate
ci/prow/e2e-aws-serial 1471d2c link /test e2e-aws-serial
ci/prow/e2e-vsphere-upgrade 1471d2c link /test e2e-vsphere-upgrade

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 9c07edd into openshift:master Jul 27, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 27, 2021

@QiWang19: All pull requests linked via external trackers have merged:

Bugzilla bug 1986453 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1986453: Check for API server and node versions skew

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

wking added a commit to wking/machine-config-operator that referenced this pull request Mar 26, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare-RHEL support, and I want the Node lister to look
for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

but we are ok with RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0
wking added a commit to wking/machine-config-operator that referenced this pull request Mar 26, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare-RHEL support, and I want the Node lister to look
for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

but we are ok with RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0
wking added a commit to wking/machine-config-operator that referenced this pull request Mar 27, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare-RHEL support, and I want the Node lister to look
for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

but we are ok with RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0
wking added a commit to wking/machine-config-operator that referenced this pull request Mar 27, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare-RHEL support, and I want the Node lister to look
for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

but we are ok with RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 3, 2025
The kubelet skew guard is from 1471d2c (Bug 1986453: Check for API
server and node versions skew, 2021-07-27, openshift#2658).  But the Kube API
server also landed a similar guard in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal from MCO-guards to KAS-guards, so I'm not clear on why
the MCO guard landed.  This commit drops it, to consolidate around the
KAS-side guard.
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 3, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare-RHEL support, and I want the Node lister to look
for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

but we are ok with RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 4, 2025
The kubelet skew guard is from 1471d2c (Bug 1986453: Check for API
server and node versions skew, 2021-07-27, openshift#2658).  But the Kube API
server also landed a similar guard in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal from MCO-guards to KAS-guards, so I'm not clear on why
the MCO guard landed.  This commit drops it, to consolidate around the
KAS-side guard.
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 4, 2025
The kubelet skew guard is from 1471d2c (Bug 1986453: Check for API
server and node versions skew, 2021-07-27, openshift#2658).  But the Kube API
server also landed a similar guard in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal from MCO-guards to KAS-guards, so I'm not clear on why
the MCO guard landed.  This commit drops it, to consolidate around the
KAS-side guard.
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 15, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare, package-managed RHEL support.  I'd initially
thought about looking for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

while excluding RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0

But instead of switching on osImage, I'm using the
node.openshift.io/os_id label to find package-managed RHEL Nodes.  The
machine-config operator is setting up the label [1] based on the ID
value in /etc/os-release.  On RHCOS instances, the ID value is 'rhcos'
[2].  On package-managed RHEL, it's 'rhel' [3,4].

[1]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/templates/worker/01-worker-kubelet/_base/units/kubelet.service.yaml#L19-L31
[2]: https://github.com/openshift/os/blob/41f6a028d37b750db0bf4257447d809bd9cbe4bf/manifest-ocp-rhel-9.6.yaml#L41
[3]: https://github.com/openshift/enhancements/blob/ea465e192bfb58ec8654f1c904a4af68777f68ec/enhancements/rhcos/split-rhcos-into-layers.md?plain=1#L416
[4]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/pkg/daemon/osrelease/osrelease.go#L69
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 15, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare, package-managed RHEL support.  I'd initially
thought about looking for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

while excluding RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0

But instead of switching on osImage, I'm using the
node.openshift.io/os_id label to find package-managed RHEL Nodes.  The
machine-config operator is setting up the label [1] based on the ID
value in /etc/os-release.  On RHCOS instances, the ID value is 'rhcos'
[2].  On package-managed RHEL, it's 'rhel' [3,4].

[1]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/templates/worker/01-worker-kubelet/_base/units/kubelet.service.yaml#L19-L31
[2]: https://github.com/openshift/os/blob/41f6a028d37b750db0bf4257447d809bd9cbe4bf/manifest-ocp-rhel-9.6.yaml#L41
[3]: https://github.com/openshift/enhancements/blob/ea465e192bfb58ec8654f1c904a4af68777f68ec/enhancements/rhcos/split-rhcos-into-layers.md?plain=1#L416
[4]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/pkg/daemon/osrelease/osrelease.go#L69
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 15, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare, package-managed RHEL support.  I'd initially
thought about looking for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

while excluding RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0

But instead of switching on osImage, I'm using the
node.openshift.io/os_id label to find package-managed RHEL Nodes.  The
machine-config operator is setting up the label [1] based on the ID
value in /etc/os-release.  On RHCOS instances, the ID value is 'rhcos'
[2].  On package-managed RHEL, it's 'rhel' [3,4].

[1]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/templates/worker/01-worker-kubelet/_base/units/kubelet.service.yaml#L19-L31
[2]: https://github.com/openshift/os/blob/41f6a028d37b750db0bf4257447d809bd9cbe4bf/manifest-ocp-rhel-9.6.yaml#L41
[3]: https://github.com/openshift/enhancements/blob/ea465e192bfb58ec8654f1c904a4af68777f68ec/enhancements/rhcos/split-rhcos-into-layers.md?plain=1#L416
[4]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/pkg/daemon/osrelease/osrelease.go#L69
wking added a commit to wking/machine-config-operator that referenced this pull request Apr 29, 2025
The kubelet skew guards are from 1471d2c (Bug 1986453: Check for
API server and node versions skew, 2021-07-27, openshift#2658).  But the Kube
API server also landed similar guards in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal form MCO-guards to KAS-guards, so I'm not entirely clear
on why the MCO guards landed at all.  But it's convenient for me that
they did, because while I'm dropping them here, I'm recycling the Node
lister for a new check.

4.19 is dropping bare, package-managed RHEL support.  I'd initially
thought about looking for RHEL entries like:

  osImage: Red Hat Enterprise Linux 8.6 (Ootpa)

while excluding RHCOS entries like:

  osImage: Red Hat Enterprise Linux CoreOS 419.96.202503032242-0

But instead of switching on osImage, I'm using the
node.openshift.io/os_id label to find package-managed RHEL Nodes.  The
machine-config operator is setting up the label [1] based on the ID
value in /etc/os-release.  On RHCOS instances, the ID value is 'rhcos'
[2].  On package-managed RHEL, it's 'rhel' [3,4].

[1]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/templates/worker/01-worker-kubelet/_base/units/kubelet.service.yaml#L19-L31
[2]: https://github.com/openshift/os/blob/41f6a028d37b750db0bf4257447d809bd9cbe4bf/manifest-ocp-rhel-9.6.yaml#L41
[3]: https://github.com/openshift/enhancements/blob/ea465e192bfb58ec8654f1c904a4af68777f68ec/enhancements/rhcos/split-rhcos-into-layers.md?plain=1#L416
[4]: https://github.com/openshift/machine-config-operator/blob/ddc18e84f4a0650e0e87aa0a4f90f9cf01b5259c/pkg/daemon/osrelease/osrelease.go#L69
umohnani8 pushed a commit to umohnani8/machine-config-operator that referenced this pull request Aug 6, 2025
The kubelet skew guard is from 1471d2c (Bug 1986453: Check for API
server and node versions skew, 2021-07-27, openshift#2658).  But the Kube API
server also landed a similar guard in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal from MCO-guards to KAS-guards, so I'm not clear on why
the MCO guard landed.  This commit drops it, to consolidate around the
KAS-side guard.
umohnani8 pushed a commit to umohnani8/machine-config-operator that referenced this pull request Oct 31, 2025
The kubelet skew guard is from 1471d2c (Bug 1986453: Check for API
server and node versions skew, 2021-07-27, openshift#2658).  But the Kube API
server also landed a similar guard in
openshift/cluster-kube-apiserver-operator@9ce4f74775 (add
KubeletVersionSkewController, 2021-08-26,
openshift/cluster-kube-apiserver-operator#1199).
openshift/enhancements@0ba744e750 (eus-upgrades-mvp: don't enforce
skew check in MCO, 2021-04-29, openshift/enhancements#762) had shifted
the proposal from MCO-guards to KAS-guards, so I'm not clear on why
the MCO guard landed.  This commit drops it, to consolidate around the
KAS-side guard.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants