Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
codewithabhi17 opened this issue Jun 2, 2024 · 2 comments
Labels

Comments

@codewithabhi17
Copy link

codewithabhi17 commented Jun 2, 2024

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

enable_fargate_fluentbit = true

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?

Copy link

github-actions bot commented Jul 3, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jul 3, 2024
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant