Alauda DevOps Pipelines Docs
  • English

    • Configuring Resource Quotas for Trigger Components

    TOC

    OverviewUse CasesPrerequisitesResource Configuration GuidelinesStepsOperation ResultReferences

    Overview

    Configure resource quotas related to the Trigger component.

    Use Cases

    • Adjust the resource quotas for Trigger control plane components
    • Tune replica count and CPU/memory settings for Trigger Deployments based on cluster load

    Prerequisites

    Resource Configuration Guidelines

    Before configuring resource quotas:

    • Assess your cluster's available resources and capacity
    • Consider your webhook traffic pattern and peak event load
    • Start with conservative values and adjust based on monitoring data
    • Test configurations in non-production environments first

    Steps

    Step 1

    Edit the TektonConfig resource.

    $ kubectl edit tektonconfigs.operator.tekton.dev config

    Step 2

    WARNING

    Modifying the configuration may trigger a rolling update of the component Pods, which could lead to temporary service unavailability. Please execute this at an appropriate time.

    Example of modifying the spec.trigger.options.deployments configuration:

    apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
  name: config
spec:
  trigger:
    options:
      disabled: false
      deployments:
        tekton-triggers-controller:
          spec:
            replicas: <REPLICA_COUNT>  # e.g., 1
            template:
              spec:
                containers:
                  - name: tekton-triggers-controller
                    resources:
                      requests:
                        cpu: <CPU_REQUEST>        # e.g., "200m"
                        memory: <MEMORY_REQUEST>  # e.g., "256Mi"
                      limits:
                        cpu: <CPU_LIMIT>          # e.g., "500m"
                        memory: <MEMORY_LIMIT>    # e.g., "512Mi"

        tekton-triggers-core-interceptors:
          spec:
            replicas: <REPLICA_COUNT>  # e.g., 1
            template:
              spec:
                containers:
                  - name: tekton-triggers-core-interceptors
                    resources:
                      requests:
                        cpu: <CPU_REQUEST>        # e.g., "200m"
                        memory: <MEMORY_REQUEST>  # e.g., "256Mi"
                      limits:
                        cpu: <CPU_LIMIT>          # e.g., "500m"
                        memory: <MEMORY_LIMIT>    # e.g., "512Mi"

        tekton-triggers-webhook:
          spec:
            replicas: <REPLICA_COUNT>  # e.g., 1
            template:
              spec:
                containers:
                  - name: webhook
                    resources:
                      requests:
                        cpu: <CPU_REQUEST>        # e.g., "200m"
                        memory: <MEMORY_REQUEST>  # e.g., "256Mi"
                      limits:
                        cpu: <CPU_LIMIT>          # e.g., "500m"
                        memory: <MEMORY_LIMIT>    # e.g., "512Mi"

    Step 3

    Submit the configuration and wait for the Pods to update.

    $ kubectl get pods -n tekton-pipelines -w

NAME                                                READY   STATUS    RESTARTS   AGE
tekton-triggers-controller-67f69dbb5d-zk5x2         1/1     Running   0          2m16s
tekton-triggers-core-interceptors-d6495f95f-vk49r   1/1     Running   0          2m16s
tekton-triggers-webhook-55758bbcd9-2qvzs            1/1     Running   0          2m16s

    Operation Result

    You can see that the resource quota configurations for Trigger related components are effective.

    $ kubectl get deployments.apps -n tekton-pipelines tekton-triggers-controller tekton-triggers-core-interceptors tekton-triggers-webhook -o yaml | grep 'resources:' -A 6

          resources:
            limits:
              cpu: 500m
              memory: 512Mi
            requests:
              cpu: 200m
              memory: 256Mi
--
          resources:
            limits:
              cpu: 500m
              memory: 512Mi
            requests:
              cpu: 200m
              memory: 256Mi
--
          resources:
            limits:
              cpu: 500m
              memory: 512Mi
            requests:
              cpu: 200m
              memory: 256Mi

    References