EKSA vSphere Cluster upgrade plan shows cilium version when cilium is skipped in cluster config file

[saiteja313]

What happened:

1. Create EKSA vSphere cluster
2. Install cilium OSS version. not the default Cilium that gets installed as part of EKSA Cluster creation
3. Configured cilium in EKSA Cluster config file with skipUpgrade: true for cilium.

spec:
  clusterNetwork:
    cniConfig:
      cilium: 
        skipUpgrade: true

4. Although above config was added before the cluster creation, when we run eksctl anywhere upgrade plan cluster command, output shows, eksctl anywhere is going to upgrade cilium as well.

NAME     CURRENT VERSION      NEXT VERSION
cilium      v1.13.9-eksa.1                 v1.13.20-eksa.1

https://anywhere.eks.amazonaws.com/docs/clustermgmt/cluster-upgrades/upgrade-overview/

What you expected to happen:

• upgrade plan should show cilium as skipped

NAME     CURRENT VERSION      NEXT VERSION
cilium      v1.13.9-eksa.1                 skipUpgradeTrue

How to reproduce it (as minimally and precisely as possible):

• same instructions as above

Anything else we need to know?: n/a

Environment: vSphere

• EKS Anywhere Release: v0.19 and v0.20.6