k8s操作手册 2.3
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-lee0 码力 | 126 页 | 4.33 MB | 1 年前3python3学习手册
#设置要安装的路径, 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 # 默 认 安 装 无 需 指 定 oct() 将一个整型数字转为8进制字符串,0onn bin() 将一个整型数字转为2进制字符串,0bnn ★str字符串大小写转换及替换过滤拆分拼接 strx="what cAnd Wfds s�dsD" strx.lower() #全转为小写,返回新的字符串,不改变原字符串 strx.upper() #全转为大写,返回新的字符串,不改变原字符串 strx print( "这是第%2d号,体重%5.2f公折" % (num, wei) ) %-6.3f 表示左对齐,共6位宽,3位小数,浮点型(默认左对齐) 类 型 码 含义 类型码 含义 %c 字符 %s 字符串 %d 十进制整数 %u 无符号整数 %o 八进制数 %x 小写十六进制数 %X 大写十六进制数 %f 浮点数 %e 科学计数法,小写e %g 自动采用最短的%f或%e %F 同%f,会把inf0 码力 | 213 页 | 3.53 MB | 1 年前3A Seat at the Table: IT Leadership in the Age of Agility - Part 2
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 one0 码力 | 7 页 | 387.61 KB | 5 月前3The Phoenix Project
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 planned0 码力 | 3 页 | 154.45 KB | 5 月前3A Seat at the Table - IT Leadership in the Age of Agility
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 0 码力 | 4 页 | 379.23 KB | 5 月前3Government Excerpt
Let’s ask a question that has a chance to actually change things: “What is the set of incentives that drives bad behavior?” I truly doubt that any of the Beltway bandits sees themselves as bad people well-meaning. It’s the system that has failed them, and us. But how do we change it? How do we encourage transparency, priori- ties, and accountability? You know the answer: Scrum. Let’s start a few thousand state does is make decisions. We want to find a way to leave less paper on a desk.”1 The governor’s plan has five points that could have been plucked from any campaign platform: 1. A “world-class”0 码力 | 3 页 | 414.99 KB | 5 月前3The DevOps Handbook
poor quality 3. Consider when we have an annual schedule for software releases, where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing possible c. Gary Gruver observes, “It’s impossible for a developer to learn anything when someone yells at them for something they broke six months ago—that’s why we need to provide feedback to everyone decisions.” 2. Greatness is not achieved by leaders making all the right decisions—instead, the leader’s role is to create the conditions sotheir team can discover greatness in their daily work. In other0 码力 | 8 页 | 22.57 KB | 5 月前3The DevOps Handbook
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 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. ii. Modern Monitoring architecture 1. Data Collection internal issues 5. Fatal – forces a termination iv. Examples of potentially significant events (Gartner’s GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data0 码力 | 8 页 | 24.02 KB | 5 月前3A Seat at the Table - IT Leadership in the Age of Agility
on behalf of the business; it is to steward the asset that is the total of all of the enterprise’s IT capabilities—an asset that has functional capabilities (how it is used today) but also latent capabilities is a kind of feedback cycle that lets us make good decisions in the normal course of work. Let’s say that we are deciding between two different open source products for building a piece of the system due to capacity constraints or to the governance process’s limitations. A picture of today’s emerging workforce. These characteristics of today’s emerging workforce reinforce the changes I have been describing0 码力 | 7 页 | 387.48 KB | 5 月前3The DevOps Handbook
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 and availability b. Don’t inspect security in at the end, it’s integrated as part of our daily work i. Make security part of everyone’s jobii. Integrate preventative controls into our shared repository process vii. Reduce reliance on separation of duties 2. Ch. 22 – Information Security as Everyone’s Job, Every Day a. Many DevOps organizations have better results than when security is organized as0 码力 | 9 页 | 25.13 KB | 5 月前3
共 16 条
- 1
- 2