#4150·vcluster

Pod status desynchronisation between vCluster and host

Author: JCL38-ORANGECreated Aug 21, 2026Updated Aug 21, 2026
Labelskind/bug

What happened?

We face with a pod status desynchronisation between vCluster and host :

  • pod is in a running state in a host cluster
  • pod remains pending in the vcluster

What did you expect to happen?

I expect to have the same pod status between host cluster and vcluster

How can we reproduce it (as minimally and precisely as possible)?

TBC

Anything else we need to know?

We have the following message in the vcluster logs : vcluster-696b59b865-m59xs syncer 2026-08-21 15:43:28 ERROR controller/controller.go:494 Reconciler error {"component": "vcluster", "controller": "pod", "namespace": "01-coa-replacement-sync-k8s-gitops-repo", "nam e": "k8s-wip-generator-84778c9bd4-2vskg", "reconcileID": "29dc9db6-8c04-4551-87d3-4c41ca0a272d", "error": "sync: patch virtual object: update object: Pod "k8s-wip-generator-84778c9bd4-2vskg" is invalid: spec: Forbidden: po d updates may not change fields other than spec.containers[*].image,spec.initContainers[*].image,spec.activeDeadlineSeconds,spec.tolerations (only additions to existing tolerations),`spec.terminationGracePeriodSecond

Host cluster Kubernetes version

v1.35.6-gke.1641000 (GKE Autopilot)

vcluster version

v0.36.1 - v1.35

VCluster Config

```yaml
sync:
  fromHost:
    ingressClasses:
      enabled: true
    nodes:
      enabled: true
    storageClasses:
      enabled: true
  toHost:
    ingresses:
      enabled: true
    pods:
      enabled: true
      
    networkPolicies:
      enabled: false           

    podDisruptionBudgets:
      enabled: true
    
    persistentVolumes:
      enabled: true          
</details>