serving icon indicating copy to clipboard operation
serving copied to clipboard

Error: timeout: service 'hello' not ready after 600 seconds

Open alanmoleapfive opened this issue 2 years ago • 1 comments

kn service create hello \

--image gcr.io/knative-samples/helloworld-go
--port 8080
--env TARGET=World Creating service 'hello' in namespace 'default':

Error: timeout: service 'hello' not ready after 600 seconds Run 'kn --help' for usage

kn version Version: v20220823-local-6d86bf75 Build Date: 2022-08-23 20:27:36 Git Revision: 6d86bf75 Supported APIs:

  • Serving
    • serving.knative.dev/v1 (knative-serving v0.34.0)
  • Eventing
    • sources.knative.dev/v1 (knative-eventing v0.34.1)
    • eventing.knative.dev/v1 (knative-eventing v0.34.1) [root@edge-master alan]# kn-quickstart version Version: v1.7.0 Build Date: 2022-08-23 23:26:35 Git Revision: f9a6e8d [root@edge-master alan]# kubectl version Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-08-11T22:45:16Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"} WARNING: version difference between client (1.22) and server (1.24) exceeds the supported minor version skew of +/-1 [root@edge-master alan]# kubeadm version kubeadm version: &version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:02:08Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} [root@edge-master alan]# kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-6d4b75cb6d-mnqs7 1/1 Running 0 8h kube-system coredns-6d4b75cb6d-xb66b 1/1 Running 0 8h kube-system etcd-knative-control-plane 1/1 Running 0 8h kube-system kindnet-m87s7 1/1 Running 0 8h kube-system kube-apiserver-knative-control-plane 1/1 Running 0 8h kube-system kube-controller-manager-knative-control-plane 1/1 Running 1 (5h52m ago) 8h kube-system kube-proxy-zx4ln 1/1 Running 0 8h kube-system kube-scheduler-knative-control-plane 1/1 Running 1 (5h52m ago) 8h local-path-storage local-path-provisioner-6b84c5c67f-nnbh9 1/1 Running 0 8h

alanmoleapfive avatar Sep 07 '22 01:09 alanmoleapfive

From the kubectl get pod -A output, it doesn't look like the Knative components are running on your cluster. How did you set up your cluster?

psschwei avatar Sep 07 '22 12:09 psschwei

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

github-actions[bot] avatar Dec 26 '22 01:12 github-actions[bot]