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
Installing the new version of tobs in my new cluster does not work correctly.
The grafana-db init container fails due to name resolution.
$ kubectl logs -n tobs tobs-grafana-db-c5j2x -c init-db
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 0
Waiting 5 seconds
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 1
Waiting 5 seconds
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 2
Waiting 5 seconds
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 3
Waiting 5 seconds
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 4
Waiting 5 seconds
Checking if tobs.tobs.svc is up
Server: 10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local
nslookup: can't resolve 'tobs.tobs.svc'
Num times failed: 5
Failed 5 times while waiting for tobs.tobs.svc, exiting
I thought I'd managed to reproduce the underlying DNS issue with kind/minikube/k3s, but I cannot. So closing this, because it seems more an issue with my cluster (although busybox:uclibc has a long history of DNS issues).
In any case, making Grafana using SQLite seems to be a good idea :)
NOTE: if you use an editor to perform the change, make sure it does not leave a backup file behind. Helm will try to create things twice if there are backup files.
Installing the new version of tobs in my new cluster does not work correctly.
The grafana-db init container fails due to name resolution.
I can reproduce the issue easily:
There are many issues with DNS resolution with busybox (see https://bugs.busybox.net/show_bug.cgi?id=14671, docker-library/busybox#48 (comment)) and ndots.
If I use the
rockylinux:8
container, install bind-utils, the same name resolution works:Environment
Tobs CLI Version: 0.10.0, latest tobs helm chart version: 0.10.0
Single-node kubeadm-provisioned cluster on top of Fedora CoreOS, using crio. See https://github.com/alexpdp7/proxmox-k8s (passes sonobuoy, except for the tests that require multiple nodes)
The text was updated successfully, but these errors were encountered: