91–100 of 168 posts
I kinda have a hard time understanding what it is ... is it kinda a 'glue' layer between Kubernetes and istio ? Can somebody give us a 2 sentences explanation? please and thank you
This is a way to deploy and manage a stateless web application ("function") without needing to get into a bunch of low-level details, and get closer to pay-for-what-you-use.
How though, won't you need a Kubernetes cluster running?
I kinda have a hard time understanding what it is ... is it kinda a 'glue' layer between Kubernetes and istio ? Can somebody give us a 2 sentences explanation? please and thank you
This is a way to deploy and manage a stateless web application ("function") without needing to get into a bunch of low-level details, and get closer to pay-for-what-you-use.
How do you pronounce it? Native with a silent K? (like "knave" or "knee") Kay-Native? Kuh-Native?
Joining in, Markus from IBM and OpenWhisk. Been involved with knative for quite some time now as well. Happy to answer any questions that might arise as well. Answers might be biased and opinions are my own. See IBM's statement: https://www.ibm.com/blogs/cloud-computing/2018/07/24/ibm-clo...
@markusthoemmes could you kindly comment on how OpenWhisk Knative interact or live together or side by side
In technical terms, OpenWhisk's invoker system could be replaced by knative, keeping the API/Controller bits stable to still support the notion of actions/triggers/rules/sequences/compositions you name it.
Earlier quoted context omitted.
You have source code. You want a simple way to turn it into running functions and apps, with eventing support, with clever routing and rollout capabilities, without lifting a finger. It's an abstraction layer being developed above both of Kubernetes and Istio.
You still need a Kubernetes cluster running though, right?
Joining in, Markus from IBM and OpenWhisk. Been involved with knative for quite some time now as well. Happy to answer any questions that might arise as well. Answers might be biased and opinions are my own. See IBM's statement: https://www.ibm.com/blogs/cloud-computing/2018/07/24/ibm-clo...
Earlier quoted context omitted.
You have source code. You want a simple way to turn it into running functions and apps, with eventing support, with clever routing and rollout capabilities, without lifting a finger. It's an abstraction layer being developed above both of Kubernetes and Istio.
You still need a Kubernetes cluster running though, right?
Earlier quoted context omitted.
You basically have a git repo that contains your business logic implemented as 'functions' and some configuration : knative will build, containerize, deploy, and glue/route those functions for you to make it a full fledged app. it will also take care of load balancing/scaling etc. So all you need really is focus on you business logic code and write some config for knative ... well this is at least the vision
Why isn't a polished version of this the blurb?
Earlier quoted context omitted.
You basically have a git repo that contains your business logic implemented as 'functions' and some configuration : knative will build, containerize, deploy, and glue/route those functions for you to make it a full fledged app. it will also take care of load balancing/scaling etc. So all you need really is focus on you business logic code and write some config for knative ... well this is at least the vision
How would this compare to something like serverless.com?
Earlier quoted context omitted.
You still need a Kubernetes cluster running though, right?
This is what I am trying to figure out too. Is Knative standalone, or is it running inside your K8 cluster, or do you build a K8 cluster and run this in it exclusively?