how to syncer all k8s core resource to workspace root:xxxx. in latest version

[tangshibokmpler]

I installed it using Helm with version v0.28.0 on my Mac kind cluster. There is no information about this in the latest documentation. I tried using PublishedResource to sync all Kubernetes core resources, and it works, but the subresource status cannot sync. The error is:

failed to synchronize object state: failed to update source object status: pods.wk.test.com "hello-pod" not found

Should I use PublishedResource to sync all Kubernetes core resources?

My PublishedResource is：

apiVersion: syncagent.kcp.io/v1alpha1
kind: PublishedResource
metadata:
  name: publish-pods
spec:
  resource:
    apiGroup: ""  
    kind: Pod
    versions: ["v1"]

  projection:
    group: "wk.test.com" 

[embik]

Hi @tangshibokmpler, thanks for reporting your problem. This sounds like an api-syncagent problem, so I have transferred the issue to that repository.

[tangshibokmpler]

Hi @tangshibokmpler, thanks for reporting your problem. This sounds like an api-syncagent problem, so I have transferred the issue to that repository.

Will kcp support using PublishedResource to sync Pod、Deployment and other core resources upstream to workspaces in the future?

Is this mechanism used in version 0.28.0?

[embik]

Will kcp support using PublishedResource to sync Pod、Deployment and other core resources upstream to workspaces in the future?

We did not intend to exclude them from PublishedResources, which likely means we have a bug here, and yes, we do intent to fix such a bug.

Is this mechanism used in version 0.28.0?

This question isn't clear to me. But api-syncagent is separate from core kcp versions, so PublishedResources aren't part of kcp releases. With that being said, you likely want to use kcp 0.28.1 (freshly released), because 0.28.0 had a few issues. Perhaps this issue was triggered by it. We would have to investigate.

[tangshibokmpler]

Will kcp support using PublishedResource to sync Pod、Deployment and other core resources upstream to workspaces in the future?

We did not intend to exclude them from PublishedResources, which likely means we have a bug here, and yes, we do intent to fix such a bug.

Is this mechanism used in version 0.28.0?

This question isn't clear to me. But api-syncagent is separate from core kcp versions, so PublishedResources aren't part of kcp releases. With that being said, you likely want to use kcp 0.28.1 (freshly released), because 0.28.0 had a few issues. Perhaps this issue was triggered by it. We would have to investigate.

Thank you very much! May I ask when the Helm chart for version 0.28.1 will be available? I see that the Helm chart is still at version 0.28.0.

$ helm search repo kcp/kcp                                                                                                shibotang@ShibodeMacBook-Pro
NAME            	CHART VERSION	APP VERSION	DESCRIPTION
kcp/kcp         	0.12.2       	0.28.0     	A prototype of a multi-tenant Kubernetes contro...
kcp/kcp-operator	0.1.1        	v0.1.0     	A Helm chart for kcp-operator, a Kubernetes ope...

[embik]

The new chart version was published about 4 hours ago, so it's probably just a matter of a helm repo update.

[xrstf]

How did you manage to create the Pod APIResourceSchema? At least the current syncagent with kcp 0.28 reports issues:

2025-12-03T17:59:06.144+0100 error controller/controller.go:300 Reconciler error {"controller": "syncagent-apiresourceschema", "controllerGroup": "syncagent.kcp.io", "controllerKind": "PublishedResource", "PublishedResource": {"name":"publish-pods"}, "namespace": "", "name": "publish-pods", "reconcileID": "30600502-1334-400e-acf1-ed2e41c3f9ef", "error": "failed to create APIResourceSchema: apiresourceschemas.apis.kcp.io "vd70ad34d.pods.kcp.example.com" is forbidden: [spec.versions[0].schema.openAPIV3Schema.properties[status].properties[hostIPs].x-kubernetes-list-type: Invalid value: "atomic": must be map if x-kubernetes-list-map-keys is non-empty]"}

... when I try your PublishedResource in a quick e2e test (i.e. kcp<->envtest).