Looking for help: helloworld-go IngressNotConfigured about serving

[ReToCode]

Everything seems well at first, then I deployed a demon

I don't think we can help you much here. It seems like something is off with your set-up / and especially the networking configuration (as the webhook is there but cannot be called). Maybe check without that daemon again? Or check what that does and how it interferes with Knative.

[springCozyRock]

Everything seems well at first, then I deployed a demon

I don't think we can help you much here. It seems like something is off with your set-up / and especially the networking configuration (as the webhook is there but cannot be called). Maybe check without that daemon again? Or check what that does and how it interferes with Knative.

hi @ReToCode , thank you very much for your reply, since I am alone to fix these as a student. I decided to redeploy knative after getting your info. And something weird happened before I test the helloworld-go demo.

So, I deployed Knative-serving components & Kourier, totally following the official docs. So far so well.

Then I tried to configure DNS by Magic DNS(sslip.io), but the default-domain-xxxx STAUS remained as Completed, detailed info are as follows.

ubuntu@kmaster:~$ sudo kubectl get pods -n knative-serving
NAME                                      READY   STATUS      RESTARTS   AGE
webhook-56bf849884-8v2qj                  1/1     Running     0          28m
controller-ddf58dbc6-tbrnm                1/1     Running     0          28m
autoscaler-78ddd8548b-vf8bq               1/1     Running     0          28m
activator-56fb6f44f6-pn66l                1/1     Running     0          28m
net-kourier-controller-758c787975-6d829   1/1     Running     0          26m
default-domain-kj79t                      0/1     Completed   0          20m

Then I logs this weird pod, but I can not get a clear clue

ubuntu@kmaster:~$ sudo kubectl logs default-domain-kj79t -n knative-serving
W0415 12:13:41.186014       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
{"level":"info","ts":1713183231.2954903,"logger":"fallback.default-domain","caller":"default-domain/main.go:230","msg":"Updated default domain to: 192.168.70.5.sslip.io"}

could you kindly help me?

[ReToCode]

I don't know why that job did fail, but you can actually also just set the domain with kubectl:

kubectl patch configmap/config-domain \
  --namespace knative-serving \
  --type merge \
  --patch '{"data":{"192.168.70.5.sslip.io":""}}'

That should help make your set-up work.

[springCozyRock]

Thank you very much. All these issues came from missing 2 steps when setting up kourier. I am so stupid. Now everything works well. Thanks again!