Feature Description

My syncagents did not come up with this error message

{"level":"info","time":"2025-10-20T12:57:39.456Z","caller":"api-syncagent/main.go:101","msg":"Moin, I'm the kcp Sync Agent","version":"v0.3.0","name":"myservice-syncagent","apiexport":"myapiexport"} {"level":"fatal","time":"2025-10-20T12:57:39.458Z","caller":"api-syncagent/main.go:91","msg":"Sync Agent has encountered an error","error":"kcp kubeconfig does not point to a specific workspace"}

My kubeconfig (properly saved as secret and bound in the syncagent) looked like this

`apiVersion: v1
clusters:

• cluster:
  certificate-authority-data: cert...
  server: https://internal.platform.hubert.pe.poc3.cloud-native.training:8443/clusters/root:provider
  name: kcp-provider
  contexts:
• context:
  cluster: kcp-provider
  user: kcp-provider
  name: kcp-provider
  current-context: ""
  kind: Config
  preferences: {}
  users:
• name: kcp-provider
  user:
  token: token...
  `

So, my mistake was not providing the current-context. The error message kcp kubeconfig does not point to a specific workspace sent me into the wrong direction.

Proposed Solution

Please provide a proper error message.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response