Bring your own code vs. Bring your own container

2018 - Cloud Foundry Summit North America, Boston, USA

https://www.youtube.com/watch?v=V_lM59cvGoI

Transcript

1. Bring your own code - Bring your own container Matthias Haeussler NovaTec Consulting GmbH
2. #whoami - Matthias Haeussler NovaTec Cloud Consultant Stuttgart CF Meetup Organizer @maeddes
3. &
4. &
5. What this talk will not be about ❏ Infrastructure & Infrastructure Automation ❏ ANYTHING BEYOND OOTB ❏ VENDOR - SPECIFIC IMPLEMENTATION ❏ EXTENSIONS & ADD-ONS
6. Intention of this talk app app deploy recovery (auto) scaling supported runtimes service bindings (aggregated) logging zero-downtime deployment
7. Intro
8. Cloud Foundry Basics app buildpack cf push app Applications Services container route
9. Kubernetes Basics - Part I - Container Dockerfile runtime app app runtime base container runtime app
10. runtime app Kubernetes Basics - Part II - Kubernetes runtime app kubectl run pod replica set runtime app runtime app pod v2 replica set v2 deployment service/ingress endpoint
11. Demo
12. Summary
13. Kubernetes ❏ Live Editing of Configuration ❏ Updating Configuration w/o Downtime ❏ Large Function Scope ❏ Very Granular Configuration Options ❏ Very Granular Configuration Options ❏ High Skill Requirement (Docker & K8s) ❏ Handling of Containers ❏ No OOTB (Tailed) Logs over RS/Deployments
14. Cloud Foundry ❏ Simplicity ❏ “Containerless” ❏ Very Fast “App to Platform” Path ❏ Buildpacks ❏ Limitation to Buildpacks ❏ Limited Configuration Scope ❏ No Automated Blue/Green Deploy ❏ Stateful workloads
15. You can do and configure more, But you have to do and know more
16. It is very easy to handle, does it give me all I need?
17. My wish: Functional Scope of K8s with the simplicity of Cloud Foundry
18. Happy to help @maeddes github.com/maeddes/cf-vs-k8s Stuttgart-Cloud-Foundry-Meetup