aws-samples / aws-samples/amazon-cloudwatch-container-insights
0/6 nodes are available: 1 Too many pods, 5 node(s) didn't match Pod's node affinity/selector.
- Dominant language
- Shell
- Stars
- 178
- Forks
- 117
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 3
Description
Hi,
I have followed the [Quick Start Container Insights](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-quickstart.html) - tutorial.
I used the following command:
```
ClusterName='clusterName'
LogRegion='logRegion'
FluentBitHttpPort='2020'
FluentBitReadFromHead='Off'
[[ ${FluentBitReadFromHead} = 'On' ]] && FluentBitReadFromTail='Off'|| FluentBitReadFromTail='On'
[[ -z ${FluentBitHttpPort} ]] && FluentBitHttpServer='Off' || FluentBitHttpServer='On'
curl https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/quickstart/cwagent-fluent-bit-quickstart.yaml | sed 's|{{cluster_name}}|'${ClusterName}'|;s|{{region_name}}|'${LogRegion}'|;s|{{http_server_toggle}}|"'${FluentBitHttpServer}'"|;s|{{http_server_port}}|"'${FluentBitHttpPort}'"|;s|{{read_from_head}}|"'${FluentBitReadFromHead}'"|;s|{{read_from_tail}}|"'${FluentBitReadFromTail}'"|' | kubectl apply -f -
```
It applied successfully, however, the pods are err'ing out with the following error:
`0/6 nodes are available: 1 Too many pods, 5 node(s) didn't match Pod's node affinity/selector.`

What am I doing wrong? For reference, I am using EKS with Fargate. I read online about removing the tolerations, however, i'm unsure if this would fix the issue. And I thought about adding the `nodeSelector` key, but unsure where exactly to put it inside the `.yaml` file that is downloaded.
Your assistance would be great!
Thank you.
Contributor guide
Research direction
Start with the Quick Start Container Insights documentation and the referenced cwagent-fluent-bit-quickstart.yaml manifest. Investigate the reported Kubernetes scheduling error in the stated EKS with Fargate environment, including the manifest's affinity and toleration settings. Done means determining whether the manifest supports this environment and documenting the required guidance or incompatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, shell
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100