Skip to content

DeadlineExceeded Error (failed to fetch secret) #1901

@DrazThan

Description

@DrazThan

TL;DR
Every few days the provider is unable to retrieve secrets from the Secret Manager

Expected behavior
Expecting secrets to be retrieved throughout

Observed behavior
Secrets are not retrieved and logs fill with DeadLine Exceeded error, only fixed by restarting the provider daemonset IE
kubectl -n kube-system rollout restart daemonset csi-secrets-store-provider-gcp

Reproduction
Normal operation, every few days I see new containers are stuck on containercreating status with this under the pod events -
{"ts":1754931810198.8691,"caller":"server/server.go:170","msg":"failed to fetch secret","resource_name":"projects/X/secrets/X/versions/latest","err":"rpc error: code = DeadlineExceeded desc = context deadline exceeded while waiting for connections to become ready"}

Environment
GKE Cluster using both provider and CSI driver installed via helm
I tried increasing the resources in helm for both

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions