aws-vpc-cni: CRDs needs to be in crds folder

[vadim-a-nesterov]

Hi,

we having issues with installing aws-vpc-cni and having race condition with ENIConfig CRDs, because helmwave is trying to create CRDs before CRD definition is applied.

The aws-vpc-cni chart should be fixed, CRDs must be in separate folder like here

STDERR:
  Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "eu-west-1a" namespace: "" from "": no matches for kind "ENIConfig" in version "crd.k8s.amazonaws.com/v1alpha1"
  ensure CRDs are installed first, resource mapping not found for name: "eu-west-1b" namespace: "" from "": no matches for kind "ENIConfig" in version "crd.k8s.amazonaws.com/v1alpha1"
  ensure CRDs are installed first]

COMBINED OUTPUT:
  Release "aws-vpc-cni" does not exist. Installing it now.
  Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "eu-west-1a" namespace: "" from "": no matches for kind "ENIConfig" in version "crd.k8s.amazonaws.com/v1alpha1"
  ensure CRDs are installed first, resource mapping not found for name: "eu-west-1b" namespace: "" from "": no matches for kind "ENIConfig" in version "crd.k8s.amazonaws.com/v1alpha1"
  ensure CRDs are installed first]
in ./helmfile.yaml: failed processing release aws-vpc-cni: command "/usr/local/bin/helm" exited with non-zero status:

[jayanthvn]

Thanks, we will restructure the folders and also update the installation doc to install CRDs and then run helm upgrade.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

[jayanthvn]

This is been actively worked on.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.