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 # pod网络和service网络都要求为16位的地址块，且不能与环境中其他网络地址 段冲突 # hostnamectl set-hostname k8s-master1.cof-lee.com set-�mezone Asia/Shanghai #设置时区 # systemctl restart chronyd # chronyc sources -v ⑦设置网络参数 #首先加载模块 # cat > /etc/modules-load.d/br_ne�ilter.conf <service.d # docker info ★docker会修改防火墙规则，导致pod网络不通 # vi /usr/lib/systemd/system/docker.service #在[Service]下的ExecStart=/usr/bin/dockerd -H fd:// 这行下面再添加一行：

按原字节数 < li�le-endian 按原字节数，小端字节序 > big-endian 按原字节数，大端字节序，逻辑上 是啥顺序就是啥 ! network = big- endian 按原字节数，网络字节序 使用方法是在format的第一个位置指示即可 struct解析二进制串示例： import struct with open("test.txt","rb+") as fileobj: # win32, linux2 print(sys.getwindowsversion()) # (major=10,minor=0,build=17763,platform=2,service_pack='') ★math模块 import math x = 2 math.sqrt(x) # 返回x的平方根，float math.pi # add_experimental_option("excludeSwitches", ['enable-automation']) # 解决密码提示 prefs = {"credentials_enable_service": False, "profile.password_manager_enabled": False} chrome_options.add_experimental_option("prefs"

/var/lib/pgsql/13/* /data_pg/ #将原数据目录下所有内容移动到新 数据目录下 # vi /usr/lib/systemd/system/postgresql-13.service #pg-13版本，修改systemd服 务文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/13/data/ 改为新的路径，如 下： /var/lib/pgsql/* /data_pg/ #将原数据目录下所有内容移动到新数 据目录下 # vi /usr/lib/systemd/system/postgresql.service #pg-10版本，修改systemd服务 文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/data/ 改为新的路径，如下： E HeidiSQL官网： h�ps://www.heidisql.com/ pgAdmin官网下载： h�ps://www.pgadmin.org/download/ 下载并安装最新版本的HeidiSQL，新建会话，网络类型为PostgreSQL(TCP/IP)，依 赖库要>=目标pg数据库版本 下载最新版本的pgAdmin并安装运行 ★第6章、数据库及表基础操作 pg数据库名称及表名称不区分大小写

#停止 # gitlab-ctl restart #重启 ★放通防火墙 # firewall-cmd --add-service=h�p # firewall-cmd --add-service=h�ps # firewall-cmd --run�me-to-permanent ★查看h�p配置： gitlab-ce自带有nginx软件，查看默认生成的配置： reused 0 (delta 0), pack-reused 0 Receiving objects: 100% (6/6), done. ★配置webhook自动化触发功能 首先配置允许向本地网络（私有网段地址）发送webhook通知，如果不配置则 会报错： 管理员用户登录，点击设置： 勾选“Allow requests to the local network from webhooks

sidecar container will include: 1. A logging agent to push logs to a platform centralized logging service. 2. Container policy enforcement. This includes ensuring container hardening from DCAR containers notifications when there is anomalous behavior. 4. Vulnerability Management 5. A service mesh proxy to connect to the service mesh 6. Zero Trust down to the container level. Zero trust requires strict Program-specific Log Storage and Retrieval Service 2. Service Mesh 3. Program-specific artifact repository 4. Runtime Behavior Analysis Artificial Intelligence (AI) service 5. DCAR for the hardened containers

Respond to the 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 iii. Production deployments (sixty times higher change success rate) iv. Mean time to restore service (168 times faster) 4. An Introduction to The DevOps Handbook xxi 5. PART I—THE THREE WAYS 1 a desired iv. Operations – the team responsible for maintaing the production environment and ensuring service levels are met v. Infosec – team responsible for securing systems and data vi. Release Managers

Operation Framework study found the best-performing organization were better at diagnosing & fixing service incidents. 1. “Culture of Causality” 2. Used disciplined approach to solving problems using telemetry Collection at business logic, application, & environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and delete 2. Event router responsible for storing our events and metrics production changes iii. Tools – StatsD, JMX, codahale, New Relic, Prometheus, etc. f. CREATE SELF-SERVICE ACCESS TO TELEMETRY AND INFORMATION RADIATORS i. Spread the information – anyone who wants or needs

Velocity all about? What did I learn? Service Workers: The Practical Bits by Patrick Meenan (Google) @patmeenan http://www.slideshare.net/patrickmeenan/service-workers-for-performance  They are effectively

#先结束刚刚运行的进程 # cat > /etc/systemd/system/redis.service <Service] Type=forking ExecStart=/usr/local/bin/redis-server /root/redis-6

– continually ensure all environments are synchronized and consistent e. ENABLE AUTOMATED SELF-SERVICE DEPLOYMENTS i. As a result of compliance, oversight, and control needs separate Operations groups deployment ii. Shows readiness of production environments at a glance iii. Provides push-button, self-service for any suitable version into production iv. Record automatically for auditing who and what commands