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
{{ message }}
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
➜ ~ k get po -l app=kiosk
NAME READY STATUS RESTARTS AGE
kiosk-6bbff86fd4-gts8n 1/1 Running 9 40d
➜ ~ k logs -p kiosk-6bbff86fd4-gts8n
E0513 03:51:13.342092 1 deleg.go:144] setup: unable to create client Get "https://10.80.0.1:443/api?timeout=32s": dial tcp 10.80.0.1:443: connect: connection refused
The text was updated successfully, but these errors were encountered:
@john-deng thanks for creating this issue! Seems like your cluster was not available during that time or kiosk couldn't connect to it, what Kubernetes cluster are you using?
@FabianKramm I am using kind cluster which is running Kubernetes v1.20.2, kiosk works fine, just saw the pod restarted so often, it may not work during the pod restarting I guess. so there is a risk that the kiosk will not available from time to time. Is the logging that I pasted above helps? It has only one line of logging presence when I type kubectl logs -p kiosk-pod-name.
@john-deng yes the log message helps, however I'm afraid there is not much we can do on our side to avoid this, as kiosk requires interaction with the Kubernetes API server during startup.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Kiosk restarted several times with below error
Version: kiosksh/kiosk:0.2.4
The text was updated successfully, but these errors were encountered: