DevOps with Azure, Kubernetes, and Helm: Automating App Deployment
•Transferir como PPTX, PDF•
7 gostaram•2,269 visualizações
This document discusses DevOps tools for working with containers and Kubernetes. It introduces Helm as a package manager for Kubernetes that allows defining complex Kubernetes applications as charts that can be installed, upgraded, and rolled back easily. Codefresh is presented as a DevOps platform that integrates with Kubernetes and provides built-in steps for working with containers in CI/CD pipelines. The document provides an overview of concepts like containers, Docker, Kubernetes, orchestration, and Helm architecture. It also describes how to get started with installing Helm.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a DevOps with Azure, Kubernetes, and Helm: Automating App Deployment
Semelhante a DevOps with Azure, Kubernetes, and Helm: Automating App Deployment (20)
Mais de Codefresh
Mais de Codefresh (20)
Último
Último (20)
DevOps with Azure, Kubernetes, and Helm: Automating App Deployment
- 1. DevOps with Azure, Kubernetes, and Helm Jessica Deen ⎸Cloud DevOps Advocate ⎸Microsoft Dan Garfield ⎸Full Stack Engineer ⎸Codefresh
- 2. • Linux, Open Source, Containers, IT/Ops • CrossFit • HUGE Disney and Star Wars fan • League of Extraordinary Cloud DevOps Advocates
- 5. Adopting Kubernetes by cobbling together lots of tools and scripts is costly and time consuming ● Build servers ● Staging servers ● Build automation ● Webhooks ● Docker registry ● Kubectl ● Helm ● CI Tests ● Integration Tests ● UI Tests ● Performance Tests ● Security Scans ● Deployment tools ● Secrets management ● Configuration testing ● Traceability Dashboards Why Codefresh?
- 6. Codefresh is a DevOps Platform Built for Kubernetes Kubernetes CI/CD Pipelines Self-Service Test Environments Docker & Helm Registry Release Management
- 7. Codefresh pipelines have built-in steps for working with containers ● Deep integration w/ K8s and Helm ● Supports any language ● Complete DevOps platform Create an account at codefresh.io Start streamlining your engineering!
- 8. Agenda
- 10. What we hear from developers I need to create applications at a competitive rate without worrying about IT New applications run smoothly on my machine but malfunction on traditional IT servers My productivity and application innovation become suspended when I have to wait on IT
- 11. What we hear from IT I need to manage servers and maintain compliance with little disruption I’m unsure of how to integrate unfamiliar applications, and I require help from developers I’m unable to focus on both server protection and application compliance
- 13. Servers Services Cloud is a new way to think about a datacenter
- 15. DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. - Donovan Brown http://bit.ly/WhatIs-DevOps
- 16. Plan 1 Monitor + Learn ReleaseDevelop + Test 2 Development Production 4 3
- 18. What is a container? Containers = operating system virtualization Traditional virtual machines = hardware virtualization Windows Server containers: maximum speed and density Hyper-V containers: isolation plus performance OS Kernel Applications Container Container Container Hardware Hardware Container Container Container Hyper-V Container Kernel Container Kernel Container Kernel Hardware OS Application VM VM VM App OS App OS App OS
- 19. What is a container? Not a real thing. An application delivery mechanism with process isolation based on several Linux kernel features. (what a process can see) (what a process can use)
- 20. What is ? • An open source container runtime • Mac, Windows & Linux support • Command line tool • “Dockerfile” file format for building container images • The Docker image format with layered filesystem
- 22. Docker Layered File System
- 23. Virtualization Containerization Type 1 Hardware Hypervisor 1 VM VM VM Hardware Type 2 Host OS Hypervisor 2 VM VM VM Virtual machine Guest OS Dependencies Application Hardware Host OS Docker Engine Dependency 1 Dependency 2 C C C C C Container App dependencies Application XYZ Virtualization versus containerization
- 24. The container advantage Fast iteration Agile delivery Immutability Cost savings Elastic bursting Efficient deployment For ITFor developers
- 26. The elements of orchestration Scheduling Affinity/anti- affinity Health monitoring Failover Scaling Networking Service discovery Coordinated app upgrades
- 27. Kubernetes: the de-facto orchestrator Portable Public, private, hybrid, multi-cloud Extensible Modular, pluggable, hookable, composable Self-healing Auto-placement, auto-restart, auto-replication, auto-scaling
- 28. Kubernetes: empowering you to do more Deploy your applications quickly and predictably Scale your applications on the fly Roll out new features seamlessly Limit hardware usage to required resources only
- 37. Where can I get/run Kubernetes
- 40. Why AKS?
- 41. Getting Started with AKS
- 42. Managing an AKS cluster
- 45. Release automation tools Simplifying the Kubernetes experience Streamlined Kubernetes development The package manager for Kubernetes Event-driven scripting for Kubernetes Visualization dashboard for Brigade Azure Container Service (AKS) Azure Container Instances (ACI) Azure Container Registry Open Service Broker API (OSBA) Release Automation Tools
- 46. Helm The best way to find, share, and use software built for Kubernetes Manage complexity Charts can describe complex apps; provide repeatable app installs, and serve as a single point of authority Easy updates Take the pain out of updates with in- place upgrades and custom hooks Simple sharing Charts are easy to version, share, and host on public or private servers Rollbacks Use helm rollback to roll back to an older version of a release with ease Azure Container Service (AKS) Azure Container Instances (ACI) Azure Container Registry Open Service Broker API (OSBA) Release Automation Tools
- 47. Helm Helm Charts helps you define, install, and upgrade even the most complex Kubernetes application custom services Chart.yml db load balancer ci … Azure Container Service (AKS) Azure Container Instances (ACI) Azure Container Registry Open Service Broker API (OSBA) Release Automation Tools
- 49. Architecture Key concepts: Helm, Tiller, Charts • Helm has two major components: • Helm client • Tiller server • Helm client is the CLI for end users • Written in Go, uses gRPC to interact with the server • Sends charts and values to Tiller for install, upgrade, etc.
- 50. Architecture Tiller server • In-cluster server that interacts with the client and interfaces with the Kubernetes API server Chart • Collection of Kubernetes resources
- 54. Get a Codefresh Demo! Schedule a 1:1 at Codefresh.io
- 55. Connect with me! Email: jessica.deen@microsoft.com Twitter/GitHub/Instagram: @jldeen Blog: jessicadeen.com LoECDA Website: loecda.com
Notas do Editor
- Why is this transformation important? Let’s take a look at the next few years before us… In 2020, 1 million new devices are expected to come online every hour. The connectivity between people and data is creating billions of new relationships that are driven not only by data but by algorithms that keep customers engaged and buying.* In 2020, the average age of a S&P 500 corporation is expected to be 12 years old. Compare that to the S&P 500 in 1960 when the average age was 60 years old.** By the year 2025, at least 60 percent of computing will be cloud-based, due to “everything-as-a-service” shifting fundamental changes in the IT industry.*** For digital transformation, mobility is the universal catalyst and cloud is the great enabler. How are you planning for digital transformation? Do you have the right people and the right technology in place to build your digital vision? How can you use technology to shape your future? *http://www.gartner.com/newsroom/id/3142917 **http://upstart.bizjournals.com/resources/author/2015/06/04/fortune-500-must-disrupt-or-die-writes-r-ray-wang.html?page=all ***http://www.emersonnetworkpower.com/en-US/Latest-Thinking/Data-Center-2025/Documents/002401_DataCenter2025Report_HR_INTERACTIVE.PDF
- Here’s what we hear from dev Want to be able to move fast Things to run smooth on their machine and production – dev / prod parity Don’t want to be blocked on IT / ops team
- IT - wants to minimize risk don’t really understand applications or what it takes to be a dev Unable to do both infrastructure stuff and handle the application operations
- Traditional model - Empathize, land the case for change based on change in business context Take empathizing tone (don’t want to make this sound negative). We want them to realize that what customers have done may have worked in the past but they need to recognize the need for change as the business is changing rapidly. Most companies are running custom apps that are stitched together, they have purpose-built hardware to think about, and have specialized teams, and everything has been carefully customized (over many years in some cases!). Now as an enterprise, you did all this for all the right reasons, but you might consider that it might be holding our customers (and their business) back in many ways given that the business context has changed fundamentally. In this new age of apps, the old way of doing this is causing friction because IT isn’t moving as fast as business wants it to. This is manifested in developers not getting the speed and freedom they need to create the best end-user experiences. That leads to lost productivity on their side, which results in ‘Shadow IT’. In 2015, 42% of the technology budget resides outside IT; this will grow to 50% by 2020 (Gartner). So this is real. And we all know that while Shadow IT behaviors provide immediate gratification, it comes with risk. Slide 8: Cloud model (Mark) – Empathize, ask customers to be change agents, land cloud principles. Now let’s look at the cloud. Everyone knows that the cloud offers agility and innovation. It’s proving itself to be the way forward for the modern enterprise and we’ll talk more about that in a bit. But for some of our IT customers, the cloud might seem a little daunting. They might be asking, “Is this something I want to lead the charge on? How does it help my career?” The tension some of them experience is because you’re not sure if things are consistent with what you’re doing on-premises and it seems like it will be hard to manage. There’s also a tension between developers who want speed and freedom (represented by business demands), and the IT folks who have to worry about things like security and compliance. Bridge to our POV while bringing them along. Implore them to be change agents in their orgs. But make no mistake about it – the cloud is the natural way forward for the rapidly evolving enterprise. Let’s all embrace it. In this context, we’re already seeing some leading indicators around “bi-modal“ IT among you: 45% of CIOs have a second, fast, mode of service delivery that complements their rock solid operations” (Gartner Symposium, Oct 2014). So there’s already some great progress that a lot of you seem to be driving. This is do-able. And we want our customers to be change agents in driving cloud adoption in your orgs. Our POV We believe that cloud is a model/architecture, not a location. (Cloud-first principles as in the slide) Turns out that Microsoft has been on its own cloud-first journey for many years and we have fully operationalized cloud-first in our hyper-scale datacenters. We’d like to share some of that next to help customers shortcut their journey.
- People = Culture Fundamental attributes of successful cultures: Shared mission and incentives: infrastructure as code, apps as services, DevOps/all as teams You need to consider your hardware as a commodity, (don't give your servers names) , servers are like farm animals, it is just harder if you let theids name them Build deep instrumentation into services, push complexity up the stack Rally around agile, shared metrics, CI, service owners on call, etc. Changing the culture: any change takes time, changing culture is no exception and you can't do it alone, exploit compelling events to change culture: downtimes, cloud adoption, devops buzz PROCESS Definition and design, compliance, and continuous improvement PEOPLE Responsibilities, management, skills development, and discipline Products Tools and infrastructure
- 2014 Report collected in December 2013 had over 9,200 survey respondents across 110 countries with companies of ALL sizes and verticals. 2015 Report had 4,976 respondents with companies of ALL sizes and verticals.
- What is a container really? Operating system virtualization / process.
- Demo Notes Scenario: I've introduced a compliance violation to the image and will correct that compliance violation. I am going to setup a Codefresh CI pipeline and configure a quick unit test and use the build image to scan my built image. - Show adding repository - Add shared configuration - Convert UI -> YAML - Replace ${{BuildingDockerImage}} - Run build of master - Create new compliance-fix branch - Add twistlock user code to Docker image && \ adduser -u 1000 -S twistlock -G docker USER twistlock - Build locally - Test locally - Commit & Push - Wait for Codefresh build - Merge That completes my demo