Skip to content

feature: Identity resolution without root shard #4347

Description

@mjudeikis

Feature Description

The root kubeconfig is still
required for APIExport identity resolution and will be removed once
identities are resolvable without the root shard.

We need way to remove need for "root" shard to be there to resolve identities, so we can remove need for root shard :)

Proposed Solution

Do it :)

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

This will depend on decouple shards first

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Sep 1, 2026
  2. mjudeikis commented on Sep 3, 2026

    @mjudeikis
    ContributorAuthor

    This is harder than it looks.
    Identities are now established ONLY by root shard in the root workspace.
    Most ideal option for this is to use Certificate and "seed" the identies from it.
    But it does not have an upgrade path for existing installs.
    So for this to decouple we need to do this https://github.com/kcp-dev/enhancements/blob/c62b9141c1b49df82b0be1d519ec74a11a3a7996/keps/core/0005-apiexport-identity-rotation.md
    and once we have migration, we would migrate existing identities, to seed file ones during kcp upgrade.

  3. self-assigned this
    on Sep 22, 2026
  4. added this to the v0.35 milestone on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Projects

  • Status
    In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions