Skip to content

Commit 71100ed

Browse files
alexelliswelteki
authored andcommitted
Minor update to flags for new slicer release
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
1 parent 4168645 commit 71100ed

File tree

1 file changed

+5
-0
lines changed
  • cluster-autoscaler/cloudprovider/slicer

1 file changed

+5
-0
lines changed

cluster-autoscaler/cloudprovider/slicer/README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ The autoscaler is run out of cluster for now, on your local machine.
99

1010
K3sup Pro makes scaffolding the cluster, and fetching the various secrets much easier and is included with the Slicer bundle.
1111

12+
On your local machine, you'll have to run the route commands so that your local machine can reach the Slicer API and the K3s nodes.
13+
14+
If your control plane and agents are on different machines (recommended), then you'll need to run the routes in on the respective hosts, so the control plane can reach the agents, and the agents the control plane. However if these are on the same virtualisation server, *do not run the routes there*.
15+
1216
### Pre-setup
1317

1418
Create an initial K3s cluster with 3x nodes using the following command on the virtualization server:
@@ -20,6 +24,7 @@ slicer new k3s-cp \
2024
--count=3 \
2125
--cidr 192.168.137.0/24 \
2226
--api-port=8080 \
27+
--api-bind="0.0.0.0" \
2328
--ssh-key
2429
> k3s-cp.yaml
2530

0 commit comments

Comments
 (0)