Fargate fluentbit is always using default scheduler on Fargate only cluster and pods fail to comeup.

Fargate fluentbit is using default scheduler even after creating a fargate profile with the name "aws-cloudwatch"

Provide a link to the example/module related to the question

https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/blob/a9963f4a0e168f73adb033be594ac35868696a91/tests/complete/main.tf#L129

Additional context

I have configured blueprints to install fulentbit on my Fargate only cluster. But the pods are not coming withe the following error.

FailedScheduling 4m7s (x258 over 21h) default-scheduler 0/13 nodes are available: 1 Too many pods, 12 node is filtered out by the prefilter resul │ │ t. preemption: 0/13 nodes are available: 1 No preemption victims found for incoming pod, 12 Preemption is not helpful for scheduling.

My blueprint configuration looks like :

enable_fargate_fluentbit = true fargate_fluentbit = { flb_log_cw = true schedulerName = "Fargate" } fargate_fluentbit_cw_log_group = { name = "/fargate-fluentbit-logs" name_prefix = "${var.project_name}-${var.infra_env}" retention = var.infra_env == "dev" ? 7 :30 }

Am i missing any configuration?

aws-ia / terraform-aws-eks-blueprints-addons