after enabling sharding, the application cannot be updated normally.

[zxbyoyoyo]

Describe the bug

To Reproduce

1. make a test application

cat <<EOF | kubectl apply -f -
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: app-normal
spec:
  components:
    - name: comp-normal
      type: webservice
      properties:
        image: nginx
  policies:
    - name: topology
      type: topology
      properties:
        clusters: ["local"]
EOF

2. switch on Controller sharding

vela install  -v 1.9.5 --set sharding.enabled=true
vela addon enable vela-core-shard-manager nShards=2

3. update the test application

cat <<EOF | kubectl apply -f -
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: app-normal
spec:
  components:
    - name: comp-normal
      type: webservice
      properties:
        image: nginx
  policies:
    - name: topology
      type: topology
      properties:
        clusters: ["local"]
EOF

What happens: when updating the application, the application mutating webhook will assign a random shard-id if it finds that the application does not have a shard-id. but it doesn't add the shard-id to the related apprev and rt resources. because of this, the slave controller will report that it can't find the apprevision resource when it is processing the application.

How to solve: we can try to adjust the application mutating webhook logic to make it also add a shard-id to the application, apprev, rt and other related resources. but in the test, we found that the master controller will get the apprev, rt data from the cache (at this point, there is no apprev, rt data in the cache. Once the sharding is activated, the master controller will only cache resources with the shard-id: master label).

Expected behavior

Screenshots

KubeVela Version
v 1.9.5

Cluster information

Additional context