參考官網(wǎng)：
https://kubernetes.io/docs/setup/independent/install-kubeadm/#verify-the-mac-address-and-product-uuid-are-unique-for-every-node
kubeadm init 配置文件參數(shù)參考：
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
3臺 centos7 最新的系統(tǒng)
etc 跑在1臺 master 節(jié)點上
網(wǎng)絡組件使用Calico, 轉(zhuǎn)發(fā)使用 ipvs
主機名ip說明組件 k8s-company01-master01 172.16.4.201 1個 master 節(jié)點 keepalived、haproxy、etcd、kubelet、kube-apiserver k8s-company01-worker001 ~ 002 172.16.4.204 ~ 205 2個 worker 節(jié)點 kubelet
swapoff -a; sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab
timedatectl set-timezone Asia/Shanghai
crontab -e 加入：
crontab：8 * * * * /usr/sbin/ntpdate asia.pool.ntp.org && /sbin/hwclock --systohc備注:關閉 selinux
setenforce 0
sed -i --follow-symlinks "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/config
sed -i --follow-symlinks "s/^SELINUX=permissive/SELINUX=disabled/g" /etc/selinux/config# 關閉 firewalld
systemctl stop firewalld.service
systemctl disable firewalld.service# 配置主機名（注意修改成自己的）：
3臺主機分別設置主機名：
hostnamectl set-hostname k8s-company01-master01
hostnamectl set-hostname k8s-company01-worker001
hostnamectl set-hostname k8s-company01-worker002在3臺主機的/etc/hosts 中添加
cat >> /etc/hosts <<EOF
172.16.4.201 k8s-company01-master01.skymobi.cn k8s-company01-master01
172.16.4.204 k8s-company01-worker001.skymobi.cn k8s-company01-worker001
172.16.4.205 k8s-company01-worker002.skymobi.cn k8s-company01-worker002
EOFyum install wget git jq psmisc vim net-tools tcping bash-completion -y
yum update -y && reboot
# 重啟不僅是是讓新升級的 kernel 生效，也讓調(diào)用到 hostname 的相關服務使用新的 hostname
每臺安裝CRI(這里默認使用 docker，k8s 1.12開始推薦使用 docker 18.06 版本，但由于18.06有個 root 提權的漏洞，這里我們使用最新的版本，18.09.5)
yum
install -y yum-utils device-mapper-persistent-data lvm2yum-config-manager \--add-repo \https://download.docker.com/linux/centos/docker-ce.repoyum
install -y docker-ce-18.09.5 docker-ce-cli-18.09.5
mkdir /etc/docker
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 mkdir -p /etc/systemd/system/docker.service.dsystemctl daemon-reload
systemctl
enable docker.service
systemctl restart docker
固定 docker 版本，防止以后意外更新到另外的大版本：
yum -y install yum-plugin-versionlock
yum versionlock docker-ce docker-ce-cli
yum versionlock list
cat << EOF
> /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables
= 1
net.bridge.bridge-nf-call-iptables
= 1
net.ipv4.ip_forward
= 1
vm.swappiness
= 0
vm.overcommit_memory
= 1
vm.panic_on_oom
= 0
fs.may_detach_mounts
= 1
fs.inotify.max_user_watches
= 89100
fs.file-max
= 52706963
fs.nr_open
= 52706963
net.netfilter.nf_conntrack_max
= 2310720
EOFmodprobe br_netfilter
sysctl --system
cat << EOF
> /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
exclude
= kube*
EOFyum
install -y kubelet-1.14.1 kubeadm-1.14.1 kubectl-1.14.1 cri-tools-1.12.0 kubernetes-cni-0.7.5 ipvsadm --disableexcludes
= kubernetes
modprobe ip_vs
modprobe ip_vs_rr
modprobe ip_vs_wrr
modprobe ip_vs_sh
modprobe nf_conntrack_ipv4
modprobe br_netfilter
cat << EOF
>> /etc/rc.d/rc.local
modprobe ip_vs
modprobe ip_vs_rr
modprobe ip_vs_wrr
modprobe ip_vs_sh
modprobe nf_conntrack_ipv4
modprobe br_netfilter
EOF
chmod +x /etc/rc.d/rc.local
DOCKER_CGROUPS=$(docker info | grep 'Cgroup' | cut -d' ' -f3)
echo $DOCKER_CGROUPS
cat > /etc/sysconfig/kubelet <<EOF
KUBELET_EXTRA_ARGS="--cgroup-driver=$DOCKER_CGROUPS --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google_containers/pause-amd64:3.1"
EOF# 開機啟動并 start now，之后 kubelet 啟動是失敗的，每隔幾秒鐘會自動重啟，這是在等待 kubeadm 告訴它要做什么。
systemctl enable --now kubelet# 添加 kubectl 參數(shù) tab 鍵自動補全功能
source /usr/share/bash-completion/bash_completion
source <(kubectl completion bash)
echo "source <(kubectl completion bash)" >> ~/.bashrc
網(wǎng)絡組件使用Calico, 轉(zhuǎn)發(fā)使用 ipvs
k8s-master01
# 注意修改 controlPlaneEndpoint: "k8s-company01-master01:6443" 中對應的 master主機名，這里應該不能使用 ip，因為會自動配 tls 證書
cat << EOF > kubeadm-config.yaml
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: v1.14.1
# add the available imageRepository in china
imageRepository: reg01.sky-mobi.com/k8s/k8s.gcr.io
controlPlaneEndpoint: "k8s-company01-master01:6443"
networking:podSubnet: "10.254.0.0/16"
---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
ipvs:minSyncPeriod: 1ssyncPeriod: 10s
mode: ipvs
EOF
預拉取鏡像：
kubeadm config images pull --config kubeadm-config.yaml
master01 初始化：
kubeadm init --config=kubeadm-config.yaml
注意剛開始的打印出的信息，根據(jù)提示，消除掉所有的 WARNING
如果想要重來，使用 kubeadm reset 命令，并且按照提示清空 iptables 和 ipvs 配置，然后重啟 docker 服務。
提示成功后，記錄下最后 join 的所有參數(shù)，用于后面節(jié)點的加入（兩小時內(nèi)有效。用于 worker 節(jié)點的加入）
# 類似：
You can now join any number of the control-plane node running the following command on each as root:Then you can join any number of worker nodes by running the following on each as root:kubeadm join k8s-company01-lb:16443 --token fp0x6g.cwuzedvtwlu1zg1f \--discovery-token-ca-cert-hash sha256:5d4095bc9e4e4b5300abe5a25afe1064f32c1ddcecc02a1f9b0aeee7710c3383
記得執(zhí)行如下命令，以便使用 kubectl訪問集群
mkdir -p $HOME/.kubecp -i /etc/kubernetes/admin.conf $HOME/.kube/configchown $(id -u):$(id -g) $HOME/.kube/config
查看集群狀態(tài)時，coredns pending 沒關系，因為網(wǎng)絡插件還沒裝
# 顯示結(jié)果作為參考
[root@k8s-master01 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-56c9dc7946-5c5z2 0/1 Pending 0 34m
coredns-56c9dc7946-thqwd 0/1 Pending 0 34m
etcd-k8s-master01 1/1 Running 2 34m
kube-apiserver-k8s-master01 1/1 Running 2 34m
kube-controller-manager-k8s-master01 1/1 Running 1 33m
kube-proxy-bl9c6 1/1 Running 2 34m
kube-scheduler-k8s-master01 1/1 Running 1 34m
安裝 calico 網(wǎng)絡插件（在 master01 上操作）
參考：
https://docs.projectcalico.org/v3.6/getting-started/kubernetes/installation/calico下載 yaml 文件( 這里的版本是 v3.6.1，文件源于官網(wǎng)https://docs.projectcalico.org/v3.6/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/typha/calico.yaml 修改過網(wǎng)段和replicas以及 image 地址)# 機房外部使用（有訪問限制，公司自己的公網(wǎng)地址）
curl http://111.1.17.135/yum/scripts/k8s/calico_v3.6.1.yaml -O
# 機房內(nèi)部使用
curl http://192.168.160.200/yum/scripts/k8s/calico_v3.6.1.yaml -O下載下來后，將里面 replicas 值改成1（一個節(jié)點的 master，不需要部署3份 calico）# 需要開啟允許pod 被調(diào)度到master 節(jié)點上（在master01 上執(zhí)行就行）
[root@k8s-company01-master01 ~]# kubectl taint nodes --all node-role.kubernetes.io/master-
node/k8s-company01-master01 untainted# 安裝 calico （卸載是kubectl delete -f calico_v3.6.1.yaml）
[root@k8s-company01-master01 ~]# kubectl apply -f calico_v3.6.1.yaml
configmap/calico-config created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrole.rbac.authorization.k8s.io/calico-node created
clusterrolebinding.rbac.authorization.k8s.io/calico-node created
service/calico-typha created
deployment.apps/calico-typha created
poddisruptionbudget.policy/calico-typha created
daemonset.extensions/calico-node created
serviceaccount/calico-node created
deployment.extensions/calico-kube-controllers created
serviceaccount/calico-kube-controllers created# 至此，所有pod 運行正常（這是3個 master 的顯示結(jié)果的基礎上修改的，僅供參考）
[root@k8s-company01-master01 ~]# kubectl -n kube-system get pod
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-749f7c8df8-knlx4 0/1 Running 0 20s
calico-node-4txj7 0/1 Running 0 21s
calico-typha-646cdc958c-7j948 0/1 Pending 0 21s
coredns-56c9dc7946-944nt 0/1 Running 0 4m9s
coredns-56c9dc7946-nh2sk 0/1 Running 0 4m9s
etcd-k8s-company01-master01 1/1 Running 0 3m26s
kube-apiserver-k8s-company01-master01 1/1 Running 0 3m23s
kube-controller-manager-k8s-company01-master01 1/1 Running 1 3m28s
kube-proxy-8wm4v 1/1 Running 0 4m9s
kube-scheduler-k8s-company01-master01 1/1 Running 1 3m18s# 所有master 節(jié)點都是 ready 狀態(tài)
[root@k8s-company01-master01 ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-company01-master01 Ready master 4m48s v1.14.1
兩臺 worker 節(jié)點加入集群（按照前文做基礎配置，安裝好 docker 和 kubeadm 等）
# 使用之前記錄的 join 命令
kubeadm join k8s-company01-lb:16443 --token fp0x6g.cwuzedvtwlu1zg1f \--discovery-token-ca-cert-hash sha256:5d4095bc9e4e4b5300abe5a25afe1064f32c1ddcecc02a1f9b0aeee7710c3383# 添加成功顯示：
This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.Run 'kubectl get nodes' on the master to see this node join the cluster.### kubectl get nodes 命令在任意 master 節(jié)點執(zhí)行。
如果join 參數(shù)沒有記下來，或者已經(jīng)失效，參考：
http://wiki.sky-mobi.com:8090/pages/viewpage.action?pageId=9079715
#刪除node節(jié)點
#master節(jié)點執(zhí)行以下命令
kubectl get nodes #獲取node名
kubectl drain <node name> --delete-local-data --force --ignore-daemonsets #排空node
kubectl delete node <node name> #刪除node
#node節(jié)點執(zhí)行以下
kubeadm reset
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X #重置iptables
ipvsadm -C #重置IPVS
#如果想再次加入可以執(zhí)行以下命令
kubeadm join --token <token> <master-ip>:<master-port> --discovery-token-ca-cert-hash sha256:<hash>
以下命令可以查看一些狀態(tài)
kubectl get pod -n kube-system -o wide
kubectl get nodes
kubectl get csr
kubectl get componentstatuses
* 以下是監(jiān)控相關，不涉及可以不用安裝
安裝 metrics-server 用于簡單的監(jiān)控，如命令 kubectl top nodes [ root@k8s-master03 ~
]
Error from server
( NotFound
) : the server could not
find the requested resource
( get services http:heapster:
) 這里使用 helm 安裝：
安裝 helm（在 master01 上執(zhí)行）：
wget http://192.168.160.200/yum/scripts/k8s/helm-v2.13.1-linux-amd64.tar.gz
或
wget http://111.1.17.135/yum/scripts/k8s/helm-v2.13.1-linux-amd64.tar.gz
tar xvzf helm-v2.13.1-linux-amd64.tar.gz
mv linux-amd64/helm /usr/local/bin/helm
helm
help 每個節(jié)點執(zhí)行
yum
install -y socat使用微軟的源（阿里的源很長時間都沒更新了！）
helm init --client-only --stable-repo-url http://mirror.azure.cn/kubernetes/charts/
helm repo add incubator http://mirror.azure.cn/kubernetes/charts-incubator/
helm repo updatehelm init --service-account tiller --upgrade -i registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.13.1 --tiller-tls-cert /etc/kubernetes/ssl/tiller001.pem --tiller-tls-key /etc/kubernetes/ssl/tiller001-key.pem --tls-ca-cert /etc/kubernetes/ssl/ca.pem --tiller-namespace kube-system --stable-repo-url http://mirror.azure.cn/kubernetes/charts/ --service-account tiller --history-max 200
給 Tiller 授權（master01 上執(zhí)行）
# 因為 Helm 的服務端 Tiller 是一個部署在 Kubernetes 中 Kube-System Namespace 下 的 Deployment，它會去連接 Kube-Api 在 Kubernetes 里創(chuàng)建和刪除應用。# 而從 Kubernetes 1.6 版本開始，API Server 啟用了 RBAC 授權。目前的 Tiller 部署時默認沒有定義授權的 ServiceAccount，這會導致訪問 API Server 時被拒絕。所以我們需要明確為 Tiller 部署添加授權。# 創(chuàng)建 Kubernetes 的服務帳號和綁定角色kubectl create serviceaccount --namespace kube-system tillerkubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tillerkubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'# 查看是否授權成功
[root@k8s-company01-master01 ~]# kubectl -n kube-system get pods|grep tiller
tiller-deploy-7bf47568d4-42wf5 1/1 Running 0 17s[root@k8s-company01-master01 ~]# helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}[root@k8s-company01-master01 ~]# helm repo list
NAME URL
stable http://mirror.azure.cn/kubernetes/charts/
local http://127.0.0.1:8879/charts
incubator http://mirror.azure.cn/kubernetes/charts-incubator/## 如果要替換倉庫，先移除原先的倉庫
#helm repo remove stable
## 添加新的倉庫地址
#helm repo add stable http://mirror.azure.cn/kubernetes/charts/
#helm repo add incubator http://mirror.azure.cn/kubernetes/charts-incubator/
#helm repo update
使用helm安裝metrics-server（在 master01上執(zhí)行，因為只有 master01裝了 helm）
# 創(chuàng)建 metrics-server-custom.yaml
cat >> metrics-server-custom.yaml <<EOF
image:repository: reg01.sky-mobi.com/k8s/gcr.io/google_containers/metrics-server-amd64tag: v0.3.1
args:- --kubelet-insecure-tls- --kubelet-preferred-address-types=InternalIP,Hostname,InternalDNS,ExternalDNS,ExternalIP
EOF# 安裝 metrics-server（這里 -n 是 name）
[root@k8s-master01 ~]# helm install stable/metrics-server -n metrics-server --namespace kube-system --version=2.5.1 -f metrics-server-custom.yaml[root@k8s-company01-master01 ~]# kubectl get pod -n kube-system | grep metrics
metrics-server-dcbdb9468-c5f4n 1/1 Running 0 21s# 保存 yaml 文件退出后，metrics-server pod 會自動銷毀原來的，拉起一個新的。新 pod 起來后，過一兩分鐘再執(zhí)行kubectl top命令就有結(jié)果了：
[root@k8s-master01 ~]# kubectl top node
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
k8s-master01 513m 6% 7971Mi 8%
使用helm安裝prometheus-operator
# 為方便管理，創(chuàng)建一個單獨的 Namespace monitoring，Prometheus Operator 相關的組件都會部署到這個 Namespace。kubectl create namespace monitoring## 自定義 prometheus-operator 參數(shù)
# helm fetch stable/prometheus-operator --version=5.0.3 --untar
# cat prometheus-operator/values.yaml | grep -v '#' | grep -v ^$ > prometheus-operator-custom.yaml
# 只保留我們要修改 image 的部分，還有使用 https 連接 etcd，例如：
參考：https://fengxsong.github.io/2018/05/30/Using-helm-to-manage-prometheus-operator/cat >> prometheus-operator-custom.yaml << EOF
## prometheus-operator/values.yaml
alertmanager:service:nodePort: 31309type: NodePortalertmanagerSpec:image:repository: reg01.sky-mobi.com/k8s/quay.io/prometheus/alertmanagertag: v0.16.1
prometheusOperator:image:repository: reg01.sky-mobi.com/k8s/quay.io/coreos/prometheus-operatortag: v0.29.0pullPolicy: IfNotPresentconfigmapReloadImage:repository: reg01.sky-mobi.com/k8s/quay.io/coreos/configmap-reloadtag: v0.0.1prometheusConfigReloaderImage:repository: reg01.sky-mobi.com/k8s/quay.io/coreos/prometheus-config-reloadertag: v0.29.0hyperkubeImage:repository: reg01.sky-mobi.com/k8s/k8s.gcr.io/hyperkubetag: v1.12.1pullPolicy: IfNotPresent
prometheus:service:nodePort: 32489type: NodePortprometheusSpec:image:repository: reg01.sky-mobi.com/k8s/quay.io/prometheus/prometheustag: v2.7.1secrets: [etcd-client-cert]
kubeEtcd:serviceMonitor:scheme: httpsinsecureSkipVerify: falseserverName: ""caFile: /etc/prometheus/secrets/etcd-client-cert/ca.crtcertFile: /etc/prometheus/secrets/etcd-client-cert/healthcheck-client.crtkeyFile: /etc/prometheus/secrets/etcd-client-cert/healthcheck-client.key## prometheus-operator/charts/grafana/values.yaml
grafana:service:nodePort: 30579type: NodePortimage:repository: reg01.sky-mobi.com/k8s/grafana/grafanatag: 6.0.2sidecar:image: reg01.sky-mobi.com/k8s/kiwigrid/k8s-sidecar:0.0.13## prometheus-operator/charts/kube-state-metrics/values.yaml
kube-state-metrics:image:repository: reg01.sky-mobi.com/k8s/k8s.gcr.io/kube-state-metricstag: v1.5.0## prometheus-operator/charts/prometheus-node-exporter/values.yaml
prometheus-node-exporter:image:repository: reg01.sky-mobi.com/k8s/quay.io/prometheus/node-exportertag: v0.17.0
EOF## 注：以上的prometheus-operator/charts/grafana/values.yaml 對應項添加了 grafana （按chats 目錄添加的：）
#[root@k8s-master01 ~]# ll prometheus-operator/charts/
#total 0
#drwxr-xr-x 4 root root 114 Apr 1 00:48 grafana
#drwxr-xr-x 3 root root 96 Apr 1 00:18 kube-state-metrics
#drwxr-xr-x 3 root root 110 Apr 1 00:20 prometheus-node-exporter# 創(chuàng)建連接 etcd 的證書secret：
kubectl -n monitoring create secret generic etcd-client-cert --from-file=/etc/kubernetes/pki/etcd/ca.crt --from-file=/etc/kubernetes/pki/etcd/healthcheck-client.crt --from-file=/etc/kubernetes/pki/etcd/healthcheck-client.key helm install stable/prometheus-operator --version=5.0.3 --name=monitoring --namespace=monitoring -f prometheus-operator-custom.yaml## 如果想要刪除重來，可以使用 helm 刪除，指定名字 monitoring
#helm del --purge monitoring
#kubectl delete crd prometheusrules.monitoring.coreos.com
#kubectl delete crd servicemonitors.monitoring.coreos.com
#kubectl delete crd alertmanagers.monitoring.coreos.com重新安裝 不要刪除之前的，再安裝可能會報錯，用 upgrade 就好：
helm upgrade monitoring stable/prometheus-operator --version=5.0.3 --namespace=monitoring -f prometheus-operator-custom.yaml[root@k8s-company01-master01 ~]# kubectl -n monitoring get pod
NAME READY STATUS RESTARTS AGE
alertmanager-monitoring-prometheus-oper-alertmanager-0 2/2 Running 0 29m
monitoring-grafana-7dd5cf9dd7-wx8mz 2/2 Running 0 29m
monitoring-kube-state-metrics-7d98487cfc-t6qqw 1/1 Running 0 29m
monitoring-prometheus-node-exporter-fnvp9 1/1 Running 0 29m
monitoring-prometheus-node-exporter-kczcq 1/1 Running 0 29m
monitoring-prometheus-node-exporter-m8kf6 1/1 Running 0 29m
monitoring-prometheus-node-exporter-mwc4g 1/1 Running 0 29m
monitoring-prometheus-node-exporter-wxmt8 1/1 Running 0 29m
monitoring-prometheus-oper-operator-7f96b488f6-2j7h5 1/1 Running 0 29m
prometheus-monitoring-prometheus-oper-prometheus-0 3/3 Running 1 28m[root@k8s-company01-master01 ~]# kubectl get svc -n monitoring
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
alertmanager-operated ClusterIP None <none> 9093/TCP,6783/TCP 31m
monitoring-grafana NodePort 10.109.159.105 <none> 80:30579/TCP 32m
monitoring-kube-state-metrics ClusterIP 10.100.31.235 <none> 8080/TCP 32m
monitoring-prometheus-node-exporter ClusterIP 10.109.119.13 <none> 9100/TCP 32m
monitoring-prometheus-oper-alertmanager NodePort 10.105.171.135 <none> 9093:31309/TCP 32m
monitoring-prometheus-oper-operator ClusterIP 10.98.135.170 <none> 8080/TCP 32m
monitoring-prometheus-oper-prometheus NodePort 10.96.15.36 <none> 9090:32489/TCP 32m
prometheus-operated ClusterIP None <none> 9090/TCP 31m# 查看有沒有異常告警，alerts里面的第一個Watchdog 是正常的報警，用于監(jiān)控功能探測。
http://172.16.4.200:32489/alerts
http://172.16.4.200:32489/targets#以下是安裝 kubernetes-dashboard，用處不大，正式環(huán)境暫時不裝
#helm install --name=kubernetes-dashboard stable/kubernetes-dashboard --version=1.4.0 --namespace=kube-system --set image.repository=reg01.sky-mobi.com/k8s/k8s.gcr.io/kubernetes-dashboard-amd64,image.tag=v1.10.1,rbac.clusterAdminRole=true#Heapter 已在 Kubernetes 1.13 版本中移除（https://github.com/kubernetes/heapster/blob/master/docs/deprecation.md），推薦使用 metrics-server 與 Prometheus。
總結(jié)
以上是生活随笔 為你收集整理的通过 kubeadm 安装 k8s 1.14.1版本(master 单节点版) 的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。
如果覺得生活随笔 網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔 推薦給好友。
