home.social

#knative — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #knative, aggregated by home.social.

  1. It's Linux Foundation Mentorship Term 1 time. If you know anyone who wants to do a paid mentorship working on open source projects please send them to these links to apply?

    Improve Cluster API in Headlamp, github.com/headlamp-k8s/plugin

    Volcano in Headlamp, github.com/kubernetes-sigs/hea

    Improve Knative in Headlamp, github.com/headlamp-k8s/plugin

    Strimzi in Headlamp, github.com/headlamp-k8s/plugin

    Kubeflow in Headlamp, github.com/kubernetes-sigs/hea

    , ,

  2. The problem of having knowledge is knowing when to use. 😅

    Case in point, right now thinking either activation socket or on for home stuff. 🫠 The goal here is HTTP requests turn on service, does some stuff, and gracefully drains down on idle.

  3. Well as of today I’m officially laid off...

    If anyone is looking for a Senior Platform Engineer with a lot of #Kubernetes, #Crossplane, #Terraform, and #Knative, please send them my way! 💜

    #GetFediHired #FediHired #FediHire

  4. Data center emissions are surging. Every millisecond counts. Can native #Java with #Knative tilt the balance? Marius Stein & Vishal Shanbhag explore how new builds bring old stacks into a greener future.

    The full story: javapro.io/2025/06/11/greener-

    #GraalVM #Cloud #JVM @graalvm

  5. Somehow I can't get #knative to work properly with contour ontop of #cilium as cni.
    Always routes itself into some kind of loop holes.

  6. Currently trying to get #knative in my homelab going. Stumbling into issues with getting kourier running. Somehow the envoy keep crashing due to now reachable upstreams. Using the knative operator for getting the knative-serving up an running. Does someone else ran into the same issue?

    config-wise its pretty easy currently
    ```
    apiVersion: operator.knative.dev/v1beta1
    kind: KnativeServing
    metadata:
    name: knative-serving
    spec:
    ingress:
    kourier:
    enabled: true
    service-type: "ClusterIP"
    ```

    tags for visibility: #kubernetes #knative #KnativeServing

  7. Currently trying to get #knative in my homelab going. Stumbling into issues with getting kourier running. Somehow the envoy keep crashing due to now reachable upstreams. Using the knative operator for getting the knative-serving up an running. Does someone else ran into the same issue?

    config-wise its pretty easy currently
    ```
    apiVersion: operator.knative.dev/v1beta1
    kind: KnativeServing
    metadata:
    name: knative-serving
    spec:
    ingress:
    kourier:
    enabled: true
    service-type: "ClusterIP"
    ```

    tags for visibility: #kubernetes #knative #KnativeServing

  8. Currently trying to get in my homelab going. Stumbling into issues with getting kourier running. Somehow the envoy keep crashing due to now reachable upstreams. Using the knative operator for getting the knative-serving up an running. Does someone else ran into the same issue?

    config-wise its pretty easy currently
    ```
    apiVersion: operator.knative.dev/v1beta1
    kind: KnativeServing
    metadata:
    name: knative-serving
    spec:
    ingress:
    kourier:
    enabled: true
    service-type: "ClusterIP"
    ```

    tags for visibility:

  9. Currently trying to get #knative in my homelab going. Stumbling into issues with getting kourier running. Somehow the envoy keep crashing due to now reachable upstreams. Using the knative operator for getting the knative-serving up an running. Does someone else ran into the same issue?

    config-wise its pretty easy currently
    ```
    apiVersion: operator.knative.dev/v1beta1
    kind: KnativeServing
    metadata:
    name: knative-serving
    spec:
    ingress:
    kourier:
    enabled: true
    service-type: "ClusterIP"
    ```

    tags for visibility: #kubernetes #knative #KnativeServing

  10. Currently trying to get #knative in my homelab going. Stumbling into issues with getting kourier running. Somehow the envoy keep crashing due to now reachable upstreams. Using the knative operator for getting the knative-serving up an running. Does someone else ran into the same issue?

    config-wise its pretty easy currently
    ```
    apiVersion: operator.knative.dev/v1beta1
    kind: KnativeServing
    metadata:
    name: knative-serving
    spec:
    ingress:
    kourier:
    enabled: true
    service-type: "ClusterIP"
    ```

    tags for visibility: #kubernetes #knative #KnativeServing

  11. An interesting talk here at #KubeCon by @terrytangyuan from #RedHat and Adam Tetelman from #NVIDIA on the many pitfalls of using LLMs in production.

    #KServe and #Knative come to the rescue of many Day 2 problems, but there's still a lot to do.

    And, as Adam Teleman said so well, this year's KubeCon could easily be called RAGCon, given how many talks there are about #RAG 😀

    #KubeCon24 #AI #LLM

  12. Dávid Šimanský talks about an event-driven approach in moderating offensive words in discussions and comments using #Kafka and #Knative.

    I use Kafka, but the cloud world is still unexplored for me in terms of technology.

    #DevConf_CZ

  13. What a way to finish my week! I just finished talking with my friends from @[email protected] @[email protected] and @[email protected] about all things #kubernetes #knative #dapr #tekton #kcp #kubebind and what is coming in 2023!! 🤯🤯

  14. Playing around with ... Added an helloworld app using instead of the default ... github.com/timvw/knative-rust-

  15. open specification has reached graduation at the 👏
    The spec has been adopted by I/O Events, EventBridge, Event Grid, Eventarc, Code Engine, the European Commission and more.
    And of course it's been adopted by CNCF projects, such as , , , and .
    The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
    cncf.io/announcements/2024/01/

  16. @samir what's the use case? If low startup latency on #kubernetes is required then I'm thinking you would might want to look into #FaaS options like #knative, where you can keep a warm worker pod ready and preemptively scale up more pods based on demand.

  17. #JCON2023 🎥 by Timo Salm: Going #Serverless with #SpringBoot3

    He´ll teach you how to implement your serverless applications and compile them to GraalVM native images for almost instant startup times and reduced memory consumption with Spring Boot 3...

    Watch now: youtube.com/watch?v=B3CiGWASRt
    #Knative

  18. #JCON2023 🎥 by Timo Salm: Going #Serverless with #SpringBoot3

    He´ll teach you how to implement your serverless applications and compile them to GraalVM native images for almost instant startup times and reduced memory consumption with Spring Boot 3...

    Watch now: youtube.com/watch?v=B3CiGWASRt
    #Knative

  19. New 🎥 online! Kevin Dubois at #JCON2023: Writing #Serverless Applications with #Quarkus and #Knative

    He´ll explain & demonstrate how simple it is to design & implement these next-generation application components...

    Watch now: youtube.com/watch?v=H9WtcoDPdz
    #JAVAPRO #JCON #Kubernetes

  20. New 🎥 online! Kevin Dubois at #JCON2023: Writing #Serverless Applications with #Quarkus and #Knative

    He´ll explain & demonstrate how simple it is to design & implement these next-generation application components...

    Watch now: youtube.com/watch?v=H9WtcoDPdz
    #JAVAPRO #JCON #Kubernetes

  21. Yesterday, we released vscode-openshift 1.8.0. The main feature is creating #Knative serverless functions from templates in custom template repositories. We also improved the documentation and removed many unused dependencies. See the full changelog here: github.com/redhat-developer/vs

    #vscode #openshift #kubernetes

  22. 🛫BRU-GVA 🚆 Lausanne for a customer event. Joining a panel tomorrow about developer experience, followed by a wine tasting event in a Swiss vineyard🍷. And the next morning a session about #Openshift Serverless, #Knative and.. #Quarkus of course 😏

  23. #CloudEvents open specification has reached graduation at the #CNCF 👏
    The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
    And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
    The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
    cncf.io/announcements/2024/01/
    #opensource #cloudnative

  24. #CloudEvents open specification has reached graduation at the #CNCF 👏
    The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
    And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
    The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
    cncf.io/announcements/2024/01/
    #opensource #cloudnative

  25. #CloudEvents open specification has reached graduation at the #CNCF 👏
    The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
    And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
    The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
    cncf.io/announcements/2024/01/
    #opensource #cloudnative

  26. #CloudEvents open specification has reached graduation at the #CNCF 👏
    The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
    And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
    The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
    cncf.io/announcements/2024/01/
    #opensource #cloudnative

  27. @jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
    Slightly off topic, so not about functions but just about knative eventing and serving:
    what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
    Is that a resolved issue nowadays?

  28. @jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
    Slightly off topic, so not about functions but just about knative eventing and serving:
    what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
    Is that a resolved issue nowadays?

  29. @jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
    Slightly off topic, so not about functions but just about knative eventing and serving:
    what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
    Is that a resolved issue nowadays?

  30. @jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
    Slightly off topic, so not about functions but just about knative eventing and serving:
    what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
    Is that a resolved issue nowadays?

  31. @jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
    Slightly off topic, so not about functions but just about knative eventing and serving:
    what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
    Is that a resolved issue nowadays?

  32. heise-Angebot: Mit dem Cloud Native Day die Cloud-Transformation meistern

    Beim fünften Thementag von Continuous Delivery und ContainerConf dreht sich alles um Tools, Techniken und Plattformkonzepte für Cloud-native Betriebsmodelle.
    Mit dem Cloud Native Day die Cloud-Transformation meistern
  33. For @fedora users of the following COPRs:

    - mroche/golang-test
    - mroche/cloud-native-utilities

    With Fedora 36 now EOL, I will stop building against the platform. Please migrate to Fedora 37 or Fedora 38 for continued releases and support!

  34. Played with #Knative on #Kubernetes today, it's pretty nifty

    I used `oha` to stress-test a basic health-check service, and it's cool that #KnativeServing can scale from 0 service pods, to 1 pod, and eventually up to 10 pods, all without dropping any requests (the requests are queued if there aren't enough service pods)

    It's like having my very own AWS Lambda at home (and honestly easier for me to use than AWS Lambda)

    These are the results for running `oha -c 1000 -z 30sec` against my cluster which has 3x Raspberry Pi 4B nodes (all nodes are control-plane nodes but with pod-scheduling enabled):

    ```
    Summary:
    Success rate: 1.0000
    Total: 30.0055 secs
    Slowest: 6.2945 secs
    Fastest: 0.0264 secs
    Average: 0.5445 secs
    Requests/sec: 1793.4723

    Total data: 0 B
    Size/request: 0 B
    Size/sec: 0 B

    Response time histogram:
    0.146 [2198] |■■■■
    0.292 [10205] |■■■■■■■■■■■■■■■■■■■■■■
    0.438 [14373] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
    0.584 [9585] |■■■■■■■■■■■■■■■■■■■■■
    0.731 [10099] |■■■■■■■■■■■■■■■■■■■■■■
    0.877 [4081] |■■■■■■■■■
    1.023 [1561] |■■■
    1.169 [495] |■
    1.315 [257] |
    1.461 [140] |
    1.607 [820] |■
    ```

  35. Played with #Knative on #Kubernetes today, it's pretty nifty

    I used `oha` to stress-test a basic health-check service, and it's cool that #KnativeServing can scale from 0 service pods, to 1 pod, and eventually up to 10 pods, all without dropping any requests (the requests are queued if there aren't enough service pods)

    It's like having my very own AWS Lambda at home (and honestly easier for me to use than AWS Lambda)

    These are the results for running `oha -c 1000 -z 30sec` against my cluster which has 3x Raspberry Pi 4B nodes (all nodes are control-plane nodes but with pod-scheduling enabled):

    ```
    Summary:
    Success rate: 1.0000
    Total: 30.0055 secs
    Slowest: 6.2945 secs
    Fastest: 0.0264 secs
    Average: 0.5445 secs
    Requests/sec: 1793.4723

    Total data: 0 B
    Size/request: 0 B
    Size/sec: 0 B

    Response time histogram:
    0.146 [2198] |■■■■
    0.292 [10205] |■■■■■■■■■■■■■■■■■■■■■■
    0.438 [14373] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
    0.584 [9585] |■■■■■■■■■■■■■■■■■■■■■
    0.731 [10099] |■■■■■■■■■■■■■■■■■■■■■■
    0.877 [4081] |■■■■■■■■■
    1.023 [1561] |■■■
    1.169 [495] |■
    1.315 [257] |
    1.461 [140] |
    1.607 [820] |■
    ```

  36. Honored to have been selected to speak at @RivieraDEV ! Get ready to dive deep into #ApacheCamel during my co-talk with @kevindubois and my workshop. See you there! #techtalks #speakerannouncement #integration #ApacheCamel #Quarkus #knative #Java

  37. For @fedora users of the following COPRs:

    - mroche/golang-test
    - mroche/cloud-native-utilities

    With Fedora 36 now EOL, I will stop building against the platform. Please migrate to Fedora 37 or Fedora 38 for continued releases and support!

    #fedora #eol #copr #golang #cloudnative #terraform #packer #buildpack #knative #tektoncd #helm #flyctl

  38. For @fedora users of the following COPRs:

    - mroche/golang-test
    - mroche/cloud-native-utilities

    With Fedora 36 now EOL, I will stop building against the platform. Please migrate to Fedora 37 or Fedora 38 for continued releases and support!

    #fedora #eol #copr #golang #cloudnative #terraform #packer #buildpack #knative #tektoncd #helm #flyctl

  39. For @fedora users of the following COPRs:

    - mroche/golang-test
    - mroche/cloud-native-utilities

    With Fedora 36 now EOL, I will stop building against the platform. Please migrate to Fedora 37 or Fedora 38 for continued releases and support!

    #fedora #eol #copr #golang #cloudnative #terraform #packer #buildpack #knative #tektoncd #helm #flyctl