Skip to content

installer: the Filestore CSI step fails on v1.0.0-rc.1 (overlay targets ate.dev/v1alpha1) and leaves IAM and a half-applied namespace behind #114

Closed

Description

@aditya-shantanu

From an end-to-end run of the installer against v1.0.0-rc.1. Checklist item "Filestore CSI step" in #94.

Symptom. The optional "Install Filestore CSI driver" step clones kubernetes-sigs/gcp-filestore-csi-driver at HEAD and runs deploy/kubernetes/overlays/substrate/deploy.sh --project-id <p>. It fails at "Apply Kustomize overlay":

error: resource mapping not found for name: "filestore.csi.storage.gke.io" namespace: "gcp-filestore-csi-driver" … no matches for kind "CSIDriverConfig" in version "ate.dev/v1alpha1"

Root cause. The overlay's csi_driver_config.yaml is still written against ate.dev/v1alpha1 (unchanged through its latest commit, a07c36a, 2026-10-28). agent-substrate/substrate#2996 moved every CRD to ate.dev/v1, and the csidriverconfigs.ate.dev CRD at v1.0.0-rc.1 serves v1 only. The overlay fix belongs upstream: kubernetes-sigs/gcp-filestore-csi-driver#1416.

What it leaves behind. deploy.sh grants roles/file.editor to substrate-filestore-csi@<project> at project scope and binds Workload Identity before the apply, and the installer turns off GKE's managed Filestore addon before running it. After the failure the cluster keeps namespace gcp-filestore-csi-driver with a running controller and node pods in CrashLoop (2/3) and no CSIDriverConfig; the IAM grant stays. The wizard's [s] moved on and the completion and exit summaries said "filestore skipped". The README still advertises the step.

Fix in this repo.

  • Clone and read the overlay first, then check kubectl get crd csidriverconfigs.ate.dev serves the apiVersion the overlay's CSIDriverConfig uses, and fail the step with a clear message before the managed addon is disabled and before deploy.sh touches IAM.
  • Keep the clone at HEAD (no revision of the overlay serves v1 yet; the check reads whichever apiVersion the clone has, so the step starts working when upstream moves it).
  • Record a failed-then-skipped step (FilestoreCSIFailed) so the completion panel and exit summary say "failed", not "skipped".
  • Checklist rows in the new order; README row says what the step checks and that it fails on this pin until #1416 lands.

Activity

  1. added a commit that references this issue on Nov 5, 2026
    96b0350
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions