search

fonk-apps / fonk-examples

Web application examples using FaaS/Object Storage/NoSQL on K8S
38 stars 6 forks source link

Consistent Kubeless ingress fix instructions #19

Closed nerdguru closed 5 years ago

nerdguru commented 5 years ago

Now that @juliogomez, @vallard, and I all have encountered different ways of fixing the Kubeless ingress workarounds given different scenarios, it seems like a good idea to have them all in one place instead of spread across different language implementations of Guestbook. We'll run into this as part of ToDos as well.

nerdguru commented 5 years ago

Early returns here are that the workaround that @vallard has in the Golang version of his serverless.yml instructions (but not the Python ones) works better for CCP than what I documented. Namely, if you hard code the hostname in serverless.yml:

provider:
  name: kubeless
  hostname: 10.10.20.209.xip.io

and deploy, the ingress gets set correctly when deploying:

$ kubectl get ingress
NAME        HOSTS                 ADDRESS        PORTS     AGE
guestbook   10.10.20.209.xip.io   10.10.20.102   80        21m

So, no need to manually edit the ingress like I had before. This worked for @vallard's bare metal cluster, I'll next try it on GKE. In the CCP case, it still required looking up the main CCP ingress, but at least if you set it in the serverless.yml that simplifies the instructions and doesn't have to be redone for every deployment.

nerdguru commented 5 years ago

Hmm, on GKE with K8S 1.9.7 and Kubeless v1.0.0-alpha.8, a deployment with the Serverless framework nets the following ingress:

o$ kubectl get ingress
NAME        HOSTS                   ADDRESS   PORTS     AGE
guestbook   35.203.171.231.xip.io             80        5m

Soooo, no address. Weird. Let me try an earlier Kubeless version I've had success with before.

nerdguru commented 5 years ago

Same thing on v1.0.0-alpha.6, which I previously had success with. This will take some digging, tomorrow.