[DevOps] Orchestration With Kubernetes
DevOpsKubernetes with
2023-09-14 08:59:12 时间
We’ll cover topics including:
- Why Orchestration?
- Kubernetes Fundamentals
- Kubernetes on AWS
- Using a Kubernetes Cluster
- Other Deployment Strategies
Why Orchestration?
Mainly it helps to handle complicated workflows
- Deploy code
- Recover from failure
- Scale
We focus on continuesly deployment.
The tools such as Jenkins / Travis can help to build docker image (CI), Kbuernates can helps to orchestrate our CD process to complete our software developement life-cycle.
Kubernetes Fundamentals
- A container orchestration system packed with features for automating our application’s deployment
- Enables us to easily scale our application and ship new code
- Automate scheduling
- Recover from Failure
- Automate releases
- Handle Scaling
K8s for Automated code Rollout
- Detect the latest code
- Launch into containers
Pods
- Containers often need to communicate with one another. It's not uncommon to see a deployment involving a few containers to be deployed.
- Kubernetes pods are abstractions of multiple containers and are also ephemeral.
Services
-
Applications are often deployed with multiple replicas. This helps with load balancing and horizontal scaling.
-
Services are an abstraction of a set of pods to expose them through a network.
What's the purpose of wrapping pods as a service?
A: User shouldn't care when pods are destroyed. Pods are ephemeral and expected to be terminated. Services persist and are the abstraction that exposes the pods.
New Terms
Term | Description |
---|---|
Horizontal Scaling | Handling increased traffic by creating additional replicas so that traffic can be divided across the replicas |
Kubernetes Service | An abstraction of a set of pods and interface for how to interact with the pods |
Pods | A set of containers that are deployed together |
Load Balancing | Handling traffic by distributing it across different endpoints |
Replica | A redundant copy of a resource often used for backups or load balancing |
Consumer | An external entity such as a user or program that interfaces with an application |
相关文章
- 【精彩回顾】软件DevOps云化发展的趋势
- 【华为敏捷/DevOps实践】7. 敏捷,DevOps,傻傻不分清楚
- devops思想
- DevOps - curl
- DevOps - Groovy
- DevOps - API网关
- [DevOps] Using Terraform to Create an EC2 Instance
- ML:从工程化思维分析—机器学习团队十大角色的简介(背景/职责/产出物):产品经理、项目经理、业务咨询顾问、数据科学家、ML研究员、数据工程师、ML工程师、DevOps/软件开发/交付工程师
- Computer:项目管理之软件开发模式(瀑布式开发、快速原型开发、迭代式开发、螺旋式开发、敏捷式开发、DevOps开发)的简介、对比之详细攻略
- 618之际,“敏捷+ DevOps”正提高电商企业的业务和交付效能
- 【华为云技术分享】华为云 DevCloud 首席产品布道师:AIOps 不是 DevOps 的下一代
- 【云原生 • Kubernetes】kubernetes 核心技术 - 持久化存储
- 【云原生 • DevOps】devOps 入门、Maven 插件自动部署微服务
- 杂记 DevOps模式定义及优势
- Kubernetes 深入理解kubernetes(一)
- Kubernetes 将应用迁移至kubernetes
- Kubernetes基础_01_从云原生到kubernetes
- 云原生DevOps篇:使用Pipeline流水线项目构建Docker镜像实战
- 从业者必读,一篇文章轻松掌握DevOps核心概念和最佳技能实践!