Add ability to change kubelet default path

[Amos-85]

There is no option in the helm chart values file to define the kubelet mountPath

it would be nice if we can define it if some cluster has some kubelet path other then the default one which is /var/lib/kubelet

[leakingtapan]

Hey @Amos-85 thx for reporting the issue. Could you add more details on why "some cluster has some kubelet path other then the default one"?

[Amos-85]

Hi @leakingtapan
Case 1

• RKE use this path /opt/rke/var/lib/kubelet as default.

Case 2

• Sometimes you don't want to deploy k8s components under root paths cause of small root fs.

[leakingtapan]

It is possible now if you update the path yourself here: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/deploy/kubernetes/base/node.yaml#L38 if this is the path being concerned?

[Amos-85]

@leakingtapan, the file you mentioned refer to kustimize, not for the helm chart.

the /var/lib/kubelet is not template in the helm chart:
as-daemonset-reference

[leakingtapan]

Yep. the above is a workaround while the path is not configurable. You could either manually edit the helm or kustomize file.

But free feel to submit a PR to make helm configubale, I will review the change

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[leakingtapan]

/reopen

[k8s-ci-robot]

@leakingtapan: Reopened this issue.

In response to this:

/reopen

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.

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.

[wongma7]

/reopen
/help-wanted
/lifecycle frozen

more configuration options welcome.

[k8s-ci-robot]

@wongma7: Reopened this issue.

In response to this:

/reopen
/help-wanted
/lifecycle frozen

more configuration options welcome.

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.