A presentation at Innotech OKC in
November 2018 in
Oklahoma City, OK, USA by
Why to Cloud Native Karthik Gaekwad @iteration1 Principal Engineer, Oracle Cloud Innotech OKC
Hello • I’m Karthik Gaekwad • NOT a DBA
• https://cloudnative.oracle.com/ • Cloud Native evangelist at Oracle Cloud • Previous: developer on the Oracle Managed Kubernetes Team.
• Been in Industry 15 years. • In general, I like building stuff with friends. • A maintainer for Gauntlt- Open source security scanner.
• Love Teaching and building community. • Run Devopsdays Austin, Container Days, Cloud Austin. • Chair All Day Devops Cloud Native track. • LinkedIn Learning Author for Learning Kubernetes (and more).
Need an OCI Trial Account?
My questions for you..
Agenda • What is cloud native? • Where are we today in the cloud native world? • The Cloud Native ecosystem. • Cloud Native adoption. • Challenges.
What is Cloud Native?
What is Cloud Native? “A new computing paradigm that is optimized for modern distributed systems environments capable of scaling to tens of thousands of self healing multi-tenant nodes” -Cloud Native Computing Foundation
Pillars of Cloud Native
Continuous Delivery Devops
Pillars of Cloud Native: Devops “DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.” -The Agile Admin blog https://theagileadmin.com/what-is-devops/
Pillars of Cloud Native: Devops • Generally based on principles of CALMS • Based on the ideas of Automation, Measurement, Sharing • Emphasis on a Collaborative culture in organizations • Shifting operations more to the left. • Operations teams does more than just “server management” • Uses same techniques as developers for systems work
Pillars of Cloud Native: CD • Origins in the automation segment of Devops • Similar to Continuous Integration • Frequent code commits into source control • Run automated builds against each code commit • Result= Detecting errors quicker
• Continuous Delivery • Step 1: Continuous Integration • Release code builds to end users • Result= ship software quicker to end users
Pillars of Cloud Native: Microservices
Microservices Design • Start with Twelve-Factor App design • https://12factor.net • Based on the principals of software design and deployment at Heroku • Development best practice that synergizes with devops engineers
Twelve Factor App • Principles: • Declarative formats for Automation • Clean Contracts with underlying systems • Able to deploy to modern cloud platforms • Keep your prod and dev systems similar • Easily scale up without changes to architecture, tooling, development etc.
• 12 factor apps enable easy container integration
Pillars of Cloud Native: Containers • Way to package applications • Fits really well as a packaging strategy for microservices • Not a new concept • Popularized by the growth of Docker, and Kubernetes
Pillars of Cloud Native: Containers Core to Edge
Phase I Developer Focus
Container Adoption Focus Applications Automation Community
Developer adoption Dev/Test apps Simple orchestration Individual developers
Phase II DevOps Focus
Application Deployment DevOps deployment Production apps Advanced orchestration Teams & lines of business
Phase III Business Focus (end-to-end)
Intelligent Operations End-to-end integration Digital business apps Serverless, DevSecOps, & ML Cloud native enterprises
Developer Trends in the Cloud: Open source Digital Ocean Survey, October 2018 Respondents=4300
Evolution of Development and Deployment Development Process
Deployment and Packaging
Plan Monito r
Cloud Native Usecases
Key Container Use Cases Share
Container Use Cases
Orchestration Use Cases
Developer productivity; Consistent appstacks in Dev, Test & Production
Automated deploys to accelerate application release cadence
Containerized dependencies; Container registries;
Rolling updates and reversals
Standardized environments for dev, testing and operations
Resilient, self-healing systems; High Availability; Elastic Scalability
Refactor Legacy Apps
Refactor from N-tier to portable containerized applications
Run distributed, stateful apps on scale-out infrastructure
Migrate to Cloud
Move entire appstacks and see them run identically in the cloud
Cloud bursting; Reduce infrastructure costs by avoiding over-provisioning
New Microservice Apps
Create small purpose-built services that can be assembled to scalable custom applications
Dynamically manage large-scale microservices infrastructure
SOURCE: THE EVOLUTION OF THE MODERN SOFTWARE SUPPLY CHAIN, DOCKER SURVEY 2016
New Technology?? Must Adopt!!
Business and Engineering
The Business Case for Cloud Native • Quicker Time to Deliver • Modernizing present day applications • Develop new applications quickly • Improve speed of innovation
Quicker Time To Deliver • Containers + Microservices allows for a common language between your development and operations teams • Shared Understanding… • Allows for IT in general to practice a devops culture • Less friction between various teams in the organization
• Practicing Continuous Delivery allows you to ship faster • Process of making changes becomes easily • Reduces perceived risk of making changes
Modernizing present day applications • Shipping applications in containers reduces dependencies on underlying infrastructure • As a result, previous on premise applications can be exported to the cloud. • Kubernetes provides a single unified platform to deploy containers across all your infrastructure
Develop new applications quickly • Rich technical ecosystem. • Large community • Kubernetes and CNCF slack has over 35k people • Plenty of meetups in many different cities
• Based on opensource • Developers can read the source code of platforms they are using
• Easier to find developers who want to work on newer technologies
Improve speed of innovation • Cloud Native brings a new culture, technology and processes to accelerate innovation in organizations. • Devops, CI/CD, Containerization modernizes your existing development teams • Allows them to go much faster than before.
CNCF Trail Map https://landscape.cncf.io/images/landscape.pdf
Top 5 challenges to cloud native adoption… Monitoring Security Lack of Training Cultural Challenges Complexity 0
Other Challenges • Storage (30% down from 41%) • Networking (30% down from 38%) • Reliability (17% down from 20%) • Logging (25% down from 32%) • Scaling (20% down from 24%)
Technical Challenges Decrease
Kubernetes & Cloud Native Challenges • Managing, maintaining, upgrading Kubernetes Control Plane • API Server, etcd, scheduler etc….
• Managing, maintaining, upgrading Kubernetes Data Plane • In place upgrades, deploy parallel cluster etc….
• Figuring out container networking & storage
• Overlays, persistent storage etc… - it should just work
• Managing Teams
• How do I manage & control team access to my clusters?
• Security, security, security
Source: Oracle Customer Survey 2018
Where do I start? Some strategies…
Silos • Heavily siloed organizations can benefit from a devops mindset • Use containers as a way to break down silos in your engineering orgs
Releasing Code • Step 1: Invest in Continuous Integration • Step 2: Continuous Delivery
Orchestration? Your company/organization manages containers with:
Biggest Lie: “Kubernetes is easy”
Kubernetes is complex • Use a Kubernetes Managed Service
• Like Oracle Container Engine for Kubernetes, Google Kubernetes Engine etc
• Benefits: • Enables developers to get started and deploy containers quickly. • Gives DevOps teams visibility and control for Kubernetes management. • Combines production grade container orchestration of open Kubernetes, with control, security, IAM, and high predictable performance of cloud infrastructure • Manage what you really need to manage
Kubernetes is Complex OCI Registry
OCI Container Engine for Kubernetes Cluster Management
Encryption for Data in Transit (SSL) and at Rest
HA - 3 Masters/etcd across 3 ADs OKE Dashboard in OCI Console
Customer’s OCI Account/Tenancy
VM based Clusters and Nodes Bare Metal Clusters and Nodes
Oracle Cloud Infrastructure Oracle Managed
Customer Managed 4 1
End to End Workflow… Any CI/CD - ie Jenkins, Oracle Pipelines, etc.
• Container Native: Standard Upstream Kubernetes; Fully Managed Lifecycle; Integrated Registry
• Developer Friendly: Simple, Streamlined User
Interface; REST API; Helm, and DNS Built-in
OCI Container Engine for Kubernetes
• Enterprise Ready: Oracle Cloud Infrastructure
Performance; Highly Available; Secure with OCI Access Controls
Exposed Kubernetes Service
Node Pool Node Pool
Take It slow…
Greenfield OR Strangler application patterns
KEEP CALM AND KUBE ON @iteration1
View Why to Cloud Native on Notist.
Presentation on what it means to be cloud native, covering the ecosystem, adoption and challenges in the landscape