aws-efs-csi-driver
aws-efs-csi-driver copied to clipboard
Adding ability to set volMetricsOptIn on Daemonset
Is this a bug fix or adding new feature? This is a bug-fix in response to #698.
What is this PR about? / Why do we need it?
It seems as though volMetricsOptIn
is set for the controller container when the code that uses the flag isn't executed in that context. I've added the flag to the daemonset as well in the first instance because I'm not 100% sure that the flag is never used in the context of the controller. If that is the case I'm happy to also delete those settings in a separate commit.
What testing is done? As this is a helm change that is very simple, and replicates code that already exists in the codebase, this is untested other than the automated tests that run as part of the PR. However if there are further tests you would like performing I'm happy to do so.
fixes #698
Hi @jonathanrainer. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Hey, this change looks simple enough. Can it be reviewed?
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jonathanrainer
Once this PR has been reviewed and has the lgtm label, please assign justinsb for approval by writing /assign @justinsb
in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/ok-to-test
@makomatic: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
In response to this:
/ok-to-test
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Works as expected if I use it in our QA cluster with --vol-metrics-opt-in=true
as arg for the daemonset binary.
kubelet_volume_stats_available_bytes is set to EFS max capacity, of course (8388607Ti), but kubelet_volume_stats_used_bytes seems to be valid.
Hi @mskanth972 can we have an ok-to-test
on this one?
Any update on this one? What is still blocking?
/ok-to-test
@jonathanrainer, thanks for the PR. Can you remove that parameter in controller helm chart in a separate commit?
@mskanth972 That's now done, do I need to re-generate the Kustomize as well?
@jonathanrainer not necessary I believe but if you can that would be great.
@mskanth972 That's now fixed too, I also realised there was an inconsistency between the helm chart and the kustomize so that's now fixed up as well.
Thanks @jonathanrainer, will merge it and mark in the next release.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jonathanrainer, mskanth972
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [mskanth972]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment