4 ms·

Thanks to everyone who played a part of this! The Google team is also watching this thread. Happy to answer any questions people have.

by dewitt 8y ago

dcosson 8y ago
This looks really cool, I'll definitely be looking into it more closely when I get a chance. Obviously this is a conflict of interest for Google, but just curious if you know of any plans in the works for being able to run this on AWS EKS? It's the obvious omission from the list of supported clouds on the installation page[0]. [0] https://github.com/knative/docs/tree/master/install https://github.com/knative/docs/tree/master/install
- markusthoemmes 8y ago
  If AWS EKS gives you access to kubectl or similar, it is probably trivial to setup. There shouldn't be any obvious roadblocks. Will be a great contribution to add to the guides!
  - csears 8y ago
    AWS EKS definitely does support kubectl, but requires the aws-iam-authenticator (formerly Heptio) to integrate with AWS IAM. Docs here: https://docs.aws.amazon.com/eks/latest/userguide/configure-kubectl.html https://docs.aws.amazon.com/eks/latest/userguide/configure-k...
- jacques_chester 8y ago
  I think PRs would be gladly accepted. But, in general, it should work fine with any conforming Kubernetes system.
- dewitt 8y ago
  I'd love to see a PR that documents Knative on EKS!
- empath75 8y ago
  There seems to be a problem with istio working on EKS, actually -- i'm getting a timeout to the sidecar injector: same issue as this: https://github.com/istio/old_issues_repo/issues/271 https://github.com/istio/old_issues_repo/issues/271
jacques_chester 8y ago
It's been a really interesting experience. Google's position as a catalyst made this level of cooperation possible.
- dewitt 8y ago
  Huge thanks to Pivotal for being an amazing development partner. Pivotal's deep experience with enterprise customers and developing products like riff brought real-world knowledge and technical leadership to Knative early on. We're super grateful for the opportunity to have worked together on this!
otterley 8y ago
Can we see a design document/theory of operations, please? It’s difficult to evaluate this effort without understanding exactly what it is - namely, the constituent components, their respective functions, how they work and relate to one another, etc. Just a comment here about this in general - given all the resources at Google’s disposal, I’m perplexed as to why we don’t see world-class (or even at least halfway decent) documentation being shipped along with the product at first release. As a community I think we need to demand higher standards in this area. If GNU can do it, Google certainly can.
- jhabdas 8y ago
  So you found the Zipkin UI link in the Microsoft GitHub docs already?
- dewitt 8y ago
  Is this something like what you're looking for? https://github.com/knative/serving/blob/master/docs/spec/overview.md https://github.com/knative/serving/blob/master/docs/spec/ove... Or a little higher-level: https://docs.google.com/presentation/d/1CbwVC7W2JaSxRyltU8CS1bIsrIXu1RrZqvnlMlDaaJE/edit# https://docs.google.com/presentation/d/1CbwVC7W2JaSxRyltU8CS... There are a lot of technical docs in the individual repositories. You can get started, for example, with the serving docs under: https://github.com/knative/serving/tree/master/docs https://github.com/knative/serving/tree/master/docs Same for the other repos, like build and eventing. Thanks for asking!
  - otterley 8y ago
    Not really, I'm afraid. Resource descriptions don't constitute a theory of operations, and the higher-level document you linked to is not public. By "theory of operations," I mean a design document, often but not always created before a line of code is written, that describes in plain English what is to be built (or, what was built). It often discusses things like: * What problems are being solved? * What attempts have already been made to solve the problem? * How does it work? How do the components interrelate? How does one operate it, especially at scale? * How does this solution solve the problems better than the alternatives? There are lots of great examples out there. I like to point to Consul[1] as a textbook example of fantastic documentation, and it's been there since day 1. Google would do well to follow Hashicorp's and GNU's lead. [1] https://www.consul.io https://www.consul.io
pas 8y ago
How serving works? Is it possible to use it with kong? (Or other ingress controllers?)

