51 k8s-master2.cof-lee.com 10.99.1.52 k8s-master3.cof-lee.com 10.99.1.53 k8s-node01.cof-lee.com 10.99.1.61 k8s-node02.cof-lee.com 10.99.1.62 规划Pod网络： 10.244.0.0/16 规划Service网络： 10.7.0.0/16 # 99.1.53 k8s-master3.cof-lee.com k8s-master3 10.99.1.61 k8s-node01.cof-lee.com k8s-node01 10.99.1.62 k8s-node02.cof-lee.com k8s-node02 EOF ★k8s初始化时要求系统里有/etc/resolv.conf文件及系统对外通信网口上配置有 默认路由；根据实际情况添加 #加载配置 ⑧防火墙放行端口 TCP: 6443，2379，2380，10250~10252，30000~32767 UDP: 8285，8472 ★最好是允许整个k8s的node网段以及pod网段入站 # firewall-cmd --add-rich-rule='rule family="ipv4" source address="10.99.1.0/24" accept'

Em Campbell-Pretty - $200M, All streams of work were significantly behind schedule. Surprising discovery: only 50% of the source code in Dev/Test environments matched Prod. They fixed forward, but changes when validation tests fail 3. Developers working in small batches on trunk rather than long-lived feature branches f. BUILD A FAST AND RELIABLE AUTOMATED VALIDATION TEST SUITE i. Slow and periodic feedback purposes ii. Deployment – installing a specified version to a given environmentiii. Release – when a feature is made available to customers. 1. Release of functionality should not require changing our application

We can think of the project team and its sponsors and stakeholders as embarking on a voyage of discovery and innovation, during which they begin with a goal in mind and empirically find and test hypotheses

Condi�on()方法创建一个条件对象， 条件对象能让一个进程A暂停下来，等待另一个进程B的通知，当进程B 满足某个条件后通知进程A继续运行 import multiprocessing def operator_func(cond, name): cond.acquire() print(name + ": 我可以变更了吗？") cond.notify() # 发消息给Manager，唤醒一个挂起的线程 变更方案有问题，先不变更，先改方案") cond.notify() # 发消息给Operator，唤醒一个挂起的线程 cond.wait() # 等待Operator的回复 print(name + ": 好，可以变更了") cond.notify() # 发消息给Operator，唤醒一个挂起的线程 cond.release() def main(): cond = multiprocessing.Condition() opuser = multiprocessing.Process(target=operator_func, args=(cond, "cof-lee",)) mgmt = multiprocessing.Process(target=manager_func, args=(cond, "boss",))

whenever anyone performs deployment; focus on the metrics associated with the feature. ii. If negative results, ideally feature toggle off and fix-forward or use other Blue- Green, Canary release patterns Engineering) iii. Find the proper balance between fixing production issues and new features development – feature is only “done” when it’s performing as expected in production c. HAVE DEVELOPERS FOLLOW WORK DOWNSTREAM actually exists.” ii. How to build a feature: 1. Ask, “Should we build it, and why?” 2. Perform cheapest, fastest experiment possible to validate whether the feature will achieve desired outcomes. 3.

as we decide whether the quality of each individual feature is adequate for the feature to be deployed.  It is easy enough to say that the feature is ready for deployment when it passes all of its tests concepts of deployability and quality. A feature is simply deployable when it passes its tests; that is a yes-or-no question independent of quality.  Once the feature is in production, we can assess its

After we have invested so much of our time into implementing a given feature, if our customer tells us they don’t value the feature, can we really let it go?

day- or week- long improvement blitzes with Dev & Ops teams. Focus on problems they care about. NO FEATURE WORK ii. Goal is focused improvement on daily work, not experimentation and innovation iii. Demo

Route Adds – requires heightened security access  Database Data Script Execution  Load Balancer Node Disablement  OS and Security Patching  Requesting access to technology specific dashboards and