Dmytro Sirant

@FernandoMiguel but using toast(data.kubectl_path_documents.karpenter_default_provisioner.documents) lead to the bigger problem. Each time when you do changes to the provisioner it will delete current one and create a new one. The worst...

@FernandoMiguel It's strange because of in my case, when I'm using ``` data "kubectl_path_documents" "karpenter_provisioners" { pattern = "${path.module}/provisioners/*.yaml" vars = { azs = join(",", local.azs) iam-instance-profile-id = "${var.eks_iam_instance_profile_id}" eks-cluster-id...

> What is provided is just one way of deploying multiple provisioners - users are free to choose the method that best suits their needs. an alternative that would resolve...

Have the same problem with `kubecost` and `karpenter` OCI registries. I have the latest versions (but it changes nothing): ``` Terraform version: 1.3.3 Helm Provider version: 2.7.1 Helm Provider version:...

> For me assuming of aws roles did not work in any way through a profile. I found the following workaround for the assuming role: > > ```shell > $(aws...

I was able to solve the problem by running ``` docker logout public.ecr.aws ``` as explained [here](https://docs.aws.amazon.com/AmazonECR/latest/public/public-troubleshooting.html)

Could anyone check it please, it affects our workload