You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorials/setup_k8s.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,20 +12,14 @@ For this reason DLS users should skip this tutorial unless you have a spare linu
12
12
13
13
## Introduction
14
14
15
-
This is a very easy set of instructions for setting up an experimental
16
-
single-node Kubernetes cluster, ready to test deployment of EPICS IOCs.
15
+
This is a very easy set of instructions for setting up an experimental single-node Kubernetes cluster, ready for a test deployment of EPICS IOCs.
17
16
18
17
## Bring Your Own Cluster
19
18
20
19
If you already have a Kubernetes cluster then you can skip this section.
21
20
and go straight to the next tutorial.
22
21
23
-
IMPORTANT: you will require appropriate permissions on the cluster to work
24
-
with epics-containers. In particular you will need to be able to create
25
-
pods that run with network=host. This is to allow Channel Access traffic
26
-
to be routed to and from the IOCs. You will also need to be able to create
27
-
a namespace and a service account, although you could use an existing
28
-
namespace and service account as long as it has network=host capability.
22
+
IMPORTANT: you will require appropriate permissions on the cluster to work with epics-containers. In particular you will need to be able to create pods that run with network=host. This is to allow Channel Access traffic to be routed to and from the IOCs. You will also need to be able to create a namespace and a service account, although you could use an existing namespace and service account as long as it has network=host capability. The alternative to running with network=host is to run a ca-gateway in the cluster and expose the PVs to the IOCs via the gateway.
29
23
30
24
Cloud based K8S offerings may not be appropriate because of the Channel Access
0 commit comments