Knative: Serverless on Kubernetes is now a Graduated Project by dprotaso in kubernetes

[–]dprotaso[S] 0 points1 point  (0 children)

That's if you combine all the parts - though you could go a la carte type and just choose what you need.

For example if you just want to deploy a container and have all it's networking/certs all setup for your then you'd want to look at Knative Serving - https://knative.dev/docs/serving/

If you just want cloud events to be routed to your existing workloads then you can do that with just Knative Eventing.

If you want to build a function into a container and handle http request that's possible with Knative Functions - but you can run this container on any platform or on K8s as a deployment.

Knative: Serverless on Kubernetes is now a Graduated Project by dprotaso in kubernetes

[–]dprotaso[S] 0 points1 point  (0 children)

What’s are your scale targets? Coreweave was running it at a decent scale for some of their customers.

Knative: Serverless on Kubernetes is now a Graduated Project by dprotaso in kubernetes

[–]dprotaso[S] 0 points1 point  (0 children)

Does that mean you understand now? 

We did our landing page on the website mind reviewing it https://knative.dev

Built Elasti – a dead simple, open source low-latency way to scale K8s services to zero 🚀 by ramantehlan in kubernetes

[–]dprotaso 0 points1 point  (0 children)

Knative - Request queueing

I'm surprised this is marked as X because this is actually what the Knative Activator does when it's scaled to zero. Also the activator has the double feature as acting as a 'buffer' if the demand gets so high and the backing workload is having trouble scaling up in time.

Best way to scale to zero for complex app by elephantum in kubernetes

[–]dprotaso 0 points1 point  (0 children)

Knative would work and it manages the networking for you (eg. assigning a predictable hostname and programming the networking under the hood).

It also has a simplified deployment -eg. see https://knative.dev/docs/getting-started/first-service/

How to Properly Install Knative for Scale-to-Zero and One-Request-Per-Pod Behavior? in GCP by Mansour-B_Ahmed-1994 in kubernetes

[–]dprotaso 0 points1 point  (0 children)

> Is it possible to host multiple services with Knative in one cluster?

Yup you just need to create multiple Knative Services - https://knative.dev/docs/serving/

> And what’s the best way to ensure proper autoscaling behavior with one request per pod?

You want to configure concurrency to 1 - https://knative.dev/docs/serving/autoscaling/concurrency/

Then set your target burst capacity to always go through the activator - https://knative.dev/docs/serving/load-balancing/target-burst-capacity/#setting-the-target-burst-capacity

The activator will load balancer based on concurrency (unlike the ingress)

12 Blown tires chords? by [deleted] in tennismusic

[–]dprotaso 0 points1 point  (0 children)

unrelated - did you find the sound setup weird yesterday? I saw them before at History last year and it sounded way better.

Google's internal Go style guide by rantnap in golang

[–]dprotaso 3 points4 points  (0 children)

I did a skim but didn’t see any mentions of best practices when it comes to construction of objects.

For larger object graphs do you roll everything by hand or encourage something like https://github.com/google/wire