search

HaraldUebele / HaraldUebele.github.io

Harald's Blog
https://haralduebele.github.io/
Other
0 stars 0 forks source link

Serverless and Knative - Part 2: Knative Serving – Harald Uebele's Blog #8

Open utterances-bot opened 3 years ago

utterances-bot commented 3 years ago

Serverless and Knative - Part 2: Knative Serving – Harald Uebele's Blog

In the first part of this series I went through the installation of Knative on CodeReady Containers which is basically Red Hat OpenShift 4.4 running on a notebook.

http://haralduebele.github.io/2020/06/03/serverless-and-knative-part-2-knative-serving/

vyom-soft commented 3 years ago

Hello Harald , Thank you for the detail explanation.

I have been following the same. For the same thing I see for Revision following status:

Last Transition Time: 2021-09-28T08:47:37Z Message: Requests to the target are being buffered as resources are provisioned. Reason: Queued Severity: Info Status: Unknown Type: Active Last Transition Time: 2021-09-28T08:47:37Z Reason: Deploying Status: Unknown Type: ContainerHealthy Last Transition Time: 2021-09-28T08:47:37Z Reason: Deploying Status: Unknown Type: Ready Last Transition Time: 2021-09-28T08:47:37Z Reason: Deploying Status: Unknown Type: ResourcesAvailable

And for the deployment follwing is seen:

$oc logs -f testserver-one-v1-deployment-6b454f955b-xddcd -c queue-proxy {"severity":"INFO","timestamp":"2021-09-28T10:17:23.8498997Z","caller":"logging/config.go:116","message":"Successfully create d the logger."} {"severity":"INFO","timestamp":"2021-09-28T10:17:23.8551836Z","caller":"logging/config.go:117","message":"Logging level set t o: info"} {"severity":"INFO","timestamp":"2021-09-28T10:17:23.8552177Z","caller":"logging/config.go:79","message":"Fetch GitHub commit ID from kodata failed","error":"\"KO_DATA_PATH\" does not exist or is empty"} {"level":"info","ts":1632824243.8555899,"logger":"fallback","caller":"metrics/metrics_worker.go:76","msg":"Flushing the exist ing exporter before setting up the new exporter."} {"level":"info","ts":1632824243.8557427,"logger":"fallback","caller":"metrics/prometheus_exporter.go:51","msg":"Created Prome theus exporter with config: &{knative.dev/internal/serving revision prometheus 5000000000 false 9091 0.0.0.0 fal se { false}}. Start the server for Prometheus exporter."} {"level":"info","ts":1632824243.8557637,"logger":"fallback","caller":"metrics/metrics_worker.go:91","msg":"Successfully updat ed the metrics exporter; old config: ; new config &{knative.dev/internal/serving revision prometheus 5000000000 <n il> false 9091 0.0.0.0 false { false}}"} aggressive probe error (failed 202 times): dial tcp 127.0.0.1:8080: connect: connection refused timed out waiting for the condition

I exactly coudn't find why it say connect: connection refused. Any suggestion from your point of view.

Harald-U commented 3 years ago

Hi Sanjeev,

I have no idea what fails and why and I can no longer reproduce; I have retired from IBM and have no more access to OpenShift clusters that I could test with.

A while ago I have modified the workshop that this blog post is based upon to work with Minikube and you can find it here.

HTH, Harald

Harald-U commented 3 years ago

Oh well, this is still bleeding edge and moving fast. I have updated the workshop to Knative v0.26 and it should work now, at least it did for me 15 minutes ago :-)