The document discusses how Kubo can be used as a gateway to running cloud-native workloads. It outlines different types of workloads like code developed internally which may change frequently or code from third parties. For internally developed code, Kubo allows maintaining existing processes while deploying container images instead of infrastructure. For external code and data-centric workloads, Kubo provides benefits like health management, multi-cloud support, and operating system/Kubernetes upgrades without affecting applications. The document calls developers to run workloads on Cloud Foundry Container Runtime and share experiences.

1. Kubo
Your Gateway Drug to Cloud-native
Cornelia Davis
Sr. Director of Technology
Pivotal
@cdavisafcCF Summit Basel, October 2017

2. @cdavisafc
Me?
Developer (wasn’t Ops)
Web architectures for >10 years
Cloud-native for 5 years
Cloud Foundry for 5 years
More recently
Discount code 40% off!: 40cloudnat

3. CONTAINERS
EVENT-DRIVEN
FUNCTIONS
DATA SERVICES
MICROSERVICES
Batches
MONOLITHIC
APPLICATIONS
Companies have many ways to package and run their
workloads in the cloud

4. CONTAINERS
EVENT-DRIVEN
FUNCTIONS
DATA SERVICESMICROSERVICES
Batches
MONOLITHIC
APPLICATIONS
IaaS
Application
Platform
(PaaS)
This is what most enterprises have today

5. CONTAINERS
EVENT-DRIVEN
FUNCTIONS
DATA SERVICESMICROSERVICES
Batches
MONOLITHIC
APPLICATIONS
IaaS
Container
Orchestrator
(CaaS)
Application
Platform
(PaaS)
Serverless
Functions
(FaaS)
Their goal: pick the right runtime for each workload
Kubo allows
us to up-level
from pure IaaS

6. So, let’s talk about workloads…
What workloads are you currently running on IaaS?
Code that
You
develop
Code that
Someone Else
Develops

7. Code that You develop
Cloud Native
Traditional
ArchitecturalStyle
Software LifecycleInfrequent
Changes
Frequent
Changes
Developer Productivity
Operational Efficiency
Operational Efficiency
Operational Efficiency
Operational Efficiency
Developer Productivity
(much of it you bring yourself)

8. Code that You develop
Traditional
ArchitecturalStyle
Software LifecycleInfrequent
Changes
Frequent
Changes
Operational Efficiency
Operational Efficiency
Developer Productivity
(much of it you bring yourself)

9. Code thatYou developTraditional Infrequent
ChangesOperational Efficiency
with
What are you doing for Infra deployments today?

10. Code thatYou developTraditional Infrequent
ChangesOperational Efficiency
with
What are you doing for Infra deployments today?
APP DEV QA OPERATIONS
CHANGE
MGMT
SECURITY COMPLIANCE
APPROVER APPROVER APPROVER APPROVER
infrastructure

11. Code thatYou developTraditional Infrequent
ChangesOperational Efficiency
with
Make target of existing processes the
image
rather than the infrastructure.
APP DEV QA OPERATIONS
CHANGE
MGMT
SECURITY COMPLIANCE
APPROVER APPROVER APPROVER APPROVER
docker image

12. Code thatYou developTraditional Infrequent
ChangesOperational Efficiency
with
What are you doing for Infra
deployments today?
Value
Minimal Disruption to Current Processes
Creates “low-hanging” fruit
Done Infrequently Approval heavy processes
okay
Health Management, Logging, Scaling From
Kubernetes
Multi-cloud Via Goodness!!
Kernel and Kubernetes Upgrades How do
you roll out new versions of the platform with
the lights on?
Consolidation More fully utilize your VMs and
Servers
More goodness!!

13. BUT...
Can I really roll the kernel or K8s version
without involving the app team?
While the app may be changing infrequently, the kernel
or Kubernetes version is likely to cycle more frequently.
Maybe…

14. cmtcmtcmt v201cmt cmt cmt cmt v202 cmt
… …
Prod
Acceptance
CI
Application Team - “Developer Productivity”

15. cmt v201cmt cmt cmt cmt v202 cmt
… …
App
Platform
CVE
Prod
Acceptance
Platform Team - “Operational Efficiency”

16. You don’t have to refactor your app, or retool your whole
process, but a test suite is a significant enabler!
What enables this is the
existence of a rich test suite!

17. Code that You develop
Traditional
ArchitecturalStyle
Software LifecycleInfrequent
Changes
Frequent
Changes
Operational Efficiency
Operational Efficiency
Developer Productivity
(much of it you bring yourself)

