The Shipwright Build APIs and controllers can be installed directly with our release deployment, or with our operator.
Kubernetes 1.21 or later.
Tekton pipelines v0.41 or later.
kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
The Shipwright operator is designed to be installed with the Operator Lifecycle Manager (“OLM”). Before installation, ensure that OLM has been deployed on your cluster by following the OLM installation instructions.
Once OLM has been deployed, use the following command to install the latest operator release from operatorhub.io:
$ kubectl apply -f https://operatorhub.io/install/shipwright-operator.yaml
To deploy and manage Shipwright Builds in your cluster, first make sure this operator is installed and running.
Next, create the following:
---
apiVersion: operator.shipwright.io/v1alpha1
kind: ShipwrightBuild
metadata:
name: shipwright-operator
spec:
targetNamespace: shipwright-build
The operator will deploy Shipwright Builds in the provided targetNamespace
.
When .spec.targetNamespace
is not set, the namespace will default to shipwright-build
.
Refer to the ShipwrightBuild documentation for more information about this custom resource.
We also publish a Kubernetes manifest that installs Shipwright directly into the shipwright-build
namespace.
Applying this manifest requires cluster administrator permissions:
$ kubectl apply -f https://github.com/shipwright-io/build/releases/latest/download/release.yaml --server-side=true
The Shipwright community maintains a curated set of build strategies for popular build tools. These can be optionally installed after Shipwright Builds has been deployed:
$ kubectl apply -f https://github.com/shipwright-io/build/releases/latest/download/sample-strategies.yaml
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.