Initial attempt at k8s

Requires more work to syncronize everything. Maybe setting up
several dedicated proxy containers might be useful (for load
balancing and TLS handling).

This could possibly use something like Redis as a datastore and
KubeMQ for pubsub.

k8s/app-deployment.yaml

@@ -0,0 +1,35 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: syncplay-srv
+  labels:
+    app: syncplay-srv
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: syncplay-srv
+  template:
+    metadata:
+      labels:
+        app: syncplay-srv
+    spec:
+      containers:
+      - name: syncplay-srv
+        image: weeb-poly/syncplay-srv
+        env:
+        - name: SYNCPLAY_PORT
+          value: "8995"
+        - name: SYNCPLAY_PASSWORD
+          valueFrom:
+            secretKeyRef:
+              name: syncplay
+              key: password
+        - name: SYNCPLAY_SALT
+          valueFrom:
+            secretKeyRef:
+              name: syncplay
+              key: salt
+        ports:
+        - containerPort: 8995
+      restartPolicy: Always

k8s/app-service.yaml

@@ -0,0 +1,23 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: syncplay-srv
+spec:
+  selector:
+    app: syncplay-srv
+  ports:
+  - port: 8995
+    protocol: TCP
+    targetPort: 8995
+  - port: 8996
+    protocol: TCP
+    targetPort: 8995
+  - port: 8997
+    protocol: TCP
+    targetPort: 8995
+  - port: 8998
+    protocol: TCP
+    targetPort: 8995
+  - port: 8999
+    protocol: TCP
+    targetPort: 8995