Bug: EKS requires managed nodegroups and Fargate profiles to align with control plane before upgrade

[bryantbiggs]

Expected Behaviour

EKS requires nodes created by managed nodegroups and Fargate profiles to align with the control plane version (minor versions to be the same) before it will allow the control plane to upgrade

Current Behaviour

Currently, eksup reports only on results as they related to the Kubernetes version skew support. This means that nodes created by a managed nodegroup or Fargate profile that are 1 minor version behind the control plane version are shown in the results as a recommended remediation (upgrade to align on versions), and not a required. Per EKS requirements, this should be shown as a required remediation since users will not be able to upgrade until they align the node versions to the control plane

Code snippet

N/A

Possible Solution

Any nodes created by managed nodegroups or Fargate profiles should report as required remediation if they do not match the control plane version

Steps to Reproduce

N/A

eksup version

latest

Operating system

macOS x86_64

Error output

No response