Fix links to deployment.md (previously deployment_new.md) (#147)

* WIP: Update GitHub Actions workflow

* Fix links to deployment.md (previously deployment_new.md)

Author: trispera

.github/workflows/build.yaml

@@ -10,23 +10,51 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/[email protected]
-        
-      - name: Create Kind Cluster
-        uses: helm/[email protected]
-        
+        with:
+          fetch-depth: 0
+            
+      - name: Create k3s Cluster
+        uses: debianmaster/[email protected]
+        with:
+          version: 'latest'
+            
       - name: Create namespace
         run: kubectl create ns tesk
 
-      - name: Lint chart
-        run: helm lint
-        working-directory: charts/tesk
+      - name: Helm Deps
+        run: |
+          for dir in $(ls -d charts/*); do
+            helm dependency update $dir;
+          done
+    
+      - name: Helm Lint
+        run: |
+          for dir in $(ls -d charts/*); do
+            helm lint $dir
+          done
         
       - name: Apply Helm file
         run: helm install -n tesk tesk . -f values.yaml
         working-directory: charts/tesk
 
-      - name: Sleep for 10 seconds
-        run: sleep 10
-        
+      - name: Sleep for 30 seconds
+        run: sleep 30
+           
       - name: Get Helm and k8s
         run: helm list -n tesk && kubectl get all -n tesk
+    
+      - name: curl URL
+        run: curl localhost -vL
+            
+      - name: Configure Git
+        run: |
+          git config user.name "$GITHUB_ACTOR"
+          git config user.email "[email protected]"
+    
+      - name: Run chart-releaser
+        uses: helm/[email protected]
+        with:
+          skip_existing: true
+        env:
+          CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+    

README.md

@@ -10,7 +10,7 @@ For organisational reasons, this project is split into 3 repositories:
 
 If the API is running on your cluster it will pull the images from our `docker.io` repository automatically.
 
-`TESK` is designed with the goal to support any `Kubernetes` cluster, for its deployment please refer to the [deployment](documentation/deployment_new.md) page.
+`TESK` is designed with the goal to support any `Kubernetes` cluster, for its deployment please refer to the [deployment](documentation/deployment.md) page.
 
 The technical documentation is available in the [documentation](documentation) folder.
 
@@ -30,4 +30,4 @@ After the last executor, the `filer` is called once more to process the outputs
 -   A working [Kubernetes](https://kubernetes.io/) cluster version 1.9 and later.
 -   If you want TESK to handle tasks with I/O (and you probably want), you additionally need:
 -   A default storage class, which TESK will use to create temporary PVCs. It is enough that the storage class supports the RWO mode.
--   And, if you want TESK to integrate with workflow managers, you additionally need either an FTP account or a PVC that can be accessed from within or from outside of the cluster by the workflow manager (more in the [deployment](documentation/deployment_new.md) page).
+-   And, if you want TESK to integrate with workflow managers, you additionally need either an FTP account or a PVC that can be accessed from within or from outside of the cluster by the workflow manager (more in the [deployment](documentation/deployment.md) page).