Open mickael-ange opened 3 years ago
We have the same issue. This issue has been spamming our BotKube channel since way before #625.
Same here, same error message:
invalid capacity 0 on image filesystem
EKS on fargate too.
I see the same Event Type warning when I run "kubectl describe node instance_name" where instance_name is the dns name of a EKS Local Clusters control-plane,master node.
Same warning, but I can't see any bad effects from it
Community Note
Tell us about your request What do you want us to build?
Since https://github.com/aws/containers-roadmap/issues/625 has been shipped, we are starting to scheduling workloads on EKS Fargate. Every time a new Fargate node is created, the node reports the following warning:
invalid capacity 0 on image filesystem
.We use BotKube to monitor our EKS clusters. Warnings and errors are sent to our Slack channels. The above
InvalidDiskCapacity
is now "spamming" us for each scheduled pod on EKS Fargate.I'm wondering if we are the only one affected by this issue or if this is a temporary issue on EKS Fargate scheduler and whether or not AWS is going to handle this warning in the near future?
Which service(s) is this request for? EKS Fargate
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
I'm trying to avoid false positive alarms on EKS cluster with workload scheduled on Fargate.
Are you currently working around this issue? How are you currently solving this problem?
I have implemented a custom BotKube filter to ignore
invalid capacity 0 on image filesystem
Node event on Fargate.Here is the custom filter for those who want to have a look:
botkube/pkg/filterengine/filters/custom_node_event_checker.go
Additional context Anything else we should know?
We don't have this issue with Self-Managed EKS Nodes nor AWS Managed EKS nodes.
Thanks in advance for your time.