Kubernetes in Startups vs Enterprise: Using Custom Resources to extend workflow

Kubernetes and Containers are taking over the world and it seems that is they fit in every use-case from a small startup to big bank industries. But in reality every environment is unique with it´s own peculiarities. Kubernetes is not the end-game, it´s the platform for platforms. During this talk we´ll discuss about the differences between startups and enterprises and how we can fill the gap integrating inside Kubernetes our custom workflow using Custom Resources and Operators.

We´ll do a demo of a Project entity that helps provision namespaces and grants user access to team members. CRDs are a powerful tool for Kubernetes extensibility but with great power comes great responsibility.

Transcript

1. @spiddy Kubernetes in Startups vs Enterprise Using Custom Resources to extend workflow By Dimitris Kapanidis
2. @spiddy About me Docker Captain | Google Developer Expert Docker BCN | Kubernetes BCN Meetup Organizer Consulting @ Harbur Cloud Solutions 2
3. @spiddy Startups vs Enterprise Where does Kubernetes fits? 3
4. @spiddy The Container revolution is here 4
5. @spiddy The Container revolution is here • Decoupling of development / deployment environment • Standard packaging format • The Twelve-Factor App implementation • Microservice design 5
6. @spiddy The evolution of IT industry 6
7. @spiddy Waterfall vs Agile 7
8. @spiddy The Waterfall Model 8 “The waterfall model is a linear sequential (non-iterative) design approach for software development, in which progress flows in one direction downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance”
9. @spiddy 9 Waterfall Origins on Construction
10. @spiddy 10 Waterfall Origins on Manufacturing
11. @spiddy 11 Requirements Design Implementation Verification Maintenance Waterfall on IT
12. @spiddy Waterfall on IT 12
13. @spiddy The Agile Model 13 “Agile software development describes a set of values and principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams“
14. @spiddy Agile Manifesto Values • Individuals and Interactions over Processes and Tools • Working Software over Comprehensive Documentation • Customer Collaboration over Contract Negotiation • Responding to Change over Following a Plan 14
15. @spiddy Agile Model vs Waterfall 15
16. @spiddy Agile Examples on IT 16
17. @spiddy Monolithic vs Microservices 17
18. @spiddy Monolithic Architecture 18 “A software system is called "MONOLITHIC" if it has a monolithic architecture, in which functionally distinguishable aspects are all interwoven, rather than containing architecturally separate components.“
19. @spiddy Traditional Architecture 19
20. @spiddy 20 Design up front
21. @spiddy Over Allocation of Infrastructure 21
22. @spiddy 22 Physical Separation
23. @spiddy 23 Monolithic Design
24. @spiddy Traditional Architecture Internal Network Load Balancers Legend Server Connection Database Client 24
25. @spiddy 25
26. @spiddy Monolithic Architecture Issues • Cannot scale-out individually each function • Cannot do easily rollback of version upgrade • Adding a function forces complete rollout • Cannot easily do A/B test of a function 26
27. @spiddy Microservices Architecture 27
28. @spiddy Modern Architecture - Design Minimal Viable Product - Design process embraces changes - Easily Scalable Infrastructure - No Physical boundaries (Zero Trust Network) - Infrastructure as Code - Microservice-Oriented Design 28
29. @spiddy Microservices Architecture 29
30. @spiddy 30
31. @spiddy Bare Metal vs Virtualization vs Containers 31
32. @spiddy 32 Bare-Metal
33. @spiddy 33 Virtual Machines
34. @spiddy 34 Containers
35. @spiddy 35 Bare Metal / Virtualization / Containers
36. @spiddy On Premise vs Cloud 36
37. @spiddy 37
38. @spiddy 38
39. @spiddy Why is Kubernetes so damn difficult? 39
40. @spiddy 40 Kubernetes orchestrates Containers
41. @spiddy 41 Containers are ephemeral by design Kubernetes orchestrates Containers
42. @spiddy 42 Containers can scale +/- on demand Containers are ephemeral by design Kubernetes orchestrates Containers
43. @spiddy 43 Kubernetes implements Microservices Containers can scale +/- on demand Containers are ephemeral by design Kubernetes orchestrates Containers
44. @spiddy 44 Microservices imply a distributed system Kubernetes implements Microservices Containers can scale +/- on demand Containers are ephemeral by design Kubernetes orchestrates Containers
45. @spiddy 45 Distributed systems are intrinsically difficult Microservices imply a distributed system Kubernetes implements Microservices Containers can scale +/- on demand Containers are ephemeral by design
46. @spiddy But there are good news 46
47. @spiddy 47 Kubernetes... architecture is simple
48. @spiddy Kubernetes... follows the single responsibility principle 48
49. @spiddy Kubernetes... facilitates separation of concerns 49
50. @spiddy Kubernetes... abstracts away cloud vendor details 50
51. @spiddy Kubernetes... is the defacto standard for container ops 51
52. @spiddy Kubernetes... learn once deploy anywhere 52
53. @spiddy Kubernetes... is extendable 53
54. @spiddy Startups vs Enterprise Where does Kubernetes fits? 54
55. @spiddy Startup environment • Start from scratch, no legacy code, no migration process • Small organization • Flat organization chart • Agile oriented • Microservice oriented 55
56. @spiddy Startup too small for Kubernetes? • Kubernetes has steep learning curve • Kubernetes is focused on automation of CI/CD • Kubernetes is compatible with DevOps • Kubernetes is designed to provide resilience, redundancy and high availability • Kubernetes is designed to run on multiple nodes 56
57. @spiddy When not to use Kubernetes... 57 When your production should run on just one node
58. @spiddy When not to use Kubernetes... 58 When your org is less than 8 people
59. @spiddy When not to use Kubernetes... 59 When maintenance downtime is not an issue (yet)
60. @spiddy When not to use Kubernetes... 60 When automation is not a priority (yet)
61. @spiddy Enterprise environment • Legacy code, migration process is needed • Big organization • Hierarchical organization chart • Waterfall oriented • Monolithic oriented 61
62. @spiddy Kubernetes on Enterprise • Multiple clusters are needed to support HA on multiple datacenters • Container Images promotion process ◦ Vulnerability scanning from security team • Networking is hardened ◦ Connection to Internet is restricted/limited ◦ Network isolation per Namespace • Assets are provisioned ◦ Using LimitRanges & ResourceQuotas • Pods are hardened ◦ Using PodSecurityPolicies • Multiple teams need access to clusters ◦ Each team can manage their own resources 62
63. @spiddy Using Custom Resources to extend workflow 63
64. @spiddy Multiple teams need access to clusters • Teams can create projects with their own namespaces (dev, pre, pro) • They can assign project members • They can grant rolebindings to project members 64
65. @spiddy Project Initializer - The Cloud Native way 65
66. @spiddy 66 https://github.com/harbur/kubernetes-project-initializer-tutorial/
67. Thank You! Innovating Container Delivery
68. @spiddy Thank you 68