Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Serverless on OpenShift - Developer Experience ...

Serverless on OpenShift - Developer Experience Office Hours

What new in OpenShift 4.7 with Serverless
Release notes: https://docs.openshift.com/container-platform/4.7/serverless/serverless-release-notes.html

What’s in pipeline for OpenShift upcoming release

Red Hat Livestreaming

March 02, 2021
Tweet

More Decks by Red Hat Livestreaming

Other Decks in Technology

Transcript

  1. CONFIDENTIAL Designator What’s we are going to talk about? 2

    What new in OpenShift 4.7 with Serverless What’s in pipeline for OpenShift upcoming release
  2. CONFIDENTIAL Designator Serverless 3 “Serverless computing refers to the concept

    of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment” -- CNCF Definition, https://www.cncf.io/blog/2018/02/14/cncf-takes-first-step-towards-serverless-computing/ Serverless
  3. 5 Serving A request-driven model that serves the container with

    your application and can "scale to zero". Eventing Common infrastructure for consuming and producing events that will stimulate applications. Knative Serverless Components
  4. New features added in 4.7 Serverless 6 • Ability to

    list/create serving and eventing resources from Admin Perspective
  5. New features added in 4.7 Serverless 7 • Event Source

    Catalog: EventSources are part of catalog now to improve scalability for better user experience • Camel Connector: Added support for kamelets (Camel Connector) as part of EventSource catalog
  6. Source → Service : Channel & Subscription Serverless 10 •

    Multiple Services can consume the same event • Subscription can point to a reply channel (not shown here) • Various Channel Backends available ◦ In-Memory, Kafka, GCP PubSub, (write your own) • Drawbacks: ◦ No filtering, Service gets always all events Source Sink Sink Subscription Subscription Source Channel
  7. 12 Serverless Source → Service: Broker & Trigger Broker •

    Eventing Mesh for distributing Events • Addressed by sources as sink Broker Source Source Sink Sink Trigger filter = Trigger filter = Trigger • Filter on CloudEvent attributes (e.g. type) • Connects a Sink with Broker
  8. From Deployment to KService Serverless 16 apiVersion: apps/v1 kind: Deployment

    metadata: name: random spec: replicas: 1 selector: matchLabels: app: random template: metadata: labels: app: random spec: containers: - image: rhuss/random name: random ports: - containerPort: 8080 apiVersion: serving.knative.dev/v1 kind: Service metadata: name: random spec: replicas: 1 selector: matchLabels: app: random template: metadata: labels: app: random spec: containers: - image: rhuss/random name: random ports: - containerPort: 8080 No more K8s Service or Ingress/Route required !