content: replace rancher-based edu cluster with data science cluster

* NS_NAME convention
* docu links
* re-add FAQ section on how to configure kubectl

Author: lucendio

content/_index.md

@@ -52,7 +52,7 @@ Or maybe you are already overwhelmed? No worries, try [How to learn DevOps](http
 
 ## External resources/repositories
 
-* [Education Kubernetes Cluster Documentation](https://gitlab.bht-berlin.de/ris/doku/-/wikis/educluster) 📖
+* [Education Kubernetes Cluster Documentation](https://docs.cluster.ris.bht-berlin.de/) 📖
 * [showcase](https://gitlab.bht-berlin.de/fb6-wp11-devops/showcase)
 * [Tutorial solutions](https://github.com/lucendio/lecture-devops-code/tutorials)
 * [code examples](https://github.com/lucendio/lecture-devops-code)

content/exercises/deploy-app-on-kubernetes.md

@@ -58,15 +58,9 @@ can be found
 
 ### (0) Preparations {id="0-prep-edu-cluster"}
 
-{{< hint info >}}
-📖 [__Upstream documentation__ (german)](https://gitlab.bht-berlin.de/ris/doku/-/wikis/educluster#nutzung-des-clusters-mit-kubectl)
-{{< /hint >}}
-
-1. [login and obtain the *Kubeconfig File*]({{< ref "/faq/cloud-and-infrastructure#kubeconfig-of-edu-cluster">}})
-2. navigate to *Projects/Namespaces*, click on *Add Namespace* (right) in the area where the project is named after
-   this module; give the namespace a meaningful & unique name (e.g. university/student account ID)
-3. [install `kubectl`](https://kubernetes.io/docs/tasks/tools/#kubectl) on your workstation, if it doesn't
-   exist already
+Assuming [prerequisites](#prerequisites) are meet and you can access the cluster with `kubectl`, the 
+Kubernetes *namespace* (`{{ NS_NAME }}`) for you to use moving forward, is named the same as the
+username of your university account. 
 
 {{< hint warning >}}
 Moving forward, either use `-n {{ NS_NAME }}` whenever namespaced objects are involved, or configure it as the
@@ -240,11 +234,10 @@ To eventually make the application available from outside the cluster, write an
 pointing to the `Service` that you just created.
 
 {{< hint warning >}}
-The ingress controller of the education cluster runs on a single node (`141.64.89.201`)
-directly on the cluster. The respective DNS entry is an A record pointing to `*.lehre.ris.bht-berlin.de`, 
-which is why the ingress host must be set to `{{ SUB_DOMAIN }}.lehre.ris.bht-berlin.de`, where `SUB_DOMAIN`
-is a virtual but globally unique host name with the format: `{{ SERVICE_NAME }}-{{ NS_NAME }}`, e.g.
-`myservice-987456.lehre.ris.bht-berlin.de` (see [*Preparations* section]({{< relref "#0-prep-edu-cluster" >}}))
+All cluster users share the same DNS zone `project.ris.bht-berlin.de`, which is why the ingress *host* must be set
+to `{{ SUB_DOMAIN }}.project.ris.bht-berlin.de`, where `SUB_DOMAIN` is a virtual but globally unique host name with
+the format: `{{ SERVICE_NAME }}-{{ NS_NAME }}`, e.g. `myservice-abcd1234.project.ris.bht-berlin.de`
+(see [*Preparations* section]({{< relref "#0-prep-edu-cluster" >}}))
 {{< /hint >}}
 
 ```bash
@@ -256,8 +249,9 @@ Finally, verify that the application is indeed accessible from your browser (or
 
 ### (4) Cleaning up
 
-Use the [cluster management web console](https://rancher.ris.beuth-hochschule.de) to delete your namespace,
-which will then delete all associated objects.
+```bash
+kubectl delete all --all
+```
 
 
 ## Solution: Minikube {id="solution-minikube"}

content/exercises/manage-kubernetes-objects-with-helm.md

@@ -202,8 +202,8 @@ helm uninstall {{ RELEASE_NAME }}
 ### (4) Enable TLS
 
 The feature is covered in the upstream documentation
-([TLS](https://gitlab.bht-berlin.de/ris/doku/-/wikis/educluster#ressourcen-service-ingress),
-You just have to integrate the respective attributes and objects into you chart(s) and make them
+([TLS](https://docs.cluster.ris.bht-berlin.de/user/ingress/)) and may require additional permission upon request.
+If permitted, you just have to integrate the respective attributes and objects into you chart(s) and make them
 configurable via Helm values if needed.
 
 

content/exercises/persist-state-on-kubernetes.md

@@ -49,8 +49,8 @@ TODO
 ### (1) Enable TLS and Data persistence
 
 Both features are covered in the upstream documentation
-([TLS](https://gitlab.bht-berlin.de/ris/doku/-/wikis/educluster#ressourcen-service-ingress),
-[Storage](https://gitlab.bht-berlin.de/ris/doku/-/wikis/educluster#ressourcen-volumes-persistener-speicher-f%C3%BCr-deployments-und-pods)).
+([TLS](https://docs.cluster.ris.bht-berlin.de/user/ingress/),
+[Storage](https://docs.cluster.ris.bht-berlin.de/user/storage/)).
 You just have to integrate the respective attributes and objects into you chart(s) and make them
 configurable via Helm values if needed.
 

content/faq/cloud-and-infrastructure.md

@@ -16,8 +16,7 @@ a) your workstation has enough resources (CPU, memory) to host one or more virtu
 
 b) have a look at the link section on [*cloud providers*]({{< ref "/links#cloud-providers" >}})
 
-c) the university provides a Kubernetes cluster managed with Rancher (requires student account, and VPN access if you
-   are not on-site)
+c) the university provides a Kubernetes cluster (requires student account, and VPN access)
 
 
 ## Which cloud provider should I use?
@@ -107,6 +106,18 @@ __*Example with DNS delegation (AWS + Name.com):*__
 4. Create additional records, e.g. `sub.doamin.tld` in the *Hosted Zone* on AWS Route 53 with OpenTofu
 
 
+## How to configure `~/.kube/config` (`KUBECONFIG`) for `kubectl` in order to access the university's Kubernetes cluster? {id="kubeconfig-of-edu-cluster"}
+
+{{< hint warning >}}
+Did you already enter your university email address in the respective account list?
+{{< /hint >}}
+
+1. connect to the internal network via [VPN](https://doku.bht-berlin.de/zugang/vpn)
+2. [test](https://auth.cluster.ris.bht-berlin.de) whether your university account is permitted
+   to access the cluster
+3. follow the [cluster documentation](https://docs.cluster.ris.bht-berlin.de/user/kubectl/)
+
+
 ## Which registry supports pushing container images? 
 
 The following registries are hosted offerings: