Introduction of Knative, Riff and Pivotal Function as a Service. Presented at Cloud Foundry Meetup Singapore.

1. © Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0
Jay Lee(jaylee@pivotal.io)
Advisory Platform Architect
Knative And
Pivotal Function As A Service

3. Serverless is telling us
“there’s even more you don’t
care about”.
Dave Syer
Serverless Spring
S1P 2017

5. Serverless platform features in
a nutshell
1. Less Code
Function-invoker model
2. Auto Build
buildpacks, revisions, CI/CD
3. Auto Run
0-N autoscaling
4. Auto Wire
Event channels & Routes

6. The promise of Serverless
Narrowly-scoped units of code, and built-in
event integration, contribute to software
development efficiencies.
Code which doesn't consume resources
when idle can provide significant resource
efficiencies.
Applying serverless to distributed computing
brings operational efficiencies based on
automated event-based scheduling and self-
scaling.

7. Q: What is Knative?
Set of Building Blocks to construct
FaaS on top of Kubernetes and
Istio.

8. DeWitt Clinton, Google Cloud
"Pivotal has been instrumental in the design and
delivery of Knative.
We appreciate this partnership, and are excited that
Pivotal plans on commercializing Knative
components on Kubernetes with their Pivotal
Function Service.”

9. Knative Persona

10. Q: What does Knative do?
Source-to-container, by plug-ins (e.g. Cloud Foundry,
Dockerfile) - Deploying new (routable) function to
Kubernetes
Scale with Events (0 to 1, 1 to N, N to 0)
Roll out upgrades to functions, or perform a rollback
Trigger functions when called via HTTP requests; in
progress towards supporting gRPC as well

11. Q: What makes up Knative?
• Build - source-to-container build orchestration
• Eventing - management and delivery of events
• Serving - request-driven compute that can
scale to zero

12. Build – Source to Container
Runs on Kubernetes Cluster and implemented by CRD
Builds sources to container image that you can then run on
Knative
Build happens on Cluster, No need Docker locally
Build Templates including Jib(Google), Buildpack(Cloud
Foundry), Bazel, Kaniko, etc.

13. Build – ex. jib
apiVersion: build.knative.dev/v1alpha1
kind: Build
metadata:
name: jib-boot
spec:
serviceAccountName: knative-build
source:
git:
url: https://github.com/eggboy/jib-boot.git
revision: master
steps:
- name: build-and-push
image: gcr.io/cloud-builders/mvn
args: ["compile", "jib:build", "-Dimage=gcr.io/fe-chlee/hello-jib"]
<plugin>
<groupId>com.google.cloud.tools</groupId>
<artifactId>jib-maven-plugin</artifactId>
<version>1.0.0-rc1</version>
</plugin>

14. Build – ex. buildpack
$ pack build --path . eggboy/sm-pack:0.1
Using default builder image packs/samples:v3alpha2
Pulling builder image packs/samples:v3alpha2 (use --no-pull flag to skip this step)
Selected run image packs/run:v3alpha2 from stack io.buildpacks.stacks.bionic
Pulling run image packs/run:v3alpha2 (use --no-pull flag to skip this step)
Using cache volume pack-cache-abccc4f86c196003bee5e4779016679f
===> DETECTING
[detector] 2019/01/14 02:18:25 Trying group of 1...
[detector] 2019/01/14 02:18:25 ======== Results ========
[detector] 2019/01/14 02:18:25 Sample Node.js Buildpack: fail
[detector] 2019/01/14 02:18:25 Trying group of 1...
[detector] 2019/01/14 02:18:25 ======== Results ========
[detector] 2019/01/14 02:18:25 Sample Java Buildpack: pass
===> ANALYZING
Reading information from previous image for possible re-use
[analyzer] 2019/01/14 02:18:26 WARNING: image 'eggboy/sm-pack:0.1' not found or requires authentication to
access
[analyzer] 2019/01/14 02:18:26 removing cached layers for buildpack 'config' not in group
===> BUILDING
[builder] + env_dir=/platform/env
[builder] + layers_dir=/workspace/io.buildpacks.samples.java
[builder] + plan_path=/tmp/plan.091539468/io.buildpacks.samples.java/plan.toml
[builder] + jdk_url=https://cdn.azul.com/zulu/bin/zulu8.28.0.1-jdk8.0.163-linux_x64.tar.gz
[builder] + jdk_version=1.8.0_163
[builder] + maven_url=https://apache.org/dist/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz
[builder] + maven_version=3.5.4

15. Build Demo

16. Q: What makes up the Serving project?
There are four primary resources: service, configuration, revision, and
route.

17. Q: What makes up the Serving project?
There are four primary resources: service, configuration, revision, and
route.

18. Serving Demo

19. Knative Eventing
Connects workloads and event sources over broker-backed
pub-sub channels
KubernetesEventSource
GitHubSource
GCPPubSubSource
AWSSqsSource
ContainerSource

20. Eventing Demo

21. Invokers
Functions
Traffic
Routing
(Autoscaling)
Functions
Apps
Containers
Configurations
Revisions
Container
Builds
Channels
Subscriptions
Buildpacks
Eventing
Pivotal
contributions
https://github.com/knative
Focus Area For Pivotal
Delivering a unified vision for a serverless platform on Kubernetes.

24. Q: What is Riff?
riff is designed for running
Functions in response to Events.

26. December 6, 2017 at SpringOne
2
riff provides developers
with a service for
executing Functions in
response to Events.
Features
o Kubernetes-native
o polyglot
o event streaming

27. Google Cloud Next - July 2018
Community-driven
ecosystem of
Sources,
Channels,
Functions,
Invokers,
BuildTemplates,
etc.
Kubernetes
BuildTemplates
Channels
CLI
Invokers
CLI
Invokers
Build
Topics
Betting our Faas Future on Knative

28. Layering riff and Knative

29. • riff’s build template uses a builder to:
• compile source code
• add a runtime
• add an invoker
• builder is composed of multiple buildpacks:
• OpenJDK and NodeJS buildpacks
• Maven/Gradle buildpack for JVM functions
• NPM buildpack for node.js functions
• riff buildpack adds a suitable invoker
• final build step creates an image
riff Buildpacks and Invokers
29

30. • Install and set-up commands:
• system: install & uninstall riff and Knative
• namespace: initialise namespaces
• Function/service commands:
• function: create & update functions
• service: create, update, invoke, get status, list, & delete services
• Eventing commands:
• channel: create, list, & delete channels
• subscription: create, list, & delete subscriptions
riff Command Line Interface
30

31. Betting our FaaS future on Knative
Community-driven
ecosystem of
EventSources,
Buses,
Invokers,
BuildTemplates,
etc.
Kubernetes
VALUE LINE
BuildTemplates
Channels
CLI/UI
Invokers
VALUE LINE

32. Functions & Invokers
Developers are responsible
only for the business logic.
Dependencies in base image
layers can be managed
independently.
simpler
more secure
more efficient
Function Code
Function Layer
Invoker Layer
Dependency Layers
Base Image
Function
Container

33. Pivotal's commercially supported
distribution of riff + Knative.
Alpha release announced December 7, 2018

34. PFS Demo

35. Pivotal Application
Service (PAS)
Pivotal Container
Service (PKS)
Pivotal Function
Service (PFS)
Unit = Container
Running in Multiple Env
Open Source, Non-HTTP
Unit = Application
Web-facing App
Code First, HTTP
Unit = Function
Extending App with Event,
Lightweight ETL
Events, Fully-managed env

36. Transforming How The World Builds Software
© Copyright 2017 Pivotal Software, Inc. All rights Reserved.