kubernetes or knative issue? #212
-
Greetings. Total noob here but learning. Stock install of k3s and knative. using patch: The load balancer created by kourier adds two lb services in hetznet lb: tcp:80 -> 30532 - one is all green Quick firewall edit to debug. Knative install is essentially install serving crds, serving core, kourier & patch to get working. nothing about setting up potential ssl certs So trying to figure out if the http/https ports for each instances is created by kubernetes and informs the lb when knative/koutier does its thing, or is it knative that tells the instance to open that port (or installs a gateway pod with the settings). I assume potentially that there may need to be some certificate installed/shared to all causing the https port not to be open/failed config... that's the avenue I'm exploring right now, but any help would be appreciated. But could be a trap for noob users, hence the ask. Thanks !! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
OK, trying out the Istio option with a modified patch, tcp:80 - all red if it were a cert issue, then the http port would also have been green. I have found that istio installs an ingress gateway on instances that receives on those ports, not sure now if its a lb settings issue, or knative/kubernetes at this point.... continuing |
Beta Was this translation helpful? Give feedback.
-
I can't help yet because I haven't touched knative in general in many months. I will have to try it. |
Beta Was this translation helpful? Give feedback.
-
Its a knative settings issue. See the guide to install knative |
Beta Was this translation helpful? Give feedback.
Its a knative settings issue. See the guide to install knative