Story (Required)

The Hub Resolver currently supports only a single Artifact Hub URL and single Tekton Hub URL, configured via environment variables. This limitation prevents organizations from using resources distributed across multiple hub instances.

Current Limitations

  - Only one Artifact Hub URL can be configured cluster-wide
  - Only one Tekton Hub URL can be configured cluster-wide
  - Organizations cannot leverage independently-managed hub instances without operational complexity
  - Current workarounds require either:
    - Deploying multiple resolver instances (operationally complex)
    - Consolidating all resources into one hub (eliminates distributed ownership benefits)

Proposed Solutions

  Option A: Add per-resolution url parameter to hub resolver
  - Pipeline authors can explicitly specify which hub to query
  - Falls back to cluster defaults when parameter not provided

  Option B: Configure multiple hub URLs at cluster level
  - Implement fallback query behavior across configured hubs

  Option C: Combine both approaches
  - Maximum flexibility for different use cases

Background (Required)

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met