Skip to content

Commit 0b87585

Browse files
committed
more cluster config
1 parent 389e71a commit 0b87585

File tree

3 files changed

+38
-3
lines changed

3 files changed

+38
-3
lines changed

docs/explanations/whats_in.rst

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,4 +73,7 @@ that where a repository generates an image the image will have the same name.
7373
containers from. e.g. ioc-pmac, ioc-adaravis
7474

7575
:k8s:
76-
this prefix is for utilities and documentation repos.
76+
this prefix is for utilities and documentation repositories.
77+
78+
:helm:
79+
this prefix is for definitions of helm charts or helm chart libraries

docs/how-to/kubernetes_cluster.rst

Lines changed: 32 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,35 @@
1-
Central Kubernetes Cluster Config
2-
=================================
1+
Kubernetes Cluster Config
2+
=========================
3+
4+
Cluster Options
5+
---------------
6+
7+
Three cluster topology approaches were considered for this project.
8+
9+
- **Separate Kubernetes cluster per beamline**. This could be as simple as
10+
a single server and the K3S installation described in
11+
`setup_kubernetes` may be sufficient. The documentation at
12+
https://rancher.com/docs/k3s/ also details how to make a high availability
13+
cluster, requiring a minimum of 4 servers.
14+
15+
- **A Central Facility Cluster**. A central facility cluster that runs
16+
all IOCs on its own nodes would keep everything centralized and provide
17+
economy of scale. However, there are significant issues with routing
18+
Channel Access, PVA and some device protocols to IOCs running in a
19+
different subnet to the beamline. DLS spent some time working around these
20+
issues but eventually abandoned this approach.
21+
22+
- **Central Cluster with Beamline nodes**. This approach uses the central
23+
cluster but adds beamline nodes that sit in the beamline itself,
24+
connected to the beamline subnet. This has all the benefits of central
25+
management but is able to overcome the problems with protocol routing.
26+
The DLS argus cluster configuration described below is an example of
27+
how to achieve this.
28+
29+
30+
31+
DLS Argus Cluster
32+
-----------------
333

434
**TODO** this section will give details of the topology and special
535
configuration used by the DLS argus cluster to enable running

docs/tutorials/setup_k8s.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
.. _setup_kubernetes:
2+
13
Setup Experimental Kubernetes
24
=============================
35

0 commit comments

Comments
 (0)