Configuration is waiting for a Revision to become ready #1971
Comments
knative-prow-robot
added
area/networking
kind/bug
|
finally i make it work in a kubernetes 1.11.2 cluster which bootstrap by kubeadm (proxy is the major problem) u should set http_proxy, https_proxy and no_proxy env in knative-serving controller yaml when u run knative behind a proxy as controller will connect the docker registry to get the digest of the image back to my problem it seems and once we send a request, then it changes to rathen then my previous post, it remains in need sometimes to dive into it |
|
an old story now, close it |
|
@zrss how did you set proxy in serving controllers, can you please elaborate. |
|
@indreshmishra , hope u have found it out, i set the proxy in serving controller in this way see the deployment.yaml of serving controller serving/config/controller.yaml Lines 33 to 43 in 55c6c1d and add kind of these envs to deployment.yaml (see here define-an-environment-variable-for-a-container) env:
- name: http_proxy
value: {your_http_proxy}
- name: https_proxy
value: {your_https_proxy}
- name: no_proxy
value: {your_no_proxy} |
Expected Behavior
i bootstrap a k8s 1.11 cluster in a Ubuntu 18.04.1 LTS vm through
local-up-cluster.sh(and also install a one master and two nodes k8s 1.11.2 by kubeadm) and follow the startup demo here https://github.com/knative/docs/blob/master/install/Knative-with-any-k8s.md to install knative and play with a demo app https://github.com/knative/docs/blob/master/install/getting-started-knative-app.mdFinally, after the all effort i have done, maybe i can curl the demo app and get the expected response
Actual Behavior
Steps to Reproduce the Problem
Follow the guide https://github.com/knative/docs/blob/master/install/Knative-with-any-k8s.md and https://github.com/knative/docs/blob/master/install/getting-started-knative-app.md step by step
Additional Info
knative serving
kubectl and cluster version
pods status (all pods seems running well)
and there are some relative CRD resources status
revisions.serving.knative.dev
configurations.serving.knative.dev
services.serving.knative.dev
it seems that services.serving.knative.dev is waiting for a revision to become ready, but from the view of revisions.serving.knative.dev and configurations.serving.knative.dev crd, i can't found any exception about its status except for the condition.status is all Unknown
by the way, i notice that crazy idea #638 and its work
and find there is a
go-containerregistryremote call to get the digest of imageserving/pkg/reconciler/v1alpha1/revision/resolve.go
Lines 65 to 69 in 16d5cc1
pay attention to that will failed in nslookup gcr.io as there is no upstreamServer in kube-dns
i have to add following config to the kube-dns configmap, and kill the pod of kube-dns
to fix
Get https//gcr.io/v2/i/o timeout in revisions.serving.knative.dev status.conditionsbut it still not work
The text was updated successfully, but these errors were encountered: