[EKS] [EFS CSI driver add-on]: vol-metrics-opt-in flag not working
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
The [aws-efs-csi-driver](https://github.com/kubernetes-sigs/aws-efs-csi-driver?tab=readme-ov-file#container-arguments-for-efs-plugin-of-efs-csi-node-daemonset) provides a container argument --vol-metrics-opt-in to enable metrics for EFS volumes.
As of 2.1.8-eksbuild.1, the `node.volMetricsOptIn` parameter cannot be used.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
While trying to apply the following configuration:
```
{"node": {"volMetricsOptIn": true}}
```
I get the error:
```InvalidParameterException: ConfigurationValue provided in request is not supported: Json schema validation failed with error: [$.node.volMetricsOptIn: is not defined in the schema and the schema does not allow additional properties]```
**Are you currently working around this issue?**
No
**Additional context**
**Attachments**
Contributor guide
Research direction
Start with the EKS add-on configuration schema and the aws-efs-csi-driver container-arguments documentation linked in the issue. Reproduce the JSON schema validation error using node.volMetricsOptIn, then determine whether the parameter is accepted by the add-on configuration. Done means the configuration validates and enables EFS volume metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100