adamant-kite-43734
11/07/2022, 7:23 PMbillions-airline-85860
11/08/2022, 10:05 AMserver {
listen 443;
proxy_pass my_agent_nodes_443;
}
upstream my_agent_nodes_443 {
server 185.230.138.110:30679;
server 185.239.208.173:30679;
server 38.242.195.7:30679;
server 38.242.134.42:30679;
}
And, everything is working hunky dory (which is why I'm flabbergasted). My missing understanding is, how did I get the port numbers for the worker nodes i.e. 30679?
I do all this for a hobby and did this work like 6 months ago, but didn't think to also document how I got to the port number and I can't find any mention of those ports in the emissary configs, only listeners for ports 80 and 443. 😮billions-airline-85860
11/08/2022, 10:06 AMbillions-airline-85860
11/08/2022, 10:14 AMadamant-kite-43734
11/09/2022, 7:27 PMclever-air-65544
11/11/2022, 2:57 PMadamant-kite-43734
11/14/2022, 3:41 PMadamant-kite-43734
11/14/2022, 8:44 PMadamant-kite-43734
11/15/2022, 8:30 AMadamant-kite-43734
11/16/2022, 2:41 PMadamant-kite-43734
11/16/2022, 4:48 PMfuture-fountain-82544
11/17/2022, 10:31 PMadamant-kite-43734
11/17/2022, 10:33 PMadamant-kite-43734
11/18/2022, 4:13 PMadamant-kite-43734
11/21/2022, 10:13 AMadamant-kite-43734
11/22/2022, 4:56 PMbright-london-1095
11/23/2022, 1:06 AMk3s
version 1.22.8
and the traffic pod is in crashLoopBackOff and not accessible. I tried deleting pod but didn't help!
+ helm_v3 install --set-string global.systemDefaultRegistry= traefik <https://10.49.0.22:443/static/charts/traefik-10.14.100.tgz> --value/config/values-01_HelmChart.yaml --values /config/values-10_HelmChartConfig.yaml
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
bright-london-1095
11/23/2022, 1:15 AMkube-system pod/helm-install-traefik-q76r7 0/1 CrashLoopBackOff 5 (63s ago) 4m32s
bright-london-1095
11/23/2022, 1:26 AMk3s
logs:
Nov 23 01:19:01 nestle-test k3s[1186]: I1123 01:19:01.070591 1186 scope.go:110] "RemoveContainer" containerID="e87d34e8fb2f4d3e07ab9ee9e8656ee73f0cd1dd00f7bce0ee9956d3bc091c67"
Nov 23 01:19:01 nestle-test k3s[1186]: E1123 01:19:01.070873 1186 pod_workers.go:949] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"helm\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=helm pod=helm-install-traefik--1-8htfg_kube-system(9833a11e-3065-48d7-908f-baf37fef0168)\"" pod="kube-system/helm-install-traefik--1-8htfg" podUID=9833a11e-3065-48d7-908f-baf37fef0168
Nov 23 01:19:03 nestle-test k3s[1186]: E1123 01:19:03.366518 1186 remote_runtime.go:164] "RemovePodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to remove volatile sandbox root directory \"/run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/345c21c66d2e341863fb9b95eb829a477f2c6e799016674d3b2a80fe113601a1\": unlinkat /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/345c21c66d2e341863fb9b95eb829a477f2c6e799016674d3b2a80fe113601a1/shm: device or resource busy" podSandboxID="345c21c66d2e341863fb9b95eb829a477f2c6e799016674d3b2a80fe113601a1"
bright-london-1095
11/23/2022, 1:31 AMtraefik
shipped with k3s
(v1.22.8+k3s1)adamant-kite-43734
11/23/2022, 8:04 AMkind-helmet-90731
11/24/2022, 6:39 AMadamant-kite-43734
11/24/2022, 6:39 AMkind-helmet-90731
11/24/2022, 6:42 AMadamant-kite-43734
11/24/2022, 7:41 AMfull-park-34540
11/24/2022, 3:36 PMadamant-kite-43734
11/25/2022, 3:21 PMadamant-kite-43734
11/25/2022, 4:24 PMred-boots-23091
11/25/2022, 5:36 PMadamant-kite-43734
11/26/2022, 12:35 AM