From f9573e9d1b91c1dffc45c1ac38452b734431c978 Mon Sep 17 00:00:00 2001 From: Tristan Date: Mon, 11 Mar 2024 16:08:52 +0200 Subject: [PATCH] Fix links to deployment.md (previously deployment_new.md) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0b473dcb..ff0d377c 100644 --- a/README.md +++ b/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).