Earlier quoted context omitted.
it's a PaaS .. heroku for k8s https://github.com/knative/docs/tree/master/serving/samples/...
Interesting. I had to learn Kubernetes very recently and this seems to simplify a lot of the boilerplate needed to have an app running. One the most grating part for me was having the ingress run with a proper SSL certificate with the right handshakes though (had to install a nginx controller just for that). That’s the kind of things that everyone will go through, and is solved in one click on heroku. Yet it seems to…
https://github.com/Kong/kubernetes-ingress-controller
Knative uses parts of Istio for servign and TLS/SSL setup: https://github.com/knative/docs/blob/master/serving/using-an...
It's a bit funny that knative serving is so complicated I have still no idea what they use under the many layers of abstraction (probably something hacked together in go), and I don't understand why don't they use a generic configurable ingress component.