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

centos7 2.7.5 /usr/bin/python --> /usr/bin/python2 --> /usr/bin/python2.7 (可执行文件) centos8 3.6.8 /usr/libexec/pla�orm-python --> /usr/libexec/pla�orm-python3.6 (可执行文件) ①进入交互模式 # python3 /usr/bin/env python3 # coding=u�-8 print("hello world") # chmod +x test.py #添加可执行权限 # python3脚本文件开头位置要指定以下2行（使用的python解释器及本 源码文件编码） #!/usr/bin/env python3 # coding=u�-8 # python2脚本文件里要指定以下2行 # #!/usr/bin/env python # -*- coding: u�-8 -*- # ./test.py #执行脚本 #或者 # python3 test.py ★第1章、PyCharm常用设置 PyCharm官网： h�ps://www.jetbrains.com/pycharm/download/ ★PyCharm快捷键

更新日期：2023-12-27 ★第1章、安装postgresql # yum install postgresql-server -y # EL8安装光盘AppSteam里自带有10.x 版本的软件包 # postgresql-setup --initdb --unit postgresql # systemctl enable postgresql postgresql.org/download/linux/redhat/ 本文档选择PG-13版本作为讲解，使用el8系列的系统，x86_64平台 # yum install -y h�ps://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat- repo-latest.noarch.rpm #或者直接创建repo文件，内容如下 db_test | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres

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

version control. 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 tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – VMs, containers, applications, etc. 6. Generating configuration files 7. Run automated smoke tests 8. Running test procedures 9. Scripting & automating DB migrations iii. Focus on areas to reduce lead

to fear. Any Leader needs to be brave enough to allocate teams to do some calcuated risk- taking.” 8. Ch. 6 Understanding the Work in Our Value Stream, Making it Visible, and Expanding it Across the Organization compartmentalized and well-defined interfaces k. KEEP TEAM SIZES SMALL (THE “2-PIZZA TEAM” RULE) 10. Ch. 8 How to Get Great Outcomes by Integrating Operations into the daily Work of Development a. CREATE

Resources (RAM, disk, CPU, bandwidth, and others with hard or soft limits) 7. Health & availability 8. Startups & shutdowns 9. Faults & errors 10. Circuit breaker trips 11. Delays 12. Backup success/failure

studies over 85K cardholder breaches. 10 vulnerabilities accounted for 97% of the exploits used. 8 of the 10 exploits were over 10 years old. i. ENSURE SECURITY OF THE ENVIRONMENT i. Once a hardened