k8s操作手册 前言： 1.蓝色字体表示命令行命令，正式执行时不要复制前面的#号，#号只是提示应 该使用root权限操作 2.绿色字体表示注释，有时注释太多就不用绿色表示了 3.注意：本文档的所有操作请先在测环境进行实践，请不要直接在真实的服务 器中操作！ 版权声明： 本文档以开源的形式发布，所有条款如下： （1）无担保：作者不保证文档内容的准确无误，亦不承担由于使用此文档所导致的任何后果 更新日期：2023-12-29 ★第0章、K8S集群搭建准备工作 相关单词原义： docker 码头工人 pod 集装箱 kubernetes 舵手，领航员 helm 舵轮，驾驶盘 chart 图表，海图 ①k8s对系统要求 linux内核在3.10及以上，服 ②规划主机名及ip k8s的服务器使用固定ip地址，配置主机名，要求能解析相应的主机名（master 结点）到对应的ip地址，可以使用内网集群的dns服务器或写入/etc/hosts文件 里。如： 主机名 ip地址 k8s-master1.cof-lee.com 10.99.1.51 k8s-master2.cof-lee.com 10.99.1.52 k8s-master3.cof-lee

com/pycharm/download/ ★PyCharm快捷键 Alt + Shi� 列选择模式，可同时选择多列 Ctrl + Alt + L 重新格式化代码，Reformat Code Ctrl + B 跳转到鼠标指定的函数定义处 Shi� + F10 运行程序 Ctrl + R 查找替换 ★设置字体颜色 File → Se�ngs → Editor → Color Scheme → Language #设置要安装的路径， pefix为可选 # make && make install 创建软链接： # ln -s /usr/local/python3.x.x/bin/python3 /usr/bin/python3 # ln -s /usr/local/python3.x.x/bin/pip3 /usr/bin/pip3 # 默 认 安 装 无 需 指 定 函数创建集合，创建空集合必须使用 set()而不能用 {} 例： a=set("fldsaj") b=set("fdslj") a - b #a和b的差集 a | b #a和b的并集 a & b #a和b的交集 a ^ b #a和b中不同时存在的元素 ★判断变量类型 type(x)

The DevOps Handbook – Part 1 & 2 1. Preface xi a. Myth—DevOps is Only for Startups: b. Myth—DevOps Replaces Agile c. Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information rapidly changing competitive landscape 2. Provide stable, reliable, and secure service to the customer b. THE BUSINESS VALUE OF DEVOPS i. Code and change deployments (thirty times more frequent) ii. Code employee happiness 2. one of the best predictors of short lead times was small batch sizes of work b. Agile, Continuous Delivery, and the Three Ways 7 c. The First Way: The Principles of Flow 15 i. MAKE

pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the Church of Graphs. If it moves, we track it. Sometimes we’ll draw a graph of something that isn’t performers b. CREATE OUR CENTRALIZED TELEMETRY INFRASTRUCTURE i. Remove the silos of information – Developers don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down metrics b. Common service to centralize, rotate, and delete 2. Event router responsible for storing our events and metrics a. Enables visualization, trending, alerting, & other good things b. Enable

testing with the Chaos Monkey; they architected for failure, tested for failure, and evolved beyond it b. ESTABLISH A JUST, LEARNING CULTURE i. Unjust responses to incidents 1. Impede safety 2. Promote Post-Mortem – meeting to examine “mistakes in a way that focuses on the situational aspects of a failure’s mechanism and the decision- making process of individuals proximate to the failure.” – John Allspaw Explicitly disallow the phrases “would have” or “could have” a. These are counterfactual statements b. Frames the problem as the system as imagined rather than the system that actually exists 4. Focus

continuous integration & testing iv. Automating, enabling, and architecting for low-risk releases b. Integrating objectives of QA & Operations to improve outcomes 2. Ch. 9 – Create the Foundations of Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE ON-DEMAND CREATION OF DEV, TEST, AND PRODUCTION ENVRIONMENTS i. Major contributing cause of when they get sick, you shoot them.” iii. Ensure consistency across all environments (Prod, pre-prod(s), dev, & new) iv. Immutable Infrastructure 1. Once created no changes are allowed 2. Changes must

inser�on(+) create mode 100644 main.py # git log #查看提交记录；显示完整的hash值 commit 7b8ff6902bf14780a413a021cc1d946fd82fa82e (HEAD -> master) # commit后面为hash值，HEAD表示 Author: Cof b8ff69 (HEAD -> master) msgxxx # git log 文件名 #查看目标文件的提交记录 # git log -p -3 master * master # git branch xxx #在当前提交的对象上创建新的分支，名为xxx # git branch yyy 7b8ff6 #在指定的提交对象上创建新的分支；提交的hash值 可写全，也可只写前6字符 # git checkout xxx #切换分支 # git

exactly what IT leaders must avoid; continuously transforming and modernizing the company’s IT systems makes Fowler’s strangler pattern into an IT strategy rather than just a coding tactic. If you missed deal with the question of whether it is a near enough fit.I don’t mean that standards are bad. Let’s just agree that they might be overrated. A Better Way – Treat IT as an Enterprise Asset (EA): When user-centric way and match the enterprise’s needs precisely. Risk is low, because the team is constantly adjusting.  Option 2: Compare that to the risk of buying a vendor’s product, where the investment is one

Summary [1] Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO. The company's new IT initiative, code named Phoenix Project, is critical very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. With the help of a prospective board member and his mysterious Unplanned work “What can displace planned work? Unplanned work. That’s why Erik called it the most destructive type of work. It’s not really work at all, like the others. The others are what you planned

successful technology transformation but requires substantial changes in behavior at every level, and Mark’s thorough analysis will prove invaluable to leaders who must execute it.” – Jez Humble, CTO, DevOps process. Brining Lean Principles to Software Development: Kanban is David Anderson’s approach to bringing Lean principles into software development while driving fear out of the transformation depends on whether I am satisfied with its plan. I might ask these questions when I review a team’s plans:  What are the business outcomes the team is trying to achieve? What kinds of activities do