@terlar the error you received appear to be that addons is not supported by the autopilot.

Take a look at the comparison for the autopilot, you might see what are supported. This behavior is dictated by the api. There is not we can do at the provider level.

Where did you see it should be as what you stated in Expected Behavior?

Thank you for the link. The addon is pre-configured, but can optionally be disabled:
https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver#disable

I guess it is the same thing as with mesh certificates (cannot be enabled during creation). Filestore CSI driver cannot be disabled during creation.

But it is possible to disable the addon either via GCloud CLI and the Google Cloud Console.

I saw this in the linked documentation as well as in the Google Cloud Console on my own autopilot clusters (screenshot posted earlier).

I can add the addon for backup during creation, so addons is not completely off limits:

addons_config {
  gke_backup_agent_config {
    enabled = true
  }
}

Yes, need to bring the behavior up to the same as other tools

But updates allow it

were you able to use TF to disable the addon on an existing cluster? On create time it's not possible to turn it off.

This is an intended behavior in AP cluster, gcp_filestore_csi_driver_config will always be enabled.

We only allow customers to turn it on or off for standard clusters.

As you can see from my screenshot and earlier message that is not true. I do have autopilot clusters and I can disable filestore CSI driver both via gcloud and Google Cloud Console after cluster creation.

Whether this ability is a bug or feature I leave up to you.

@leiyiz Yes, by using the gcloud module and have it depend on the cluster resource. It is not possible via the google_container_cluster resource as it explicitly don't allow it.

This is an intended behavior in AP cluster, gcp_filestore_csi_driver_config will always be enabled.

We only allow customers to turn it on or off for standard clusters.

@sunnylovestiramisu @leiyiz

It is allowed to create an Autopilot cluster directly through the API with gcpFilestoreCsiDriverConfig set to disabled.

{
  "projectId": "x",
  "cluster": {
    "addonsConfig": {
      "gcpFilestoreCsiDriverConfig": {
        "enabled": false
      }
    },
    "name": "fromapi",
    "autopilot": {
      "enabled": true
    }
  }
}

There is also google documentation confirming that you can disable it, although it is not recommended.

Allowing this configuration for Autopilot clusters would save time when creating new clusters, especially since it's permitted through the API:

    gcp_filestore_csi_driver_config {
      enabled = false
    }

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.