pipeline installation

Installation

Kubernetes runtime configuration

Kbuild

The KernelCI pipeline uses the Kbuild module to build the kernel. As kbuild generate pod manifests, it requires some variables to be set in the environment of kubernetes build clusters.

• KCI_INSTANCE: Type of the instance (e.g. prod, or anything else is detected as staging)
• KCI_INSTANCE_CALLBACK: Base URL used by services (such as scheduler-lava) to expose callback endpoints

And several secrets:

• name:kci-storage-tokens, key:production (or staging for staging) - contains the storage tokens for the storage backends
• name:kci-api-jwt-early access (or kci-api-jwt-staging for staging), key:token - contains the JWT token for the KernelCI API

Keep the secret names aligned with the manifests (for example kube/aks/scheduler-lava.yaml) when rolling new credentials.

JWT secret for kernelci-pipeline API

The lava-callback provides an API to the kci-dev tool, providing endpoints for custom checkouts, patchset testing, job retries, etc.

TOML

In the configuration file, you need to have the following section:

[jwt]
secret = "ABCDEFGH..."

Generating tokens for user

You can use the jwt_generator.py script in the tools directory to generate user tokens.

jwt_generator.py --secret ABCDEFGH... --email user@email.com

Include the permissions your workflow needs, for example:

jwt_generator.py --secret ABCDEFGH... --email user@email.com --permissions checkout,patchset,testretry