Update dependencies

Author: ThomasVitale

.github/workflows/deploy.yml

@@ -9,7 +9,7 @@ jobs:
       contents: write
     steps:
       - name: Checkout source code
-        uses: actions/checkout@v3.3.0
+        uses: actions/checkout@v4.1.0
       - name: Deploy website
         uses: redkubes/docusaurus-deploy-action@v1.2
         with:

docs/getting-started/installation.md

@@ -48,69 +48,23 @@ kapp deploy -a kapp-controller -y \
 Add the Kadras repository to make the platform 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:0.11.1 \
-    -n kadras-packages
-  ```
-
-## Create a Secret for the OCI Registry
-
-The platform will need to interact with a container registry. Create a Secret with the credentials to access your container registry with read/write permissions. 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
+    --url ghcr.io/kadras-io/kadras-packages:0.14.0 \
+    -n kadras-packages --create-namespace
   ```
 
 ## 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.
+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 for a local environment, based on the `run` installation profile.
 
 ```yaml title="values.yml"
 platform:
+  profile: run
+  infrastructure_provider: local
   ingress:
     domain: 127.0.0.1.sslip.io
-
-  oci_registry:
-    server: <oci-server>
-    repository: <oci-repository>
-
-contour:
-  envoy:
-    service:
-      type: ClusterIP
-    workload:
-      hostPorts:
-        enabled: true
-
-workspace_provisioner:
-  namespaces:
-    - name: default
-  git:
-    credentials:
-      username: <git-username>
-      password: <git-token>
 ```
 
-* `<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 the previous step 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 the previous step 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.
-* `<git-username>` is the name of your GitHub personal account or organization.
-* `<git-token>` is a personal access token with read permissions to your GitHub repositories.
-
 The Ingress is configured with the special domain `127.0.0.1.sslip.io` which will resolve to your localhost and be accessible via the kind cluster.
 
 ## Install the Platform
@@ -120,7 +74,7 @@ Reference the `values.yml` file you created in the previous step and install the
   ```shell
   kctrl package install -i engineering-platform \
     -p engineering-platform.packages.kadras.io \
-    -v 0.9.2 \
+    -v 0.12.0 \
     -n kadras-packages \
     --values-file values.yml
   ```

docs/getting-started/workload.md

@@ -3,40 +3,20 @@ sidebar_position: 2
 description: Create and view an application workload
 ---
 
-# Create a Workload
+# Deploy a Workload
 
-Kadras Engineering Platform provides out-of-the-box capabilities to support application development workflows from source code to URL.
+Kadras Engineering Platform provides capabilities to support application deployment workflows from image to URL based on Knative or plain Kubernetes.
 
-First, check out the sample Band Service application.
+First, ensure you have the [Knative CLI](https://knative.dev/docs/client/) installed.
 
-```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` using the [Cartographer CLI](https://github.com/ThomasVitale/cartographer-cli).
-
-```shell
-carto apps workload create --file config/workload.yml
-```
-
-Alternatively, you can create a workload using the Kubernetes CLI.
+Then, deploy an application from its OCI image.
 
 ```shell
-kubectl apply -f config/workload.yml
+kn service create band-service --image ghcr.io/thomasvitale/band-service
 ```
 
-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.
+The application will be available through a local URL with a self-signed certificate and autoscaling capabilities.
 
 ```shell
-carto apps workload get band-service
+https band-service.default.127.0.0.1.sslip.io --verify no
 ```
-
-The application will be available at `https://band-service.default.127.0.0.1.sslip.io`.