18. Code thatYou developTraditional Frequent
ChangesOperational Efficiency
with
How do you ensure your images meet corporate requirements?
Developer Productivity
∴
frequently changing the
image
Well…
… it’s up to you

19. Code thatYou developTraditional Frequent
ChangesOperational Efficiency
withDeveloper Productivity
Approved Base Image
Built into approved stemcell Select/build and approve base images
Runtime and other filesystem dependencies
Approved buildpack Build and approve Dockerfiles
Allow only approved images
CF Identity and Access
Management
Control build and/or scan image
repository
And more…

20. Code thatYou developTraditional Frequent
ChangesOperational Efficiency
withDeveloper Productivity
Value
Health Management, Logging, Scaling From
Kubernetes
Multi-cloud Via Goodness!!
Kernel and Kubernetes Upgrades How do
you roll out new versions of the platform with
the lights on?
Consolidation More fully utilize your VMs and
Servers
Developer Productivity
More goodness!!
But you’re changing a lot in your
process and tooling
Standardized Images
Controlled Dockerfiles
Compliance Approvals Across a Myriad of
Tools
… and much more.

21. Code that You develop
Traditional
ArchitecturalStyle
Software LifecycleInfrequent
Changes
Frequent
Changes
Operational Efficiency
Operational Efficiency
Developer Productivity
(much of it you bring yourself)

22. So, let’s talk about workloads…
What workloads are you currently running on IaaS?
Code that
You
develop
Code that
Someone Else
Develops

23. Someone ElseCode that
Cloud Native
Traditional
ArchitecturalStyle
Software LifecycleInfrequent
Changes
Frequent
Changes
Develops

24. Someone ElseCode that
Cloud NativeTraditional Architectural Style
Develops

25. Code that Others developCloud Native
Cloud-native Clusters
&
Data-centric workloads

26. Code that Others developCloud Native
Anticipate Change!
• Support nodes having new IP addresses on recreate
• Availability zone aware
• Flexible cluster topologies (i.e. dynamically scale)
• Need persistence
• No shared storage
Cloud-native Clusters
&
Data-centric workloads

27. Code that Others developCloud Native
Anticipate Change!
• Support nodes having new IP addresses on recreate
• Availability zone aware
• Flexible cluster topologies (i.e. dynamically scale)
• Need persistence
• No shared storage
Cloud-native Clusters
&
Data-centric workloads

28. Code that Others developCloud Native
Health Management, Logging, Scaling From
Kubernetes
Multi-cloud Via Goodness!!
Kernel and Kubernetes Upgrades How do
you roll out new versions of the platform with
the lights on?
Consolidation More fully utilize your VMs and
Servers
Value
More goodness!!
Why are we running these
workloads on Kubo?
Already Containerized ISVs are increasingly
distributing their software in containers
And, all of this

29. Someone ElseCode that
Cloud NativeTraditional Architectural Style
Develops

30. Code that Others developTraditional
BOSH
VMware GCP Azure Openstack AWS
K8s Cluster
K8s Cluster
K8s Cluster
Your Application

31. Code that Others developTraditional
Why??
Arguably, WLS itself gives you some
of these values - but only some.
Health Management, Logging, Scaling From
Kubernetes
Multi-cloud Via Goodness!!
Kernel and Kubernetes Upgrades How do
you roll out new versions of the platform with
the lights on?
Consolidation More fully utilize your VMs and
Servers
Value
More goodness!!
And possibly even licensing
compression!

32. Code that Others developTraditional
Leverages Stateful Sets
StatefulSets are valuable for applications that require one or more of the following.
• Stable, unique network identifiers.
• Stable, persistent storage.
• Ordered, graceful deployment and scaling.
• Ordered, graceful deletion and termination.
• Ordered, automated rolling updates.
https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
Replace
‘Pet Sets’
Beta in 1.8

33. Code that You develop Code that Others develop
ArchitecturalStyle
Software Lifecycle
ArchitecturalStyle
Software Lifecycle

34. 34
Call to Action
Run workloads
on
Cloud Foundry Container Runtime!
And Share!

35. Thank you!
Cornelia Davis
Sr. Director of Technology
Pivotal
@cdavisafc

36. @cdavisafc
Me?
Developer (wasn’t Ops)
Web architectures for >10 years
Cloud-native for 5 years
Cloud Foundry for 5 years
More recently
Discount code 40% off!: 40cloudnat