Adding ADRs

Author: andrejcermak

ADRs/coder.md

@@ -0,0 +1,19 @@
+
+# Usage of Coder to facilitate terraform deployments
+
+## Status
+
+Accepted
+
+## Context
+
+The need for a Terraform automation/pipeline tool to facilitate Terraform deployments.
+
+## Decision
+
+We decided to use Coder for this. The alternative was to use our own Terraform pipeline implementation. 
+ 
+## Consequences
+
+This removed the struggle to make the Terraform pipelines safe, the need for our own authentication service and also deployment became easier, as Coder supports Docker deployments.
+

ADRs/ingress.md

@@ -0,0 +1,18 @@
+
+# Kubernetes Ingress over Cilium
+
+## Status
+
+Accepted
+
+## Context
+
+In order to make our service public, we needed to use some networking framework to deploy it on a cluster.
+
+## Decision
+
+First choice was to use Cilium, but after multiple days of struggle we opted for an easier option - Kubernetes Ingress.
+
+## Consequences
+
+Both development and deployment became much smoother, as Ingress is less complicated and better documented.

ADRs/oidc.md

@@ -0,0 +1,19 @@
+
+# Google OIDC for authentication
+
+## Status
+
+Accepted
+
+## Context
+
+To make a deployment of the OOD service possible, there needs to be some sort of (authentication)[https://osc.github.io/ood-documentation/latest/authentication.html]
+
+## Decision
+
+We decided to use Google OIDC, since its easy to setup and Google accounts are very popular. 
+
+## Consequences
+
+Pros: easy to setup and manage auth user. Cons: no mapping with OpenStack, so will need to be replaced in the future with the same OIDC provider as is used in the OpenStack deployment.
+