Forum Discussion

ahmedpasic's avatar
ahmedpasic
New Contributor
5 months ago
Solved

Kots Admin Console not installing

I am trying to install Kots Admin Console on my Kubernetes cluster by running: kubectl kots install swaggerhub \   --namespace data-swaggerhub-prod \   --kotsadm-namespace data-swaggerhub-prod \ ...
  • ahmedpasic's avatar
    ahmedpasic
    5 months ago

    Issue was that the app is using the domain names for the service instead of using just the k8s service name. It would have worked if my cluster was using the default :

    ...svc.cluster.local

    But that was not the case. I had to manually change the deployment to not refer to this name for my services.

ahmedpasic's avatar
ahmedpasic
New Contributor
5 months ago

Update: I didn't post the whole error message:

Error: plan sync from file "/tables/api_task_status.yaml": failed to plan table sync: failed to plan table sync for api_task_status: failed to query from sqlite_master: tried all peers unsuccessfully. here are the results:
   peer #0: http://kotsadm:xxxxx@kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local:4001/db/query?timings&level=weak&transaction failed due to Post "http://kotsadm:***@kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local:4001/db/query?timings&level=weak&transaction": dial tcp: lookup kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local on 10.150.218.142:53: no such host
plan sync from file "/tables/api_task_status.yaml": failed to plan table sync: failed to plan table sync for api_task_status: failed to query from sqlite_master: tried all peers unsuccessfully. here are the results:
   peer #0: http://kotsadm:xxxxx@kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local:4001/db/query?timings&level=weak&transaction failed due to Post "http://kotsadm:***@kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local:4001/db/query?timings&level=weak&transaction": dial tcp: lookup kotsadm-rqlite.data-swaggerhub-prod.svc.cluster.local on 10.150.218.142:53: no such host

Seems like it can't reach the rqlite pod through the service that's created. The thing is, I tested the connection from another pod and it works:

 

<<K9s-Shell>> Pod: data-swaggerhub-prod/nettools | Container: nettools
[root@nettools /]# nslookup kotsadm-rqlite
Server:		10.150.214.16
Address:	10.150.214.16#53

Name:	kotsadm-rqlite.data-swaggerhub-prod.svc.kryptonite
Address: 172.31.78.139

[root@nettools /]# wget http://kotsadm-rqlite:4001/
--2025-05-16 21:06:57--  http://kotsadm-rqlite:4001/
Resolving kotsadm-rqlite (kotsadm-rqlite)... 172.31.78.139
Connecting to kotsadm-rqlite (kotsadm-rqlite)|172.31.78.139|:4001... connected.
HTTP request sent, awaiting response... 302 Found
Location: /status [following]
--2025-05-16 21:06:57--  http://kotsadm-rqlite:4001/status
Reusing existing connection to kotsadm-rqlite:4001.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/json]
Saving to: 'index.html'

index.html                                                         [ <=>                                                                                                                                                 ]   6.34K  --.-KB/s    in 0s

2025-05-16 21:06:57 (440 MB/s) - 'index.html' saved [6488]

[root@nettools /]#