Add getting started guides

Author: ThomasVitale

docs/getting-started/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Getting Started",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "Getting started with Kadras Engineering Platform."
+  }
+}

docs/getting-started/installation.md

@@ -0,0 +1,107 @@
+---
+sidebar_position: 1
+description: Basic installation of the platform
+---
+
+# Installation
+
+Let's discover how to install a basic version of the Kadras Engineering Platform.
+
+## Prerequisites
+
+* Kubernetes 1.24+
+* Carvel [`kctrl`](https://carvel.dev/kapp-controller/docs/latest/install/#installing-kapp-controller-cli-kctrl) CLI.
+* Sigstore [`cosign`](https://docs.sigstore.dev/cosign/installation/) CLI.
+* Carvel [kapp-controller](https://carvel.dev/kapp-controller) deployed in your Kubernetes cluster. You can install it with Carvel [`kapp`](https://carvel.dev/kapp/docs/latest/install) (recommended choice) or `kubectl`.
+
+  ```shell
+  kapp deploy -a kapp-controller -y \
+    -f https://github.com/carvel-dev/kapp-controller/releases/latest/download/release.yml
+  ```
+
+## Add the Kadras Repository
+
+Add the Kadras repository to make all Kadras packages available to the cluster.
+
+  ```shell
+  kubectl create namespace kadras-packages
+  kctrl package repository add -r kadras-packages \
+    --url ghcr.io/kadras-io/kadras-packages \
+    -n kadras-packages
+  ```
+
+You can check the full list of available packages as follows.
+
+  ```shell
+  kctrl package available list -n kadras-packages 
+  ```
+
+## Create a Secret for the OCI Registry
+
+First, create a Secret with the credentials to access your container registry in read/write mode. It will be used by the platform to publish and consume OCI artifacts.
+
+  ```shell
+  export SUPPLY_CHAIN_REGISTRY_HOSTNAME=<hostname>
+  export SUPPLY_CHAIN_REGISTRY_USERNAME=<username>
+  export SUPPLY_CHAIN_REGISTRY_TOKEN=<token>
+  ```
+
+* `<hostname>` is the server hosting the OCI registry. For example, `ghcr.io`, `gcr.io`, `quay.io`, `index.docker.io`.
+* `<username>` is the username to access the OCI registry. Use `_json_key` if the hostname is `gcr.io`.
+* `<token>` is a token with read/write permissions to access the OCI registry. Use the contents of the service account key json if the hostname is `gcr.io`.
+
+  ```shell
+  kubectl create secret docker-registry supply-chain-registry-credentials \
+    --docker-server="${SUPPLY_CHAIN_REGISTRY_HOSTNAME}" \
+    --docker-username="${SUPPLY_CHAIN_REGISTRY_USERNAME}" \
+    --docker-password="${SUPPLY_CHAIN_REGISTRY_TOKEN}" \
+    --namespace=kadras-packages
+  ```
+
+## Configure the Platform
+
+The installation of the Kadras Engineering Platform can be configured via YAML. Create a `values.yml` file with any configuration you need for the platform. The following is a minimal configuration example.
+
+```yaml title="values.yml"
+platform:
+  ingress:
+    domain: <domain>
+
+  oci_registry:
+    server: <oci-server>
+    repository: <oci-repository>
+
+workspace_provisioner:
+  namespaces:
+    - name: default
+```
+
+* `<domain>` is the base domain name the platform will use to configure the Ingress controller. It must be a valid DNS name. For example, `lab.thomasvitale.com`.
+* `<oci-server>` is the server of the OCI registry where the platform will publish and consume OCI images. It must be the same used in step 3 when creating a Secret with the OCI registry credentials. For example, `ghcr.io`, `gcr.io`, `quay.io`, `index.docker.io`.
+* `<oci-repository>` is the repository in the OCI registry where the platform will publish and consume OCI images. It must be the same used in step 3 when creating a Secret with the OCI registry credentials. For example, it might be your username or organization name depending on which OCI server you're using.
+
+## Install the Platform
+
+Reference the `values.yml` file you created in the previous step and install the Kadras Engineering Platform.
+
+  ```shell
+  kctrl package install -i engineering-platform \
+    -p engineering-platform.packages.kadras.io \
+    -v ${VERSION} \
+    -n kadras-packages \
+    --values-file values.yml
+  ```
+
+You can find the `${VERSION}` value by retrieving the list of package versions available in the Kadras package repository installed on your cluster.
+
+  ```shell
+  kctrl package available list -p engineering-platform.packages.kadras.io -n kadras-packages
+  ```
+
+## Verify the Installation
+
+Verify that all the platform components have been installed and properly reconciled.
+
+  ```shell
+  kctrl package installed list -n kadras-packages 
+  ```

docs/getting-started/workload.md

@@ -0,0 +1,42 @@
+---
+sidebar_position: 2
+description: Create and view an application workload
+---
+
+# Create a Workload
+
+Kadras Engineering Platform provides out-of-the-box capabilities to support application development workflows from source code to URL.
+
+First, check out the sample Band Service application.
+
+```shell
+git clone https://github.com/thomasvitale/band-service
+```
+
+## Deploy a workload
+
+The platform exposes a Workload API based on [Cartographer](https://cartographer.sh) that developers use to trigger the supply chain for a given application.
+
+Deploy the Band Service application by creating a workload based on the configuration available in `config/workload.yml`.
+
+```shell
+carto apps workload create --file config/workload.yml
+```
+
+Alternatively, you can create a workload using the Kubernetes CLI.
+
+```shell
+kubectl apply -f config/workload.yml
+```
+
+The platform will check out the application source code and run it through a pre-configured supply chain that will package it as a container image, configure it and finally deploy it.
+
+## View a workload
+
+Using the Cartographer CLI, you can inspect the status of a workload and its supply chain.
+
+```shell
+carto apps workload get band-service
+```
+
+The application will be available at `https://band-service.default.<your-domain-name>`, where `<your-domain-name>` is the base domain used during the platform installation.

docs/intro.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 1
+---
+
+# Introduction
+
+Kadras Engineering Platform provides a foundation to support product teams in their activities to onboard, develop, deploy and operate application workloads.
+
+The platform provides several capabilities based on open-source projects, including:
+
+* Serverless deployments with Knative
+* Ingress controller with Contour
+* Certificate management with cert-manager
+* Paved paths to production with Cartographer
+* Build service with kpack and Cloud Native Buildpacks
+* Pipeline service with Tekton
+* Convention service with Cartographer Conventions
+* Secrets management with secretgen-controller
+* Policy management with Kyverno
+* Vulnerability and configuration scanning with Trivy
+* GitOps support with Flux, ArgoCD and Carvel
+* Air-gapped support with Carvel.
+
+Get started with Kadras by [installing the platform](/docs/getting-started/installation) and [creating your first workload](/docs/getting-started/workload).