kubernetes各版本離線安裝包
安裝k8s 強勢插播廣告
三步安裝,很少說node
安裝helm, 推薦生產環境用helm安裝,能夠調參
<!--more-->
release地址linux
如我使用的2.9.1版本git
yum install -y socat # 這個不裝會報錯
[root@istiohost ~]# wget https://storage.googleapis.com/kubernetes-helm/helm-v2.9.1-linux-amd64.tar.gz [root@istiohost ~]# tar zxvf helm-v2.9.1-linux-amd64.tar.gz [root@istiohost ~]# cp linux-amd64/helm /usr/bin
先建立一個service account 把管理員權限給helm:github
[root@istiohost ~]# cat helmserviceaccount.yaml apiVersion: v1 kind: ServiceAccount metadata: name: tiller namespace: kube-system --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: name: tiller-clusterrolebinding subjects: - kind: ServiceAccount name: tiller namespace: kube-system roleRef: kind: ClusterRole name: cluster-admin apiGroup: ""
kubectl create -f helmserviceaccount.yaml
安裝helm 服務端 tiller :算法
helm init --service-account tiller # 若是已安裝更新加 --upgrade 參數 helm list #沒任何返回表示成功
安裝istio
curl -L https://git.io/getLatestIstio | sh - cd istio-1.0.0/ export PATH=$PWD/bin:$PATH
helm 2.10.0之前的版本須要裝一下CRD:api
kubectl apply -f install/kubernetes/helm/istio/templates/crds.yaml kubectl apply -f install/kubernetes/helm/istio/charts/certmanager/templates/crds.yaml
安裝istio, 因爲你沒有LB因此用NodePort代替:瀏覽器
helm install install/kubernetes/helm/istio --name istio --namespace istio-system --set gateways.istio-ingressgateway.type=NodePort --set gateways.istio-egressgateway.type=NodePort
安裝成功:app
[root@istiohost istio-1.0.0]# kubectl get pod -n istio-system NAME READY STATUS RESTARTS AGE istio-citadel-7d8f9748c5-ntqnp 1/1 Running 0 5m istio-egressgateway-676c8546c5-2w4cq 1/1 Running 0 5m istio-galley-5669f7c9b-mkxjg 1/1 Running 0 5m istio-ingressgateway-5475685bbb-96mbr 1/1 Running 0 5m istio-pilot-5795d6d695-gr4h4 2/2 Running 0 5m istio-policy-7f945bf487-gkpxr 2/2 Running 0 5m istio-sidecar-injector-d96cd9459-674pk 1/1 Running 0 5m istio-statsd-prom-bridge-549d687fd9-6cbzs 1/1 Running 0 5m istio-telemetry-6c587bdbc4-jndjn 2/2 Running 0 5m prometheus-6ffc56584f-98mr9 1/1 Running 0 5m [root@istiohost istio-1.0.0]# kubectl get svc -n istio-system NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE istio-citadel ClusterIP 10.108.253.89 <none> 8060/TCP,9093/TCP 5m istio-egressgateway NodePort 10.96.151.14 <none> 80:30830/TCP,443:30038/TCP 5m istio-galley ClusterIP 10.102.83.130 <none> 443/TCP,9093/TCP 5m istio-ingressgateway NodePort 10.99.194.13 <none> 80:31380/TCP,443:31390/TCP,31400:31400/TCP,15011:31577/TCP,8060:30037/TCP,15030:31855/TCP,15031:30775/TCP 5m istio-pilot ClusterIP 10.101.4.143 <none> 15010/TCP,15011/TCP,8080/TCP,9093/TCP 5m istio-policy ClusterIP 10.106.221.68 <none> 9091/TCP,15004/TCP,9093/TCP 5m istio-sidecar-injector ClusterIP 10.100.5.170 <none> 443/TCP 5m istio-statsd-prom-bridge ClusterIP 10.107.28.242 <none> 9102/TCP,9125/UDP 5m istio-telemetry ClusterIP 10.105.66.20 <none> 9091/TCP,15004/TCP,9093/TCP,42422/TCP 5m prometheus ClusterIP 10.103.128.152 <none> 9090/TCP
reviews服務有三個版本:curl
數據平面:ide
安裝應用:
kubectl apply -f <(istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml)
安裝完成:
[root@istiohost istio-1.0.0]# kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE details ClusterIP 10.104.66.31 <none> 9080/TCP 2m kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 4h productpage ClusterIP 10.109.68.13 <none> 9080/TCP 2m ratings ClusterIP 10.99.55.110 <none> 9080/TCP 2m reviews ClusterIP 10.102.19.129 <none> 9080/TCP 2m [root@istiohost istio-1.0.0]# kubectl get pods NAME READY STATUS RESTARTS AGE details-v1-fc9649d9c-dpnlp 2/2 Running 0 2m productpage-v1-58845c779c-7g8th 2/2 Running 0 2m ratings-v1-6cc485c997-fb7nh 2/2 Running 0 2m reviews-v1-76987687b7-x5n7z 2/2 Running 0 2m reviews-v2-86749dcd5-xchzb 2/2 Running 0 2m reviews-v3-7f4746b959-nthrq 2/2 Running 0 2m
建立一個gateway,這是爲了集羣外能夠訪問
kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
瀏覽器訪問url:
47.254.28.88是個人節點ip,使用nodeport模式
http://47.254.28.88:31380/productpage
連續點擊三次,你會發現右邊沒星星-> 黑星星-> 紅星星切換,對應三個版本的review,默認策略是輪詢
建立destination rules, 配置路由訪問規則,如今仍是輪詢
kubectl apply -f samples/bookinfo/networking/destination-rule-all.yaml
把全部路由切換到v1版本
kubectl apply -f samples/bookinfo/networking/virtual-service-all-v1.yaml
這樣執行完後,無論怎麼刷頁面,咱們都看不到星星,由於v1版本沒星
能夠看到destination是這樣的:
http: - route: - destination: host: details subset: v1
試想如此咱們作版本切換將是何等簡單
kubectl apply -f samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml
你會發現用jason用戶登陸就能看到黑星星,而其它方式看到的頁面都是無星星
由於這個user走了v2版本,能不強大? 那固然還能根據header什麼的作路由了,就很少說了
http: - match: - headers: end-user: exact: jason route: - destination: host: reviews subset: v2 - route: - destination: host: reviews subset: v1
kubectl apply -f samples/bookinfo/networking/virtual-service-all-v1.yaml kubectl apply -f samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml
假設代碼裏有個bug,用戶jason, reviews:v2 訪問ratings時會卡10s, 咱們任然但願端到端的測試能正常走完
kubectl apply -f samples/bookinfo/networking/virtual-service-ratings-test-delay.yaml
注入錯誤讓jason用戶有個7s的延遲
hosts: - ratings http: - fault: delay: fixedDelay: 7s percent: 100 match: - headers: end-user: exact: jason route: - destination: host: ratings subset: v1 - route: - destination: host: ratings subset: v1
這時訪問頁面顯然會出錯,由於咱們但願7s內能返回,這樣咱們就發現了一個延遲的bug
Error fetching product reviews! Sorry, product reviews are currently unavailable for this book.
因此咱們就可能經過故障注入去發現這些異常現象
咱們先把50%流量發送給reviews:v1 50%流量發送給v3,而後再把100%的流量都切給v3
kubectl apply -f samples/bookinfo/networking/virtual-service-all-v1.yaml
此時不論刷幾遍,都沒有星星
kubectl apply -f samples/bookinfo/networking/virtual-service-reviews-50-v3.yaml
- route: - destination: host: reviews subset: v1 weight: 50 - destination: host: reviews subset: v3 weight: 50
此時一會有星,一會沒星,可是已經不是輪詢算法了
kubectl apply -f samples/bookinfo/networking/virtual-service-reviews-v3.yaml
這時無論怎麼刷都是紅心了
掃碼關注sealyun探討可加QQ羣:98488045