nodegroup has no accessible CSIStorageCapacity with enough capacity for PVC

[laxmanvallandas]

Which component are you using?:
CA (cluster-autoscaler)

What version of the component are you using?:
v1.22.11

k8s.gcr.io/autoscaling/cluster-autoscaler:v1.22.3

Component version:

What k8s version are you using (kubectl version)?:

v1.22.11

What environment is this in?:

AWS

What did you expect to happen?
Cluster autoscaler should scale the node from specified node group.

Ephemeral storage tag has been attached to the node group as suggested here: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#auto-discovery-setup

Can someone point what's missing in here?

I0816 06:00:54.705575       1 scheduler_binder.go:986] Node "template-node-for-1.generic-ephemeral-storage-scale-test.nodes.domain-name-9195797700036107435" has no accessible CSIStorageCapacity with enough capacity for PVC generic-ephemeral-storage-scale-test-testnamespace/generic-ephemeral-storage-scale-test-pod-scale-from-zero-0-generic-ephemeral-storage-scale-test-storage of size 1073741824 and storage class "topolvm-provisioner"
I0816 06:00:54.705592       1 scale_up.go:300] Pod generic-ephemeral-storage-scale-test-pod-scale-from-zero-0 can't be scheduled on 1.generic-ephemeral-storage-scale-test.nodes.domain-name, predicate checking error: node(s) did not have enough free storage; predicateName=VolumeBinding; reasons: node(s) did not have enough free storage; debugInfo=
I0816 06:00:54.705616       1 scale_up.go:449] No pod can fit to 1.generic-ephemeral-storage-scale-test.nodes.domain-name

[laxmanvallandas]

Seems like the issue is related to #3887. Wondering if there is any workaround for this until cluster autoscaler is stable to track and scale the nodes based on storage capacity on the nodes. Have verified this suggestion https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1472-storage-capacity-tracking/README.md#generic-autoscaler-support but itseems very flaky and also it doesnt seem to bring down the instances when the pods were deleted later. Any suggestions from the maintainers or may be someone able to get through the scaling of nodes based on storage capacity on the nodes?

We are using topolvm provisioner as storage class.

[k8s-triage-robot]

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

[Kavinraja-G]

@laxmanvallandas Did you had any progress on this issue later?

[Kavinraja-G]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@Kavinraja-G: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen
/remove-lifecycle rotten

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.