OpenShift 3 has been intertwined with Kubernetes development since the very beginning, and many of the developer focused workflows it has focused on has informed and been informed by the core design of Kubernetes. Today it offers workflow and tooling for application developers using Kubernetes as a development platform while still allowing those developers to manage the lower level components of the system. This talk will describe those patterns and how they enhance the core Kubernetes objects, and how those patterns are being moved into the Kubernetes core over time. We will cover: - Deploying and redeploying applications based on external changes – how does a developer rely on the platform to manage change, and how can the new Deployment object evolve to offer extended capabilities like triggers, hooks, and custom logic. - Building and rebuilding images based on administrator or developer source code, and how immutable image infrastructures like Kubernetes and Docker are dependent on automated end to end build chains. - Allowing administrators to offer a low cost way to expose hundreds or thousands of applications through a front-end load balancer without requiring dedicated load balancers, and how the Ingress resource allows abstraction of high availability and external exposure while allowing administrative control. - Hosting toolchains on top of Kubernetes that allow better development experience – specifically cheap Git hosting and mirroring and scale out Jenkins slaves. - Administrative policies that can limit and control developer action to allow sharing of the cluster. The talk will also touch on future design directions for OpenShift 3 and Kubernetes and how the platform can grow to better serve large scale application hosting. KubeCon schedule link: http://sched.co/4VAn

1. Cloud-native Development
Clayton Coleman
Architect and Engineer, OpenShift
Kubernetes Core Contributor

2. What is OpenShift?

3. Not your mother’s PaaS

4. 1. Built on top* of Kube
2. Enable organizations to use Kube
3. Add app-dev workflows
* with stuff in the middle, and underneath (for now)

5. Why not inside Kube?

6. 1. Ecosystem
(big tent)
2. Brook’s Law
(no monoliths)

7. Isn’t Kube enough?

8. “I believe it [Kubernetes] can be the right abstraction for
99% of server software running across more than a single
machine - the real cloud OS”

9. “I believe it [Kubernetes] can be the right abstraction for
99% of server software running across more than a single
machine - the real cloud OS”
— Me

10. Kube today is a runtime for apps
owned by a small set of admins.

11. Kube will be more, and the OpenShift team
is part of the many people helping to make
it that way.

12. First, make Kube usable for
organizations ...

13. Authentication, user management, LDAP integration,
groups, teams, fine-grained access control, unified
policy, quotas, admission control, limits, container
security, templating, high density edge routing, etc ...

14. You know, the boring stuff.

15. Second, enable and manage the
flow of software onto and
across cloud infrastructure
(CI/CD for everything)

16. Real world
1. Lots of flows, tools, and layers
2. Integrate all can, build only what
we must

17. BuildSource Code Image Deploy

18. BuildSource Code
CIBranch Merge
Image Deploy
Release

19. BuildSource Code
CIBranch
IntegrationLibrary
Merge
Promotion
Image Deploy
Release
Consume

20. Build Image DeploySource CodeImage

21. Image
Build Image DeploySource Code
BuildSource Code
PHP 5.5 Stable
Build Image DeploySource Code
...
Build Image DeploySource Code
...
Applications using PHP 5.5
...

22. Image
Build Image DeploySource Code
BuildSource Code
PHP 5.5 Stable
Build Image DeploySource Code
...
Build Image DeploySource Code
...
Applications using PHP 5.5
...
Sometimes you centralize
what “stable” means to you
Sometimes everyone has
their own meaning

23. Image
Build Image DeploySource Code
BuildSource Code
PHP 5.5 Stable
Build Image DeploySource Code
...
Build Image DeploySource Code
...
Applications using PHP 5.5
...
Sometimes you centralize
what “stable” means to you
Sometimes everyone has
their own meaning
Also, what happens when a
deployment fails?
Flow has to stop.

24. Demo time
Less talk

25. Thanks
Get involved! Source code at https://github.
com/openshift/origin
Download and run v1.0.8 from Docker Hub
https://docs.openshift.org/latest/getting_started/administrators.html
Clayton Coleman ccoleman@redhat.com
smarterclayton on GitHub