【4.21.1】服務(wù)器安裝 Linux中安裝 kubernetes1.19 集群方式1

參考：https://www.cnblogs.com/codenoob/p/14073585.html

添加 kubernetes.repo 文件

vim /etc/yum.repos.d/kubernetes.repo

[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

添加 docker-ce.repo 文件 從阿里下載

vim /etc/yum.repos.d/docker-ce.repo

[docker-ce-stable]
name=Docker CE Stable - $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-stable-debuginfo]
name=Docker CE Stable - Debuginfo $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/debug-$basearch/stable
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-stable-source]
name=Docker CE Stable - Sources
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/source/stable
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-edge]
name=Docker CE Edge - $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/$basearch/edge
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-edge-debuginfo]
name=Docker CE Edge - Debuginfo $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/debug-$basearch/edge
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-edge-source]
name=Docker CE Edge - Sources
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/source/edge
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-test]
name=Docker CE Test - $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/$basearch/test
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-test-debuginfo]
name=Docker CE Test - Debuginfo $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/debug-$basearch/test
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-test-source]
name=Docker CE Test - Sources
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/source/test
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-nightly]
name=Docker CE Nightly - $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/$basearch/nightly
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-nightly-debuginfo]
name=Docker CE Nightly - Debuginfo $basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/debug-$basearch/nightly
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-nightly-source]
name=Docker CE Nightly - Sources
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/source/nightly
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

安裝docker，master node節(jié)點(diǎn)都需要安裝

這部分參照

修改docker cgroup驅(qū)動(dòng)狰晚，與k8s一致坐梯，使用systemd

# 修改docker cgroup驅(qū)動(dòng)：native.cgroupdriver=systemd
cat > /etc/docker/daemon.json <<EOF
{
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2",
  "storage-opts": [
    "overlay2.override_kernel_check=true"
  ]
}
EOF

systemctl restart docker  # 重啟使配置生效

安裝 kubelet kubeadm kubectl

master言缤、node節(jié)點(diǎn)都需要安裝

# 開頭更換了k8s軟件源锯七，應(yīng)該可以直接安裝的
# 關(guān)閉SElinux
setenforce 0
sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config

# 安裝kubelet kubeadm kubectl
yum install -y kubelet kubeadm kubectl --disableexcludes=kubernetes

systemctl enable --now kubelet  # 開機(jī)啟動(dòng)kubelet

# centos7用戶還需要設(shè)置路由：
yum install -y bridge-utils.x86_64
modprobe  br_netfilter  # 加載br_netfilter模塊访敌，使用lsmod查看開啟的模塊
cat <<EOF >  /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system  # 重新加載所有配置文件

systemctl disable --now firewalld  # 關(guān)閉防火墻

# k8s要求關(guān)閉swap  (qxl)
swapoff -a && sysctl -w vm.swappiness=0  # 關(guān)閉swap
sed -ri '/^[^#]*swap/s@^@#@' /etc/fstab  # 取消開機(jī)掛載swap

上面的步驟需要在每個(gè)節(jié)點(diǎn)上面都執(zhí)行腊嗡，也可以做完一臺(tái)機(jī)器之后克隆一下

創(chuàng)建集群準(zhǔn)備工作

# Master端：
kubeadm config images pull # 拉取集群所需鏡像舷手，這個(gè)需要翻墻

# --- 不能翻墻可以嘗試以下辦法 ---
kubeadm config images list # 列出所需鏡像
k8s.gcr.io/kube-apiserver:v1.19.4
k8s.gcr.io/kube-controller-manager:v1.19.4
k8s.gcr.io/kube-scheduler:v1.19.4
k8s.gcr.io/kube-proxy:v1.19.4
k8s.gcr.io/pause:3.2
k8s.gcr.io/etcd:3.4.13-0
k8s.gcr.io/coredns:1.7.0

