TEP-0192: Direct Remote Resource Resolution - #1296
Draft
waveywaves wants to merge 4 commits into
Draft
Conversation
Assisted-by: OpenAI Codex via Pi
tekton-robot
added
do-not-merge/work-in-progress
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
tekton-robot
added
the
size/XXL
Assisted-by: OpenAI Codex via Pi
tekton-robot
added
size/L
Assisted-by: OpenAI Codex via Pi
tekton-robot
added
size/XL
Assisted-by: OpenAI Codex via Pi
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
2 participants
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.
Summary
Proposes an optional direct remote-resolution path that reuses the existing resolver Deployment, Service, and process while avoiding per-resolution Kubernetes object churn.
The design adds a bounded asynchronous requester and a versioned internal HTTPS endpoint, preserves existing Task and Pipeline APIs, and retains the CRD path during migration. Direct mode remains gated on measurements, tenant-safe caching, and durable timeout semantics.
/kind tep