Configure Tekton Integration
Feature Overview
artifacthub-shim serves Tekton catalog resources through Artifact
Hub-compatible APIs. Tekton hub resolver and Pipelines as Code should use the
in-cluster shim Service, not public artifacthub.io or api.hub.tekton.dev.
Artifact Hub Shim v1.0.0 currently works out of the box with the released
Alauda Container Platform Pipelines v4.14.0. The minimum versions for the 4.10,
4.6, and 4.0 lines are v4.10.2, v4.6.4, and v4.0.17 after those
patches are released. Standard installations with Alauda Container Platform
Pipelines 4.14 use these
defaults:
Tekton Hub Resolver
When the plugin uses the standard namespace and release name, Alauda Container
Platform Pipelines 4.14 sets the resolver defaults during component
installation. The same Service URL
applies after the minimum tektoncd-operator patch versions on the 4.10,
4.6, and 4.0 lines are released. For custom installations, merge this
configuration into TektonConfig.spec.pipeline:
default-tekton-hub-catalog must stay present even when default-type is
artifact; current resolver versions still read it while preparing defaults.
If artifacthub-shim is installed into another namespace, replace
artifacthub-shim-system in artifact-hub-api with the install namespace.
If the Helm release name changes and the Service name is overridden, update the
Service host as well.
Pipelines as Code
PAC remote annotations use PAC settings, not TektonConfig resolver settings.
For custom installations, set these PAC settings on the
OpenShiftPipelinesAsCode resource or the reconciled PAC configuration source:
Do not append /api/v1 to hub-url; PAC adds it for Artifact Hub providers.
Keep hub-catalog-type: artifacthub so PAC does not probe /api/v1/stats and
fall back to Tekton Hub behavior.
PAC has one default hub-catalog-name. It therefore asks shim for remote
Pipeline annotations from catalog; shim falls back to catalog-pipelines for
Pipeline detail lookups. New explicit hub resolver references should still use
catalog-pipelines for Pipelines.
DevOps Hub UI
The DevOps UI keeps the stable /hub gateway path. The chart renders a
dedicated hubIngress that rewrites /hub(/|$)(.*) to the canonical shim API.
The shim API itself does not register /hub/** handlers.
Related Content
Tekton™ is a trademark of The Linux Foundation.
Red Hat® and OpenShift® are registered trademarks of Red Hat, Inc. in the United States and other countries.
Alauda is an independent vendor. This product is not affiliated with, endorsed by, or sponsored by The Linux Foundation or Red Hat, Inc. All trademarks are the property of their respective owners and are used here for identification purposes only.