Tekton Buildpacks PVC gives persistentvolume-controller waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator about tekton-argocd-eks

[jonashackt]

Seems to be an upgrade problem to EKS with K8s version 1.23: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-1.23 and also https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html:

The Amazon EBS CSI driver isn't installed when you first create a cluster. To use the driver, you must add it as an Amazon EKS add-on or as a self-managed add-on.

There's also https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi-migration-faq.html

CSI drivers:

    replace the Kubernetes "in-tree" storage drivers that exist in the Kubernetes project source code.

    work with storage providers, such as Amazon EBS.

https://kubernetes.io/blog/2021/12/10/storage-in-tree-to-csi-migration-status-update/

[jonashackt]

Maybe our "old" StorageClass definition overrides the default new definition shipped with a new 1.23+ EKS cluster? Currently in https://github.com/jonashackt/tekton-argocd-eks/blob/main/tekton/misc/kustomization.yaml the StorageClass is installed. This sadly overrides the default, as needed in #60. So I will delete the current cluster, create a new one and have a look into the StorageClass. Running aws eks describe-addon-versions --addon-name aws-ebs-csi-driver as described in https://docs.aws.amazon.com/eks/latest/userguide/managing-ebs-csi.html showed that the EKS EBS CSI driver seems to be installed as an EKS addon.