isindir / eks-ebs-node-operator Goto Github PK

Container resource name validation is still failing after #16.

# * spec.containers[0].resources.limits[eksattachments]: Invalid value: "eksattachments": must be a standard resource type or fully qualified
# * spec.containers[0].resources.limits[eksattachments]: Invalid value: "eksattachments": must be a standard resource for containers
# * spec.containers[0].resources.requests[eksattachments]: Invalid value: "eksattachments": must be a standard resource type or fully qualified
# * spec.containers[0].resources.requests[eksattachments]: Invalid value: "eksattachments": must be a standard resource for containers

It appears that any extended resource should follow the fully qualified resource name scheme (e.g. eks.ebsnodeoperator/attachments):
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#extended-resources

Just found this operator while researching the node volume limit issue in the EBS CSI, but not quite sure how to use it.

As I understand it sets the eks/attachments/EBS resource limit on each node based of its instance type. I can observe this after installing the operator into the cluster. However, I'm not sure how to make use of this limit now?

Would be great to have an example in the readme.