-
Notifications
You must be signed in to change notification settings - Fork 25
46 lines (45 loc) · 1.47 KB
/
multi-cluster.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
name: Two clusters on default networks
on:
[workflow_dispatch, push]
jobs:
k3d-multicluster-demo:
name: Two clusters on default networks
runs-on: ubuntu-20.04
steps:
- uses: actions/checkout@v2
- uses: ./
name: "Create 1st k3d Cluster"
with:
cluster-name: "test-cluster-1"
args: >-
-p "80:80@agent:0:direct"
-p "443:443@agent:0:direct"
-p "5053:53/udp@agent:0:direct"
--agents 3
--no-lb
--k3s-arg "--no-deploy=traefik,servicelb,metrics-server@server:*"
- uses: ./
name: "Create 2nd k3d Cluster"
with:
cluster-name: "test-cluster-2"
args: >-
-p "81:80@agent:0:direct"
-p "444:443@agent:0:direct"
-p "5054:53/udp@agent:0:direct"
--agents 3
--no-lb
--k3s-arg "--no-deploy=traefik,servicelb,metrics-server@server:*"
- name: Cluster info
run: |
kubectl cluster-info --context k3d-test-cluster-1 && kubectl cluster-info --context k3d-test-cluster-2
- name: Nodes
run: |
docker ps -a
kubectl config use-context k3d-test-cluster-1
kubectl get nodes -o wide
kubectl config use-context k3d-test-cluster-2
kubectl get nodes -o wide
- name: Network
run: |
docker network inspect k3d-test-cluster-1
docker network inspect k3d-test-cluster-2