diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
new file mode 100644
index 0000000..ce85c07
--- /dev/null
+++ b/.github/workflows/main.yml
@@ -0,0 +1,12 @@
+# main.yml
+on: [push]
+
+jobs:
+  operator:
+    runs-on: ubuntu-latest
+    name: build operator
+    steps:
+    - uses: actions/checkout@v3
+      with:
+        submodules: recursive
+    - uses: ./execDAT-operator/.github
diff --git a/docs/adrs/2023-03-16-public-vs-private-data.md b/docs/adrs/2023-03-16-public-vs-private-data.md
index b10e381..a5e0619 100644
--- a/docs/adrs/2023-03-16-public-vs-private-data.md
+++ b/docs/adrs/2023-03-16-public-vs-private-data.md
@@ -3,6 +3,7 @@
 Date: 2023-03-16
 
 ## Status
+
 __ACCEPTED__
 
 ## Context
@@ -15,4 +16,4 @@ For now we only allow public code repositories and data sources. This means that
 
 ## Consequences
 
-This means that the user has to make the code and data public. This is not a problem for the user, because the user wants to publish the code and data anyway. The user can always make the code and data private later.
\ No newline at end of file
+This means that the user has to make the code and data public. This is not a problem for the user, because the user wants to publish the code and data anyway. The user can always make the code and data private later.
diff --git a/docs/adrs/2023-03-DD-cicd-solution.md b/docs/adrs/2023-03-DD-cicd-solution.md
new file mode 100644
index 0000000..2c75292
--- /dev/null
+++ b/docs/adrs/2023-03-DD-cicd-solution.md
@@ -0,0 +1,26 @@
+# Title
+
+Date: YYYY-MM-DD
+
+## Status
+
+What is the status if the ADR?
+
+Possible options:
+* __PROPOSED__
+* __ACCEPTED__
+* __REJECTED__
+* __DEPRECATED__ (include reference to the superseding ADR)
+* __SUPERSEDED__ (include reference to the deprecating ADR)
+
+## Context
+
+What is the context of this ADR? What is the issue that we are seeing? What is motivating this decision or change?
+
+## Decision
+
+What is the change we are proposing? What do we plan on doing to solve the issue?
+
+## Consequences
+
+What are the consequences of the change? What will be more difficult? What will be easier?
\ No newline at end of file
diff --git a/execDAT-operator b/execDAT-operator
index 75ee221..adf4e7c 160000
--- a/execDAT-operator
+++ b/execDAT-operator
@@ -1 +1 @@
-Subproject commit 75ee221e70b73d4857c420e8de590ca57c3e4081
+Subproject commit adf4e7c26a22b8b058e70da85d448a127a4bc72f
diff --git a/k3d-dev.yaml b/k3d-dev.yaml
index bd73196..9cb8e60 100644
--- a/k3d-dev.yaml
+++ b/k3d-dev.yaml
@@ -1,11 +1,11 @@
 ---
-apiVersion: k3d.io/v1alpha4
+apiVersion: k3d.io/v1alpha5
 kind: Simple
 metadata:
   name: execdat-dev
 servers: 1
 agents: 0
-image: docker.io/rancher/k3s:v1.25.6-k3s1
+image: docker.io/rancher/k3s:v1.26.5-k3s1
 
 # kubeAPI: # same as `--api-port myhost.my.domain:6445` (where the name would resolve to 127.0.0.1)
 #   host: "myhost.my.domain" # important for the `server` setting in the kubeconfig
@@ -42,6 +42,14 @@ options:
       - arg: "--tls-san=k3d.localhost"
         nodeFilters:
           - server:*
+      - arg: "--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%"
+        nodeFilters:
+          - server:*
+          - agents:*
+      - arg: "--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%"
+        nodeFilters:
+          - server:*
+          - agents:*
   kubeconfig:
     updateDefaultKubeconfig: true # add new cluster to your default Kubeconfig; same as `--kubeconfig-update-default` (default: true)
     switchCurrentContext: true # also set current-context to the new cluster's context; same as `--kubeconfig-switch-context` (default: true)