Repository navigation
[1- De-Rooting] Add APIIdentity - #4488
Conversation
|
@mjudeikis-bot review this. |
|
@mjudeikis-bot review this. |
mjudeikis-bot
left a comment
There was a problem hiding this comment.
No issues found. Checked: the registry controller's owner-missing/succession/holder-drop logic, the APIExport claim and holder path in reconcileIdentity, the admin authorizer verb and group restrictions, and the unit tests for those packages (all pass).
|
/retest |
|
/retest |
|
So this as structural problem due to kcp-dev/enhancements#19 |
|
@mjudeikis-bot review? |
|
flake #4473 |
|
/retest |
| provider := &adminAPIDefinitionSetProvider{ | ||
| config: mainConfig, | ||
| cacheDynamicClusterClient: cacheDynamicClusterClient, | ||
| identities: identities, |
There was a problem hiding this comment.
That makes me think - should the admin VW only report readiness once the relevant informers have synced?
Otherwise e.g. APIIdentty(<my-hash>) returns nothing during boot even though there may be APIExports with <my-hash>, the VW just doesn't report them yet since the informer hasn't synced. And IIRC most informers are started as part of the post start hook.
|
/retest |
|
LGTM label has been added. DetailsGit tree hash: f8ef5e48d614916b69f60884ff35bdb31f629d11 |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ntnn, xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
This adds admin api for apiidentity tracking. This will allow centralized cache-server based apiexport indetity tracking.
We need this so we can decouple root shard from being Single point of failure.
For now no user facing changes so we should be able to be more lean how we approach this
What Type of PR Is This?
/kind feature
Related Issue(s)
Fixes #
Release Notes