Quarkus Tekton

Describe what the extension does here.

Installation

If you want to use this extension, you need to add the io.quarkiverse.quarkus:quarkus-tekton extension first to your build file.

For instance, with Maven, add the following dependency to your POM file:

<dependency>
    <groupId>io.quarkiverse.quarkus</groupId>
    <artifactId>quarkus-tekton</artifactId>
    <version>0.0.3</version>
</dependency>

Extension Configuration Reference

Remove this section if you don’t have Quarkus configuration properties in your extension.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property

Type

Default

quarkus.tekton.pipelinerun.enabled

Whether to enable the tekton generation at build time of the PipelineRun.

Environment variable: QUARKUS_TEKTON_PIPELINERUN_ENABLED

boolean

true

quarkus.tekton.pipelinerun.params."params"

User’s arguments to customize the pipeline

Environment variable: QUARKUS_TEKTON_PIPELINERUN_PARAMS__PARAMS_

Map<String,String>

quarkus.tekton.pipelinerun.registry-auth-secret

Name of the Secret, expected to exist on the cluster, containing the registry auth file (config.json) which is bound to the dockerconfig-secret workspace of the PipelineRun.

Environment variable: QUARKUS_TEKTON_PIPELINERUN_REGISTRY_AUTH_SECRET

string

dockerconfig-secret

quarkus.tekton.generation.enabled

Whether to enable tekton generation at build time.

Environment variable: QUARKUS_TEKTON_GENERATION_ENABLED

boolean

true

quarkus.tekton.devservices.enabled

Enable the Tekton DevService.

Environment variable: QUARKUS_TEKTON_DEVSERVICES_ENABLED

boolean

true

quarkus.tekton.devservices.debug-enabled

Enable the debugging level.

Environment variable: QUARKUS_TEKTON_DEVSERVICES_DEBUG_ENABLED

boolean

false

quarkus.tekton.devservices.show-logs

If logs should be shown from the Tekton container.

Environment variable: QUARKUS_TEKTON_DEVSERVICES_SHOW_LOGS

boolean

false

quarkus.tekton.devservices.version

The version of Tekton to be installed from the GitHub repository and which corresponds to a tagged release expressed as such: "v0.68.0"

Environment variable: QUARKUS_TEKTON_DEVSERVICES_VERSION

string

v0.68.0

quarkus.tekton.devservices.controller-namespace

The Tekton controller namespace where Tekton stuffs are deployed The default namespace is: tekton-pipelines

Environment variable: QUARKUS_TEKTON_DEVSERVICES_CONTROLLER_NAMESPACE

string

tekton-pipelines

quarkus.tekton.devservices.time-out

Time to wait till a resource is ready: pod, etc The default value is: 180 seconds

Environment variable: QUARKUS_TEKTON_DEVSERVICES_TIME_OUT

long

360

quarkus.tekton.devservices.cluster-type

The cluster type to be used: kind or k3 The default value is: kind

Environment variable: QUARKUS_TEKTON_DEVSERVICES_CLUSTER_TYPE

string

kind

quarkus.tekton.devservices.host-name

The hostname of the tekton ingress route

Environment variable: QUARKUS_TEKTON_DEVSERVICES_HOST_NAME

string

tekton.localtest.me

quarkus.tekton.devservices.host-port

The host port to be used on the host machine to access the dashboard

Environment variable: QUARKUS_TEKTON_DEVSERVICES_HOST_PORT

string

9097

quarkus.tekton.devservices.ingress.version

The version of the Ingress controller to be installed from the GitHub repository If not specified, it will use the resources published on main branch The version to be used should be specified using the tagged release: v1.12.0, etc

Environment variable: QUARKUS_TEKTON_DEVSERVICES_INGRESS_VERSION

string

latest

quarkus.tekton.devservices.ingress.port-forward-enabled

Enable to forward the ingress traffic from the container to the local host

Environment variable: QUARKUS_TEKTON_DEVSERVICES_INGRESS_PORT_FORWARD_ENABLED

boolean

true