wide-author-88664
12/09/2022, 5:26 PM--tls-san
option more than once if I want to add both an IP and a DNS name as SANs, or does the --tls-san
option accept multiple values (and, how to specify multiple values then?)wide-author-88664
12/09/2022, 5:26 PMlimited-accountant-71118
12/12/2022, 9:57 AMabundant-camera-87627
12/12/2022, 10:44 AM/etc/rancher/k3s/registries.yaml
? I've entered several entries, but it looks like none of them are being honored.
I have entries as follows:
mirrors:
"<http://docker.io|docker.io>":
endpoint:
- "<https://registry>.<fqdn>"
rewrite:
"(.*)": "library/docker.io/$1"
However pods are not coming up with the following errors:
Failed to pull image "<http://docker.io/bitnami/sealed-secrets-controller:v0.18.1|docker.io/bitnami/sealed-secrets-controller:v0.18.1>": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/bitnami/sealed-secrets-controller:v0.18.1|docker.io/bitnami/sealed-secrets-controller:v0.18.1>": failed to resolve reference "<http://docker.io/bitnami/sealed-secrets-controller:v0.18.1|docker.io/bitnami/sealed-secrets-controller:v0.18.1>": failed to do request: Head "<https://registry-1.docker.io/v2/library/docker.io/bitnami/sealed-secrets-controller/manifests/v0.18.1>": dial tcp 44.205.64.79:443: connect: no route to host
Similarly, k3s ctr image pull <http://docker.io/bitnami/sealed-secrets-controller:v0.18.1|docker.io/bitnami/sealed-secrets-controller:v0.18.1>
returns the same error.average-night-25048
12/12/2022, 4:49 PMhelpful-window-37061
12/17/2022, 7:03 AMred-daybreak-12301
12/18/2022, 12:11 AMalert-refrigerator-93230
12/18/2022, 2:02 AMmicroscopic-exabyte-68097
12/18/2022, 9:16 PMicy-finland-84263
12/18/2022, 9:32 PMHelmChart
CRD. I came across a chat from this channel via google (link) which is pretty much my exact problem, I was interested to know if this ever went anywhere? Any info would be greatly appreciated!shy-shampoo-22224
12/19/2022, 4:56 PMbright-london-1095
12/20/2022, 1:57 PM502 bad gateway
. Has any faced this issue ? k3s: v1.22.8
echo 'Installing helm_v3 chart'
helm_v3 install --set-string global.systemDefaultRegistry= traefik <https://10.43.0.1:443/static/charts/traefik-10.14.100.tgz> --values /config/values-01_HelmChart.yaml --values /config/values-10_HelmChartConfig.yaml
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
important-tomato-46085
12/21/2022, 4:15 AMsquare-coat-44873
12/21/2022, 4:21 PMsquare-coat-44873
12/21/2022, 10:56 PMcurl -sfL <https://get.k3s.io> | sh -
Do I run this on each k3s server (master)? on each agent (worker)? Does this upgrade the underlying version of k8s as well (and all of the underlying tools, i.e. containerd, runc, …)? https://docs.k3s.io/upgrades/manual#upgrade-k3s-using-the-installation-scriptable-mechanic-45652
12/22/2022, 6:12 AMcurved-army-69172
12/22/2022, 9:00 AMcurved-army-69172
12/22/2022, 9:07 AMcurved-army-69172
12/22/2022, 10:44 AMacoustic-sunset-13848
12/22/2022, 1:40 PMbrainy-action-93740
12/22/2022, 10:30 PMhallowed-student-81622
12/23/2022, 4:38 PMsudo firewall-cmd --zone=trusted --add-interface=flannel.1 --permanent
sudo firewall-cmd --zone=trusted --add-masquerade --permanent
sudo firewall-cmd --zone=trusted --add-port=6443/tcp --permanent
sudo firewall-cmd --zone=trusted --add-port=10250/tcp --permanent
sudo firewall-cmd --zone=trusted --add-port=8472/udp --permanent
sudo firewall-cmd --zone=trusted --add-port=51820/udp --permanent
sudo firewall-cmd --zone=trusted --add-port=51821/udp --permanent
sudo firewall-cmd --reload
wonderful-appointment-6480
12/24/2022, 8:09 AMgray-river-53365
12/25/2022, 8:09 PMplain-dress-30909
12/27/2022, 7:31 AMcolossal-action-96650
12/27/2022, 3:44 PM2477 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, [invalid bearer token, square/go-jose: error in cryptographic primitive]]"
And, they never show up in the output of kubectl get nodes
I’ve Googled that error and find many bug reports, posts, etc. but no definitive answer or solution. I’ve wiped out these new nodes and started fresh, but still get the same error.
Any advice would be appreciated.witty-pharmacist-4169
12/28/2022, 4:37 AMBad Gateway
And nothing else. I deployed an Ubuntu pod to test things out, and the service it's trying to connect to functions properly and I get the output from the pod while curl'ing the service DNS. It really feels like an issue between the ingress and the service. When I deploy an ingress with Helm it gives me the following errors within the Traefik pod.
time="2022-12-28T03:08:21Z" level=error msg="Skipping service: no endpoints found" providerName=kubernetes serviceName=test servicePort="&ServiceBackendPort{Name:,Number:80,}" ingress=test namespace=default
time="2022-12-28T03:08:22Z" level=error msg="Skipping service: no endpoints found" servicePort="&ServiceBackendPort{Name:,Number:80,}" providerName=kubernetes namespace=default ingress=test serviceName=test
able-mechanic-45652
12/28/2022, 1:39 PMlate-city-83596
01/02/2023, 12:17 AMlate-needle-80860
01/02/2023, 5:05 PMError: EMFILE: too many open files, watch '/'
at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
at Object.watch (node:fs:2303:34)
at /usr/local/lib/node_modules/json-server/lib/cli/run.js:179:10 {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
path: '/',
filename: '/'
}