Update README

README.md

@@ -1,2 +1,54 @@
 # uds-capability-gitlab-runner
 Platform One Gitlab Runner deployed via flux
+
+## Pre-req
+- Minimum compute requirements for single node deployment are at LEAST 64 GB RAM and 32 virtual CPU threads (aws `m6i.8xlarge` instance type should do)
+- k3d installed on machine
+
+## Deploy
+
+### Use zarf to login to the needed registries i.e. registry1.dso.mil and ghcr.io
+
+```bash
+# Download Zarf
+make build/zarf
+
+# Login to the registry
+set +o history
+
+# registry1.dso.mil (To access registry1 images needed during build time)
+export REGISTRY1_USERNAME="YOUR-USERNAME-HERE"
+export REGISTRY1_TOKEN="YOUR-TOKEN-HERE"
+echo $REGISTRY1_TOKEN | build/zarf tools registry login registry1.dso.mil --username $REGISTRY1_USERNAME --password-stdin
+
+# ghcr.io (To access oci packages needed)
+export GH_USERNAME="YOUR-USERNAME-HERE"
+export GH_TOKEN="YOUR-TOKEN-HERE"
+echo $GH_TOKEN | build/zarf tools registry login ghcr.io --username $GH_USERNAME --password-stdin
+
+set -o history
+```
+
+### Deploy Everything
+
+```bash
+# This will destroy and create a compatible k3d cluster then it will run make build/all and make deploy/all. Follow the breadcrumbs in the Makefile to see what and how its doing it.
+make cluster/full
+```
+
+## Import Zarf Skeleton
+Below is an example of how to import this projects zarf skeleton into your zarf.yaml. The [uds-package-sofware-factory](https://github.com/defenseunicorns/uds-package-software-factory.git) does this with a subset of the uds-capability projects.
+
+```yaml
+components:
+  - name: values
+    required: true
+    files:
+      - source: <path-to-the-values-you-want-to-use>
+        target: values-gitlab-runner.yaml
+  - name: gitlab-runner
+    required: true
+    import:
+      name: gitlab-runner
+      url: oci://ghcr.io/defenseunicorns/uds-capability/gitlab-runner:0.0.3-skeleton
+```