Conversation
ifdotpy
marked this pull request as draft
September 11, 2026 07:06
ifdotpy
marked this pull request as ready for review
September 22, 2026 16:27
Two additions to the kcp-aware Service Provider Runtime ADR: 1. Provisioning: the Provisionable configuration can carry optional labels and annotations for the generated APIExport, stamped by the runtime at provisioning time. Gives embedding platforms a declarative source for their marker labels (e.g. Platform Mesh's ui.platform-mesh.io/content-for) with the runtime as the single writer. Verified live: an externally added label on a provider APIExport is stripped within a minute today, so platforms re-apply theirs in a loop. 2. Open question 4 (singleton): proposed resolution keeps the existing name convention as the rule - a service object binds to the same-named ControlPlane, so per-target uniqueness comes free from name uniqueness, with no API change and no enforcement code. Hard requirement: no matching ControlPlane means a visible Progressing condition, never silent ignoring. An explicit targetRef (defaulting to metadata.name) remains a compatible later extension. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LTnkmXa3XLTxGMmfZayFV2 Signed-off-by: Igor Fominykh <ihor.fominykh@sap.com>
ifdotpy
force-pushed
the
feat/adr-kcp-runtime-export-metadata
branch
from
September 22, 2026 18:16
cda0ef2 to
cb247e6
Compare
Signed-off-by: Igor Fominykh <ihor.fominykh@sap.com>
ifdotpy
changed the title
Signed-off-by: Igor Fominykh <ihor.fominykh@sap.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ADR now separates the proposed APIExport discovery path from the deployed Secret-backed shared onboarding path. The deployment selects the manager when it starts. ProviderConfig does not select the mode.
For the APIExport path, the platform owns the APIResourceSchema and APIExport. The shared Flux and External Secrets providers instead watch account kubeconfig Secrets. Both paths use the common ClusterContext and access deletion step.
Validation:
npm run buildpassed. Docusaurus reported an existing broken anchor in/users/concepts/providers.