# 根據(jù)所需鏡像名字先拉取國內(nèi)資源
#你需要的鏡像不一定和我的一樣拧簸，按照上一條命令列出的鏡像以及版本為準(zhǔn)
（下面的是我執(zhí)行的命令，一般來說應(yīng)該就是版本不太一樣）
#安裝鏡像
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.19.4
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.19.4
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.19.4
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.13-0
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.7.0
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2

#修改鏡像tag
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4  k8s.gcr.io/kube-proxy:v1.19.4
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.19.4  k8s.gcr.io/kube-controller-manager:v1.19.4
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.19.4  k8s.gcr.io/kube-apiserver:v1.19.4
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.19.4  k8s.gcr.io/kube-scheduler:v1.19.4
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.13-0  k8s.gcr.io/etcd:3.4.13-0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.7.0  k8s.gcr.io/coredns:1.7.0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2  k8s.gcr.io/pause:3.2

#刪除舊的鏡像
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.19.4
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.19.4
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.19.4
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.13-0
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.7.0
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2

# Node端：拉去以下兩個(gè)就夠了
# 根據(jù)所需鏡像名字先拉取國內(nèi)資源
#安裝鏡像
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2

#修改鏡像tag
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4  k8s.gcr.io/kube-proxy:v1.19.4
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2  k8s.gcr.io/pause:3.2

#刪除舊的鏡像
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.19.4
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2

使用kubeadm創(chuàng)建集群
systemctl status kubelet

# 初始化Master（Master需要至少2核）此處會(huì)各種報(bào)錯(cuò),異常...成功與否就在此
kubeadm init --apiserver-advertise-address 192.168.200.25 --pod-network-cidr 10.244.0.0/16 # --kubernetes-version 1.19.4
# --apiserver-advertise-address 指定與其它節(jié)點(diǎn)通信的接口,這里應(yīng)該寫本機(jī)的ip就可以
# --pod-network-cidr 指定pod網(wǎng)絡(luò)子網(wǎng)男窟，使用fannel網(wǎng)絡(luò)必須使用這個(gè)CIDR
# --kubernetes-version 指定k8s版本盆赤，這個(gè)不帶會(huì)使用最新的，但是獲取版本是需要聯(lián)外網(wǎng)的歉眷，可能會(huì)超時(shí)牺六，這時(shí)候可以指定一個(gè)版本

如果上述步驟執(zhí)行失敗，出現(xiàn)各種錯(cuò)誤汗捡，要執(zhí)行

kubeadm reset

之后再重新init兔乞，想要查看具體錯(cuò)誤信息可以在后面加上 --v=6

[root@localhost home]# kubeadm init --apiserver-advertise-address 192.168.0.31 --pod-network-cidr 10.244.0.0/16  --kubernetes-version 1.19.4
W1202 15:09:24.257078   17784 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.4
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost.localdomain] and IPs [10.96.0.1 192.168.0.31]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost localhost.localdomain] and IPs [192.168.0.31 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost localhost.localdomain] and IPs [192.168.0.31 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 16.003574 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node localhost.localdomain as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node localhost.localdomain as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: ere3er.k4ew50j7i31xw9mq
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.0.31:6443 --token ere3er.k4ew50j7i31xw9mq \
    --discovery-token-ca-cert-hash sha256:eb15f18caa138bd4d3944cc63db36ccdeb6a5b281009ca73444c0299d9a7adaa 
[root@localhost home]#

一定要把最后輸出的那句話保存起來

kubeadm join 192.168.0.31:6443 --token ere3er.k4ew50j7i31xw9mq \
    --discovery-token-ca-cert-hash sha256:eb15f18caa138bd4d3944cc63db36ccdeb6a5b281009ca73444c0299d9a7adaa

這個(gè)是你創(chuàng)建的其他節(jié)點(diǎn)加入該集群命令驗(yàn)證

普通用戶設(shè)置權(quán)限

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

應(yīng)用flannel網(wǎng)絡(luò)

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

node節(jié)點(diǎn)加入集群

# 把你安裝好的master節(jié)點(diǎn)最后那句話復(fù)制執(zhí)行就行，你的跟我的肯定不一樣
# node1:
kubeadm join 192.168.20.5:6443 --token w2i0mh.5fxxz8vk5k8db0wq \
    --discovery-token-ca-cert-hash sha256:65e82e987f50908f3640df7e05c7a91f390a02726c9142808faa739d4dc24252 
# node2:
kubeadm join 192.168.20.5:6443 --token w2i0mh.5fxxz8vk5k8db0wq \
    --discovery-token-ca-cert-hash sha256:65e82e987f50908f3640df7e05c7a91f390a02726c9142808faa739d4dc24252

然后就可以在master節(jié)點(diǎn)看一下是否正常

kubectl get nodes
NAME                    STATUS   ROLES    AGE   VERSION
lijun-k8s-1.novalocal   Ready    master   15h   v1.19.4
lijun-k8s-2.novalocal   Ready    <none>   15h   v1.19.4

點(diǎn)波關(guān)注 系統(tǒng)搭建（docker）

最后編輯于 ：
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請(qǐng)聯(lián)系作者
  • 人面猴
    序言：七十年代末凉唐，一起剝皮案震驚了整個(gè)濱河市庸追，隨后出現(xiàn)的幾起案子，更是在濱河造成了極大的恐慌台囱，老刑警劉巖淡溯，帶你破解...
    沈念sama閱讀 212,816評(píng)論 6贊 492
  • 死咒
    序言：濱河連續(xù)發(fā)生了三起死亡事件，死亡現(xiàn)場離奇詭異簿训，居然都是意外死亡咱娶，警方通過查閱死者的電腦和手機(jī)米间，發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 90,729評(píng)論 3贊 385
  • 救了他兩次的神仙讓他今天三更去死
    文/潘曉璐 我一進(jìn)店門，熙熙樓的掌柜王于貴愁眉苦臉地迎上來膘侮，“玉大人屈糊，你說我怎么就攤上這事∏砹耍” “怎么了逻锐？”我有些...
    開封第一講書人閱讀 158,300評(píng)論 0贊 348
  • 道士緝兇錄：失蹤的賣姜人
    文/不壞的土叔 我叫張陵，是天一觀的道長雕薪。 經(jīng)常有香客問我昧诱，道長，這世上最難降的妖魔是什么所袁？ 我笑而不...
    開封第一講書人閱讀 56,780評(píng)論 1贊 285
  • ?港島之戀（遺憾婚禮）
    正文 為了忘掉前任盏档，我火速辦了婚禮，結(jié)果婚禮上燥爷，老公的妹妹穿的比我還像新娘蜈亩。我一直安慰自己，他們只是感情好前翎，可當(dāng)我...
    茶點(diǎn)故事閱讀 65,890評(píng)論 6贊 385
  • 惡毒庶女頂嫁案：這布局不是一般人想出來的
    文/花漫 我一把揭開白布稚配。 她就那樣靜靜地躺著，像睡著了一般鱼填。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發(fā)上毅戈，一...
    開封第一講書人閱讀 50,084評(píng)論 1贊 291
  • 城市分裂傳說
    那天苹丸，我揣著相機(jī)與錄音，去河邊找鬼苇经。 笑死赘理，一個(gè)胖子當(dāng)著我的面吹牛，可吹牛的內(nèi)容都是我干的扇单。 我是一名探鬼主播商模，決...
    沈念sama閱讀 39,151評(píng)論 3贊 410
  • 雙鴛鴦連環(huán)套：你想象不到人心有多黑
    文/蒼蘭香墨 我猛地睜開眼，長吁一口氣：“原來是場噩夢啊……” “哼蜘澜！你這毒婦竟也來了施流？” 一聲冷哼從身側(cè)響起，我...
    開封第一講書人閱讀 37,912評(píng)論 0贊 268
  • 萬榮殺人案實(shí)錄
    序言：老撾萬榮一對(duì)情侶失蹤鄙信，失蹤者是張志新（化名）和其女友劉穎瞪醋，沒想到半個(gè)月后，有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體装诡，經(jīng)...
    沈念sama閱讀 44,355評(píng)論 1贊 303
  • ?護(hù)林員之死
    正文 獨(dú)居荒郊野嶺守林人離奇死亡银受，尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點(diǎn)故事閱讀 36,666評(píng)論 2贊 327
  • ?白月光啟示錄
    正文 我和宋清朗相戀三年践盼，在試婚紗的時(shí)候發(fā)現(xiàn)自己被綠了。 大學(xué)時(shí)的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片宾巍。...
    茶點(diǎn)故事閱讀 38,809評(píng)論 1贊 341
  • 活死人
    序言：一個(gè)原本活蹦亂跳的男人離奇死亡咕幻，死狀恐怖，靈堂內(nèi)的尸體忽然破棺而出顶霞，到底是詐尸還是另有隱情肄程，我是刑警寧澤，帶...
    沈念sama閱讀 34,504評(píng)論 4贊 334
  • ?日本核電站爆炸內(nèi)幕
    正文 年R本政府宣布确丢，位于F島的核電站绷耍，受9級(jí)特大地震影響，放射性物質(zhì)發(fā)生泄漏鲜侥。R本人自食惡果不足惜褂始，卻給世界環(huán)境...
    茶點(diǎn)故事閱讀 40,150評(píng)論 3贊 317
  • 男人毒藥：我在死后第九天來索命
    文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望描函。 院中可真熱鬧崎苗，春花似錦、人聲如沸舀寓。這莊子的主人今日做“春日...
    開封第一講書人閱讀 30,882評(píng)論 0贊 21
  • 一樁弒父案，背后竟有這般陰謀
    文/蒼蘭香墨 我抬頭看了看天上的太陽互墓。三九已至必尼，卻和暖如春，著一層夾襖步出監(jiān)牢的瞬間篡撵，已是汗流浹背判莉。 一陣腳步聲響...
    開封第一講書人閱讀 32,121評(píng)論 1贊 267
  • 情欲美人皮
    我被黑心中介騙來泰國打工， 沒想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留育谬，地道東北人券盅。 一個(gè)月前我還...
    沈念sama閱讀 46,628評(píng)論 2贊 362
  • 代替公主和親
    正文 我出身青樓，卻偏偏與公主長得像膛檀，于是被迫代替她去往敵國和親锰镀。 傳聞我的和親對(duì)象是個(gè)殘疾皇子，可洞房花燭夜當(dāng)晚...
    茶點(diǎn)故事閱讀 43,724評(píng)論 2贊 351

推薦閱讀更多精彩內(nèi)容

  • 下圖是一個(gè)基本的Kubernetes 安裝部署圖咖刃。 由于資源限制泳炉，我只選了兩個(gè)虛擬機(jī)來嘗試。Master: 192...
    WeiminSun閱讀 546評(píng)論 0贊 3
  • 前言： kubernetes作為docker的管理工具是由Google開源提供嚎杨，但是kubernetes的安裝一直...
    SookieYang閱讀 11,811評(píng)論 3贊 13
  • Kubernetes作為容器應(yīng)用的管理中心胡桃，通過對(duì)Pod的數(shù)量進(jìn)行監(jiān)控，并且根據(jù)主機(jī)或容器失效的狀態(tài)將新的Pod調(diào)...
    輝耀輝耀閱讀 4,597評(píng)論 0贊 13
  • 寫在前面的話：從2014年起磕潮，每看完一本書翠胰，都會(huì)在本子上寫下自己的讀后感之類的容贝，所看過的書，針對(duì)目前情況來說之景，大多...
    翔子大人閱讀 839評(píng)論 0贊 5
  • 今天聽了萌姐的刻意練習(xí)斤富，學(xué)到以下幾點(diǎn)： 1、學(xué)習(xí)要有目標(biāo)锻狗，圍繞目標(biāo)满力，大量的練習(xí)，反復(fù)的練習(xí)轻纪，需要很大的意志力脫離舒...
    A揚(yáng)州特產(chǎn)雙黃蛋閱讀 198評(píng)論 0贊 0