server地址 --pod-network-cidr=10.244.0.0/16 \ # pod容器网段 --service-cidr=10.7.0.0/16 \ # service网段，即cluster ip网段 --ignore-preflight-errors=Swap \ #忽略swap未关闭而导致的检查错误 --image-repository="cof- lee.com:5443/k8s" cof-lee.com:5443/k8s kind: ClusterConfigura�on kubernetesVersion: v1.19.4 networking: dnsDomain: cluster.local serviceSubnet: 10.7.0.0/16 podSubnet: 10.244.0.0/16 scheduler: {} --- apiVersion: kubelet server地址 --pod-network-cidr=10.244.0.0/16 \ # pod容器网段 --service-cidr=10.7.0.0/16 \ # service网段，即cluster ip网段 --ignore-preflight-errors=Swap \ #忽略swap未关闭而导致的检查错误 --image-repository="cof- lee.com:5443/k8s"

changes, never mutate existing ii. Remove application assumptions about DB version iii. The Canary & Cluster Immune System Release Patterns 1. Canary Strategy a. Automates the release process of promoting environments b. Successful application behavior moves to the next group; failure stops or rolls back 2. Cluster Immune Strategy a. Expands upon Canary. Links production monitoring with release process to automatically

be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led and managed through an inspect-and- adapt, feedback-and-vision-oriented approach because of its complexity.

REDUCING TECHNICAL DEBT i. Don’t just make the interest payments, pay down the principle ii. If not managed, services become so fragile, delivery grinds to a halt g. INCREASE THE VISIBILITY OF WORK i. Keep

required mitigation.  The basic plan would remain valid, and the risk of the unexpected could be managed within the plan by itemizing potential risks, actively working to prevent them, and, if necessary

bashrc #之后就可以正常使用conda命令了 # >>> conda ini�alize >>> # !! Contents within this block are managed by 'conda init' !! __conda_setup="$('/root/anaconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"