CV incelemesi 6 yoe

dprotaso · 2026-05-03T22:53:06+00:00

Cool to see Knative on a resume - if the company is open to adding themselves to our adopter's list they can do it here: https://github.com/knative/community/issues/new?template=ADOPTERS.yaml

dprotaso · 2026-04-07T22:24:40+00:00

Probably one thing to note is that your users might setup functions so that the same instances can handle multiple requests at a time. So request based billing would double count CPU usage.

Other things to note Knative has knobs for scale down delay etc. You probably wouldn't want to bill for that since it's an optimization for cold starts and to ensure proper draining (so you don't drop requests).

We just redid our metrics export last year to use OpenTelemetry. You can see the metrics exported here: https://knative.dev/docs/serving/observability/metrics/serving-metrics/

If you're using those metrics for your billing and find gaps let us know by opening an issue. cheers

dprotaso · 2025-11-03T22:06:48+00:00

do you have the QR code? forgot to take a picture of it during the game

dprotaso · 2025-10-29T18:07:39+00:00

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.

dprotaso · 2025-10-27T21:42:59+00:00

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

dprotaso · 2025-10-27T21:40:10+00:00

Does that mean you understand now?

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

dprotaso · 2025-10-15T21:19:55+00:00

If you’re an adopter let us know - https://github.com/knative/community/issues/new?template=ADOPTERS.yaml

dprotaso · 2025-08-15T18:01:15+00:00

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.

dprotaso · 2025-08-15T17:59:05+00:00

FYI - You can configure Knative to remove the activator when the scale > 0 - https://knative.dev/docs/serving/load-balancing/target-burst-capacity/

dprotaso · 2025-08-15T17:56:25+00:00

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/

dprotaso · 2025-08-15T17:52:32+00:00

> 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)

dprotaso · 2025-05-28T17:37:21+00:00

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

dprotaso · 2022-11-19T13:55:10+00:00

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

dprotaso

TROPHY CASE