_NAME

Install Tekton Pipelines onto your cluster.If one or more of the deployments are not in the Running state, try increasing the number of nodes in your cluster.

ZenML has only been tested with Tekton Pipelines >=0.38.3 and may not work with previous versions.

Infrastructure Deployment

A Tekton orchestrator can be deployed directly from the ZenML CLI:

zenml orchestrator deploy tekton_orchestrator --flavor=tekton --provider=<YOUR_PROVIDER> ...

You can pass other configurations specific to the stack components as key-value arguments. If you don't provide a name, a random one is generated for you. For more information about how to work use the CLI for this, please refer to the dedicated documentation section.

How to use it

To use the Tekton orchestrator, we need:

The ZenML tekton integration installed. If you haven't done so, runCopyzenml integration install tekton -y

Docker installed and running.

Tekton pipelines deployed on a remote cluster. See the deployment section for more information.

The name of your Kubernetes context which points to your remote cluster. Run kubectl config get-contexts to see a list of available contexts.

A remote artifact store as part of your stack.

A remote container registry as part of your stack.

kubectl installed and the name of the Kubernetes configuration context which points to the target cluster (i.e. runkubectl config get-contexts to see a list of available contexts). This is optional (see below).

It is recommended that you set up a Service Connector and use it to connect ZenML Stack Components to the remote Kubernetes cluster, especially If you are using a Kubernetes cluster managed by a cloud provider like AWS, GCP or Azure, This guarantees that your Stack is fully portable on other environments and your pipelines are fully reproducible.

We can then register the orchestrator and use it in our active stack. This can be done in two ways: