Confusion and conflict between upgrade docs and "upgrade insights" feature

[Kalli]

The docs for updating a cluster suggest to proceed with a kubernetes upgrade in the following order:

...
Step 3: Update cluster control plane
Step 4: Update cluster components
...
Step 4.4
Update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.

But when you go to a cluster in the console page, the upgrade insights will warn you about any out of date add ons:

Upgrade insights identify possible issues that could impact Kubernetes cluster upgrades.

If you click to upgrade your cluster, to start the update control plane and nodes before updating the add ons (as per the eks-user-guide) you will get a warning about the upgrade insights. This prompted some confusion for me and my team.

• Perhaps the docs could be updated to reflect whether to upgrade the add-ons before the control plane and nodes (as per the upgrade insights) or after (as per the userguide).
• It isn't very clear whether the add ons should be updated to the default version for the current k8s version or if they need to be updated to the default for the k8s target version before upgrade insights will let you know upgrade without warning.