StatefullSet error in GCP Kubernetes manifest

## Description

on GKE im getting " Multi-Attach error for volume"
Solution: use node affinity so that statefulset and deployment land on same node.

we need to review the manifest to avoid these errors.

Locate the GCP Kubernetes manifest referenced by the issue and inspect how the StatefulSet and deployment are scheduled. Reproduce or review the Multi-Attach error context, then verify that the manifest's node-affinity configuration keeps both workloads on the same node and avoids the volume error.

Written by the indexing model from the issue text.