Thanks to everyone who played a part of this! The Google team is also watching this thread. Happy to answer any questions people have.

by dewitt 8y ago

Thanks to everyone who played a part of this! The Google team is also watching this thread. Happy to answer any questions people have.

dcosson 8y ago

This looks really cool, I'll definitely be looking into it more closely when I get a chance. Obviously this is a conflict of interest for Google, but just curious if you know of any plans in the works for being able to run this on AWS EKS? It's the obvious omission from the list of supported clouds on the installation page[0]. [0] https://github.com/knative/docs/tree/master/install https://github.com/knative/docs/tree/master/install

markusthoemmes 8y ago
If AWS EKS gives you access to kubectl or similar, it is probably trivial to setup. There shouldn't be any obvious roadblocks. Will be a great contribution to add to the guides!
- csears 8y ago
  AWS EKS definitely does support kubectl, but requires the aws-iam-authenticator (formerly Heptio) to integrate with AWS IAM. Docs here: https://docs.aws.amazon.com/eks/latest/userguide/configure-kubectl.html https://docs.aws.amazon.com/eks/latest/userguide/configure-k...
jacques_chester 8y ago
I think PRs would be gladly accepted. But, in general, it should work fine with any conforming Kubernetes system.
dewitt 8y ago
I'd love to see a PR that documents Knative on EKS!
empath75 8y ago
There seems to be a problem with istio working on EKS, actually -- i'm getting a timeout to the sidecar injector: same issue as this: https://github.com/istio/old_issues_repo/issues/271 https://github.com/istio/old_issues_repo/issues/271

jacques_chester 8y ago

It's been a really interesting experience. Google's position as a catalyst made this level of cooperation possible.

dewitt 8y ago
Huge thanks to Pivotal for being an amazing development partner. Pivotal's deep experience with enterprise customers and developing products like riff brought real-world knowledge and technical leadership to Knative early on. We're super grateful for the opportunity to have worked together on this!

otterley 8y ago

Can we see a design document/theory of operations, please? It’s difficult to evaluate this effort without understanding exactly what it is - namely, the constituent components, their respective functions, how they work and relate to one another, etc. Just a comment here about this in general - given all the resources at Google’s disposal, I’m perplexed as to why we don’t see world-class (or even at least halfway decent) documentation being shipped along with the product at first release. As a community I think we need to demand higher standards in this area. If GNU can do it, Google certainly can.

jhabdas 8y ago
So you found the Zipkin UI link in the Microsoft GitHub docs already?
dewitt 8y ago
Is this something like what you're looking for? https://github.com/knative/serving/blob/master/docs/spec/overview.md https://github.com/knative/serving/blob/master/docs/spec/ove... Or a little higher-level: https://docs.google.com/presentation/d/1CbwVC7W2JaSxRyltU8CS1bIsrIXu1RrZqvnlMlDaaJE/edit# https://docs.google.com/presentation/d/1CbwVC7W2JaSxRyltU8CS... There are a lot of technical docs in the individual repositories. You can get started, for example, with the serving docs under: https://github.com/knative/serving/tree/master/docs https://github.com/knative/serving/tree/master/docs Same for the other repos, like build and eventing. Thanks for asking!
- otterley 8y ago
  Not really, I'm afraid. Resource descriptions don't constitute a theory of operations, and the higher-level document you linked to is not public. By "theory of operations," I mean a design document, often but not always created before a line of code is written, that describes in plain English what is to be built (or, what was built). It often discusses things like: * What problems are being solved? * What attempts have already been made to solve the problem? * How does it work? How do the components interrelate? How does one operate it, especially at scale? * How does this solution solve the problems better than the alternatives? There are lots of great examples out there. I like to point to Consul[1] as a textbook example of fantastic documentation, and it's been there since day 1. Google would do well to follow Hashicorp's and GNU's lead. [1] https://www.consul.io https://www.consul.io

pas 8y ago

How serving works? Is it possible to use it with kong? (Or other ingress controllers?)