bug: default workspace type creates too many objects in etcd on startup

[stevekuznetsov]

Describe the bug

Today, when a user creates a new workspace, they get a universal one, and that brings with it nine keys in etcd:

• /registry/apis.kcp.dev/apibindings/customresources/root:users:zu:yc:kcp-admin/apiresource.kcp.dev-cg5rx
• /registry/apis.kcp.dev/apibindings/customresources/root:users:zu:yc:kcp-admin/scheduling.kcp.dev-7uhq2
• /registry/apis.kcp.dev/apibindings/customresources/root:users:zu:yc:kcp-admin/tenancy.kcp.dev-asxvy
• /registry/apis.kcp.dev/apibindings/customresources/root:users:zu:yc:kcp-admin/workload.kcp.dev-87hht
• /registry/core/configmaps/root:users:zu:yc:kcp-admin/default/kube-root-ca.crt
• /registry/core/namespaces/root:users:zu:yc:kcp-admin/default
• /registry/core/secrets/root:users:zu:yc:kcp-admin/default/default-token-lgglq
• /registry/core/serviceaccounts/root:users:zu:yc:kcp-admin/default/default
• /registry/rbac.authorization.k8s.io/clusterrolebindings/root:users:zu:yc/system:kcp:tenancy:home-owner:kcp

As a straw-man, thinking about what a service provider like Cert-Manager would need in order to be successful in their service provider workspace, it might be a set of API resource schemas and API exports. This type of workspace needs no bindings, needs no default namespace, etc.

We likely want the most bare-bones default here to suffice for the above case, and it can seemingly do so without any of those objects. Other types of workspaces can opt into those sorts of things as they see fit.

Steps To Reproduce

kubectl kcp ws create

Expected Behaviour

Something more minimal.

Additional Context

No response

[stevekuznetsov]

cc @MikeSpreitzer @sttts @ncdc

[kcp-ci-bot]

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kcp-ci-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kcp-ci-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kcp-ci-bot]

@kcp-ci-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.