10/19 Kubernetes大講堂 講師:陳大慶

1. SERVERLESS FRAMEWORK
FOR KUBERNETES
Ta-Ching Chen, Fission Contributor

2. • Ta-Ching Chen (陳大慶)
• Software Engineer/Kubernetes Education Consultant
• Blog: https://tachingchen.com/tw/
• Email: hello@tachingchen.com
HOLA!

3. Serverless computing allows you to build and run
applications and services without thinking about servers.
- AWS Lambda
What is Serverless?

4. FaaS on Cloud Provider
Vendor lock-in
FaaS environment simulation
Data privacy/protection
Execution limits & restrictions

5. How about
FaaS on Kubernetes?

6. Portability
Flexible cost model (Optimization)
DevOps pipelines integration
FaaS on Kubernetes

7. • Open source Kubernetes-native FaaS framework
• Backed by Platform9
• On-premises/Cloud support
• Wherever you can run Kubernetes, you can run Fission
• Tunable cost/performance tradeoffs
• Designed to be easy use, productive and fast
• Focus on core business logic development
Fission - Serverless Framework for Kubernetes

8. • Declarative Config
• Fission resources are K8S CRDs, can be stored in YAML/JSON files
• Spec files allow us to recreate application in different fission clusters
• Support Rich Event Sources
• HTTP, Time, Kubewatch trigger
• Message queue trigger: NATS, Kafka
• Rich Environment Supportability
• NodeJs, Go, Python, Java (JVM) ..etc
• BYOE (Build Your Own Environment)
• Build Automation
• Builder manager creates a deployable package from source code
Fission

9. • More Cool Features
• Function Log Collection
• Canary Deployment (Beta)
• Record & Replay (Beta)
• Fission Workflow
• Function composition for serverless functions
Fission
upload
video
split
video into
frames
car
recognition
human
recognition
results
aggregation
store
end
result

10. FISSION CONCEPTS
BASIC FISSION
OBJECTS & RELATION

11. • Functions
• Source code (3rd-party dependencies)
• Environments
• Language runtime container
• Triggers
• HTTP, Timer, KubeWatch trigger
• Message queue trigger: NATS, Kafka
Three Core Objects

15. FISSION CONCEPTS
HOW FISSION WORKS
WITH KUBERNETES?

17. 第壱話
架
構、襲來

30. Function Pod - Specializing Process
1
2
3
4
5
6

31. FISSION CONCEPTS
TUNABLE
COST/PERFORMANCE
TRADEOFFS

32. • Pool-based executor (Poolmanager)
• Low-latency, small idle overhead
• Pre-warmed pool of env containers
• Functions loaded on-demand
• New-deployment executor (Newdeploy)
• High latency, small idle overhead
• Autoscaling: Min, Max instances
• Min: Idle cost v.s Burst tolerance
• Max: Throughput v.s Cost
Execution Strategies

33. • Careful configuration of resources limits
• Autoscaling makes cluster more efficient
• Public Cloud
• Pay for what you use
• Reserved/Spot/Preemptible VMs
• On-premises
• Resources should be proportional to
actual demand
Cost Optimization

34. DEMO TIME!
HOW DEVELOPERS
DELIVERY PRODUCT?

35. Make changes to production
directly and expect it to work?

36. Short feedback loop,
More iteration!
DEVELOPMENT
WORKFLOW

37. What fission can do
for developers (you)?

38. DEMO
CREATE / TEST
A SERVERLESS FUNCTION

39. DEMO
SHORT FEEDBACK LOOP
WITH LIVE-RELOAD

40. DEMO
(RE)DEPLOY APPLICATION
WITH SPEC FILES

41. Repo: https://github.com/fission/fission-bank-sample
Fission Bank Example

42. DEMO
PEFORM CANARY
DEPLOYMENT / ROLLBACK

43. What is Canary Deployment?

44. funcN-1: Red, funcN: Green
Init weight: 100:0
Traffic Graph in Canary Deployment

45. Traffic Graph in Canary Rollback
funcN-1: Red, funcN: Green
Init weight: 50:50

46. Q&A

47. Get Started with Fission!
Visit: fission.io
Github: github.com/fission/fission
Slack: slack.fission.io
Facebook: Fission User Group Taiwan
Workshop: 2018/11/03, Taipei