The instructions to add the metallb and harbor packages fail with an error

[ianatmedacist]

What happened:
eksctl anywhere generate package metallb --source cluster > metallb.yaml
Error: this command is currently not supported
echo $?
255

The same thing happens with Harbor
eksctl anywhere generate package harbor --source cluster > harbor.yaml
Error: this command is currently not supported
echo $?
255

What you expected to happen:
It to generate the metallb package yaml per the instructions found here https://anywhere.eks.amazonaws.com/docs/tasks/packages/metallb/

How to reproduce it (as minimally and precisely as possible):
Install eksctl anywhere per the instructions with brew installing what is currently latest
Warning: aws/tap/eks-anywhere 0.10.1 already installed

Anything else we need to know?:

Environment:
MacOS Intel

[TerryHowe]

Packages is a gated feature in preview right now, so you have to export CURATED_PACKAGES_SUPPORT=true for access. That should be the problem I would think since you are running 0.10.1

[ianatmedacist]

Looks like I don't have the packageBundleController its looking for.
This cluster is 1.22 created with 0.10.1, the instructions make it sound like I should not have to add it but maybe I'm misreading them.

eksctl anywhere generate package metallb --source cluster > metallb.yaml
Error: error: the server doesn't have a resource type "packageBundleController"

The commands for adding the package bundle do not seem to work on 0.10.1 either.

➜  cluster-definitions git:(master) ✗ eksctl anywhere install packagecontroller --kube-version 1.22
Error: unknown flag: --kube-version
➜  cluster-definitions git:(master) ✗ eksctl anywhere install packagecontroller                    
Error: required flag(s) "filename" not set

Ok, apparently you have to create the cluster with export CURATED_PACKAGES_SUPPORT=true now. As it seems to add it during creation.

Also note that having this flag set to true in a cluster not created with CURATED_PACKAGES_SUPPORT=true it seems to interfere with destroying the management cluster.

Maybe these features should be marked with some sort of warning on the eks anywhere guide? I assumed they were GA already.

[jonahjon]

Were you able to install the packagecontroller on an EKS-A cluster?

[csplinter]

Closing due to no activity