Enhance docs with Buildkit

Document usage of BuildKit and update all related docs

Author: qu1queee

docs/tutorials/README.md

@@ -46,6 +46,8 @@ For more information about strategies see the related [docs](/docs/buildstrategi
 
 * [Example with Buildpacks](/docs/tutorials/building_with_buildpacks.md)
 
+* [Example with Buildkit](/docs/tutorials/building_with_buildkit.md)
+
 Depending on your source code you might want to try a specific example. The following table serves as a guide to help you understand which
 strategy to choose:
 

docs/tutorials/building_with_buildkit.md

@@ -0,0 +1,109 @@
+
+# Building with Buildkit
+
+Before starting, make sure you have Tekton and Shipwright Build installed.
+
+See the [Try It!](../../README.md#try-it) section for more information.
+
+## Getting Started
+
+### Registry Authentication
+
+For this tutorial, we will require to create a `tutorial-secret` Kubernetes secret to access a [DockerHub](https://hub.docker.com/) registry, as follows:
+
+```sh
+$ REGISTRY_SERVER=https://index.docker.io/v1/ REGISTRY_USER=<your_registry_user> REGISTRY_PASSWORD=<your_registry_password>
+$ kubectl create secret docker-registry tutorial-secret --docker-server=$REGISTRY_SERVER --docker-username=$REGISTRY_USER --docker-password=$REGISTRY_PASSWORD  [email protected]
+```
+
+_Note_: For more information about authentication, please refer to the related [docs](/docs/development/authentication.md).
+
+## Create the strategy
+
+Ensure all strategies are in place, see the [Try It!](../../README.md#try-it) section for more information.
+
+```sh
+$ kubectl get cbs
+
+```
+
+_Note_: For more information about strategies, please refer to the related [docs](/docs/buildstrategies.md).
+
+## Creating a Build
+
+For the Build definition, we will require the following:
+
+- A GitHub repository containing a Go [application](https://github.com/shipwright-io/sample-go/tree/main/docker-build) that requires a `Dockerfile`.
+- The `tutorial-secret` we just created.
+- The `kaniko` ClusterBuildStrategy.
+
+Let's apply our Build and wait for it to be ready:
+
+```bash
+$ export REGISTRY_ORG=<your_registry_org>
+$ cat <<EOF | kubectl apply -f -
+apiVersion: shipwright.io/v1alpha1
+kind: Build
+metadata:
+  name: go-tutorial-using-buildkit
+spec:
+  source:
+    url: https://github.com/shipwright-io/sample-go
+    contextDir: docker-build/
+  dockerfile: docker-build/
+  strategy:
+    name: buildkit
+    kind: ClusterBuildStrategy
+  output:
+    image: docker.io/${REGISTRY_ORG}/go-tutorial:latest
+    credentials:
+      name: tutorial-secret
+EOF
+```
+
+Verify that the `go-tutorial` Build was created successfully:
+
+```sh
+
+```
+
+_Note_: For more information about Build resources, please refer to the related [docs](/docs/build.md).
+
+## Creating a BuildRun
+
+Second, we will create a `BuildRun` resource that references our previous `go-tutorial` Build:
+
+```sh
+$ cat <<EOF | kubectl create -f -
+apiVersion: shipwright.io/v1alpha1
+kind: BuildRun
+metadata:
+  name: go-tutorial-using-buildkit-buildrun
+spec:
+  buildRef:
+    name: go-tutorial-using-buildkit
+EOF
+```
+
+Wait until your `go-tutorial-buildrun` buildrun is completed:
+
+```sh
+
+```
+
+To know more about the state of the BuildRun, the `.Status.Conditions` fields provide more data:
+
+```sh
+
+```
+
+_Note_: A BuildRun is a resource that runs to completion. The `REASON` column reflects the state of the resource. If the BuildRun ran to completion successfully,
+a `Succeeded` `REASON` is expected.
+
+_Note_: For more information about BuildRun resources, please refer to the related [docs](/docs/buildrun.md).
+
+## Closing
+
+Congratulations! You just created a container image from https://github.com/shipwright-io/sample-go using [Buildkit](https://github.com/moby/buildkit).
+
+The new container image should now be available in your container registry.