can't deploy trident csi daemon set pods on GKE worker nodes

[liuningty]

Describe the bug

when deploying Trident on Google GKE environment, use both Helm and manual process to deploy trident with no custom flags.
Trident operator and csi controller can be provisioned successfully, but csi daemon set pods are not being spun up on any GKE worker node that needs to mount a volume.
I am able to create persistent volumes, but not able to mount them into the pods.
when check pod description, it shows the below error:
CSINode does not contain driver csi.trident.netapp.io

Environment
Provide accurate information about the environment to help us reproduce the issue.

• Trident version: 22.04
• Kubernetes version: 1.22.8 gke
• NetApp backend types: CVS for GCP

[jwebster7]

Hi @liuningty, thank you for reporting this. This is a known issue and a fix for this will be included in our 22.07 release.

Until 22.07 is released, one workaround is to manually create a Resource Quota in the same namespace Trident is installed in. This should allow the Trident DaemonSet to consume the system-node-critical Priority Class.

Here's an example Resource Quota for you to use:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: trident-csi
  namespace: trident # or your namespace
  labels:
    app: node.csi.trident.netapp.io
spec:
  scopeSelector:
     matchExpressions:
       - operator : In
         scopeName: PriorityClass
         values: ["system-node-critical"]

[liuningty]

Thanks @jwebster7, after I installed Resource Quota you provided, the trident CSI is working okay now. thanks for your quick response.

[jwebster7]

Happy to help @liuningty! Please continue to let us know if you find anything else or have any questions at all.

[gnarl]

This issue is fixed with commit d9715f8 and will be included in the Trident 22.07 release.