Tekton Kueue
The cluster-scoped TektonKueue custom resource installs and manages
Tekton Kueue. Using
TektonConfig is recommended.
Prerequisites
Install these APIs before enabling Tekton Kueue:
Configuration
Enable Tekton Kueue through TektonConfig:
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
name: config
spec:
kueue:
disabled: false
multi-cluster-disabled: true
multi-cluster-role: ""
config.yaml:
queueName: pipelines-queue
Alternatively, create the component resource directly:
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonKueue
metadata:
name: kueue
spec:
disabled: false
multi-cluster-disabled: true
multi-cluster-role: ""
config.yaml:
queueName: pipelines-queue
Multi-cluster configuration
A multi-cluster installation can configure the cluster as a Hub or Spoke.
Hub:
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonKueue
metadata:
name: kueue
spec:
disabled: false
multi-cluster-disabled: false
multi-cluster-role: Hub
config.yaml:
queueName: pipelines-queue
When the Hub role is configured through TektonConfig, the operator also
manages the Syncer Service and
Tekton Multicluster Proxy AAE.
Spoke:
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonKueue
metadata:
name: kueue
spec:
disabled: false
multi-cluster-disabled: false
multi-cluster-role: Spoke
config.yaml:
queueName: pipelines-queue
Upgrade compatibility
TektonKueue replaces the former TektonScheduler API. The deprecated
TektonScheduler CRD and TektonConfig.spec.scheduler field remain available
during the compatibility window.
During pre-upgrade reconciliation, the operator:
- Copies
TektonConfig.spec.schedulertoTektonConfig.spec.kueueand clears the deprecated field. If both fields are configured,spec.kueuewins. - Removes InstallerSets owned by the old component.
- Removes the deprecated
tekton-scheduler-roleandtekton-scheduler-rolebindingresources. - Creates
TektonKueue/kueuefrom an existingTektonScheduler/schedulerresource when aTektonKueueresource does not already exist. - Removes the old operator finalizer, preserves other finalizers, and requests deletion of the migrated legacy resource.
The deprecated API is retained only for migration and does not reconcile
operand resources. Use TektonKueue and spec.kueue for new configuration.
Rename IMAGE_SCHEDULER_MANAGER and IMAGE_SCHEDULER_WEBHOOK overrides to
IMAGE_KUEUE_MANAGER and IMAGE_KUEUE_WEBHOOK.
Feedback
Was this page helpful?