ProHoster > Ibhulogi > Ulawulo > Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

I-CD yamkelwa njengenkqubo yesoftware yeshishini kwaye sisiphumo sokuzivelela kwendalo kwemigaqo yeCI esekiweyo. Nangona kunjalo, i-CD isenqabile, mhlawumbi ngenxa yobunzima bolawulo kunye noloyiko lokungaphumeleli ukusasazwa okuchaphazela ukufumaneka kwenkqubo.

Iflegi ngumthombo ovulekileyo we-Kubernetes umsebenzisi ojolise ekupheliseni ubudlelwane obubhidayo. Yenza ngokuzenzekelayo ukukhuthazwa kwe-canary deployments usebenzisa i-Istio traffic offset kunye ne-Prometheus metrics ukuhlalutya ukuziphatha kwesicelo ngexesha lokukhutshwa okulawulwayo.

Ngezantsi inyathelo ngesinyathelo isikhokelo sokuseta kunye nokusebenzisa i-Flagger kwi-Google Kubernetes Engine (GKE).

Ukuseta iqela leKubernetes

Uqala ngokudala iqela le-GKE kunye ne-Istio add-on (ukuba awunayo i-akhawunti ye-GCP, ungabhalisa apha - ukufumana iikhredithi zasimahla).

Sayina ungene kwiLifu likaGoogle, wenze iprojekthi, kwaye uvule intlawulo yayo. Faka usetyenziso lomgca womyalelo gcloud kwaye usete iprojekthi yakho nge gcloud init.

Cwangcisa iprojekthi engagqibekanga, indawo yokubala, kunye nendawo (buyisela PROJECT_ID yeprojekthi yakho):

gcloud config set project PROJECT_ID
gcloud config set compute/region us-central1
gcloud config set compute/zone us-central1-a

Yenza inkonzo ye-GKE isebenze kwaye wenze i-cluster ene-HPA kunye ne-Istio add-ons:

gcloud services enable container.googleapis.com
K8S_VERSION=$(gcloud beta container get-server-config --format=json | jq -r '.validMasterVersions[0]')
gcloud beta container clusters create istio 
--cluster-version=${K8S_VERSION} 
--zone=us-central1-a 
--num-nodes=2 
--machine-type=n1-standard-2 
--disk-size=30 
--enable-autorepair 
--no-enable-cloud-logging 
--no-enable-cloud-monitoring 
--addons=HorizontalPodAutoscaling,Istio 
--istio-config=auth=MTLS_PERMISSIVE

Lo myalelo ungasentla uya kudala iphuli ye-node engagqibekanga equka ii-VM ezimbini n1-standard-2 (vCPU: 2, RAM 7,5 GB, disk: 30 GB). Ngokufanelekileyo, kuya kufuneka uwahlukanise amacandelo e-Istio kumthwalo wakho wokusebenza, kodwa akukho ndlela ilula yokuqhuba ii-Istio Pods kwidama elizinikeleyo leendawo. Ukubonakaliswa kwe-Istio kubhekwa njengokufunda kuphela kwaye i-GKE iya kulungisa naluphi na utshintsho, njengokudibanisa kwi-node okanye ukukhupha kwi-pod.

Misela iziqinisekiso ze kubectl:

gcloud container clusters get-credentials istio

Yenza indima yomlawuli weqela ebophelelayo:

kubectl create clusterrolebinding "cluster-admin-$(whoami)" 
--clusterrole=cluster-admin 
--user="$(gcloud config get-value core/account)"

Faka isixhobo somgca womyalelo Helm:

brew install kubernetes-helm

I-Homebrew 2.0 ngoku iyafumaneka Linux.

Yenza iakhawunti yenkonzo kunye nendima yeqela elibophelelayo kwiTiller:

kubectl -n kube-system create sa tiller && 
kubectl create clusterrolebinding tiller-cluster-rule 
--clusterrole=cluster-admin 
--serviceaccount=kube-system:tiller

Yandisa iTiller kwindawo yamagama kube-system:

helm init --service-account tiller

Kuya kufuneka ucinge ngokusebenzisa i-SSL phakathi kweHelm kunye neTiller. Ukuze ufumane inkcazelo engakumbi malunga nokukhusela ufakelo lwakho lweHelm, bona docs.helm.sh

Qinisekisa iisetingi:

kubectl -n istio-system get svc

Emva kwemizuzwana embalwa, i-GCP kufuneka yabele idilesi ye-IP yangaphandle yenkonzo istio-ingressgateway.

Ukuqwalasela i-Istio Ingress Gateway

Yenza idilesi ye-IP engatshintshiyo enegama istio-gatewayusebenzisa idilesi ye-IP yesango le-Istio:

export GATEWAY_IP=$(kubectl -n istio-system get svc/istio-ingressgateway -ojson | jq -r .status.loadBalancer.ingress[0].ip)
gcloud compute addresses create istio-gateway --addresses ${GATEWAY_IP} --region us-central1

Ngoku ufuna isizinda se-intanethi kunye nokufikelela kwirejista yakho ye-DNS. Yongeza ezimbini iirekhodi A (tshintsha example.com kwindawo yakho):

istio.example.com   A ${GATEWAY_IP}
*.istio.example.com A ${GATEWAY_IP}

Qinisekisa ukuba i-wildcard ye-DNS iyasebenza:

watch host test.istio.example.com

Yenza isango le-Istio eliqhelekileyo ukubonelela ngeenkonzo ngaphandle komnatha wenkonzo ngaphezulu kwe-HTTP:

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: public-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
    - port:
        number: 80
        name: http
        protocol: HTTP
      hosts:
        - "*"

Gcina esi sixhobo singasentla njenge public-gateway.yaml uze usisebenzise:

kubectl apply -f ./public-gateway.yaml

Akukho nkqubo yokuvelisa kufuneka ibonelele ngeenkonzo kwi-Intanethi ngaphandle kwe-SSL. Ukukhusela isango lokungena le-Istio nge-cert-manager, CloudDNS kunye neLet Encrypt, nceda ufunde uxwebhu Ifulegi G.K.E.

Ukuhlohla iflegi

I-add-on ye-GKE Istio ayibandakanyi umzekelo we-Prometheus ohlambulula inkonzo ye-telemetry ye-Istio. Ngenxa yokuba i-Flagger isebenzisa i-Istio HTTP metrics ukwenza uhlalutyo lwe-canary, kufuneka usebenzise i-Prometheus yoqwalaselo olulandelayo, olufana nelo eliza kunye ne-schema ye-Istio Helm esemthethweni.

REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master
kubectl apply -f ${REPO}/artifacts/gke/istio-prometheus.yaml

Yongeza indawo yokugcina iFlager Helm:

helm repo add flagger [https://flagger.app](https://flagger.app/)

Yandisa iFlegi kwindawo yamagama istio-systemngokwenza izaziso zeSlack:

helm upgrade -i flagger flagger/flagger 
--namespace=istio-system 
--set metricsServer=http://prometheus.istio-system:9090 
--set slack.url=https://hooks.slack.com/services/YOUR-WEBHOOK-ID 
--set slack.channel=general 
--set slack.user=flagger

Ungayifaka iFlegi kuyo nayiphi na indawo yamagama ukuba nje inokunxibelelana nenkonzo ye-Istio Prometheus kwi-port 9090.

I-Flager inedeshibhodi yaseGrafana yohlalutyo lwe-canary. Faka iGrafana kwindawo yamagama istio-system:

helm upgrade -i flagger-grafana flagger/grafana 
--namespace=istio-system 
--set url=http://prometheus.istio-system:9090 
--set user=admin 
--set password=change-me

Veza iGrafana ngesango elivulekileyo ngokwenza inkonzo yenyani (buyisela example.com kwindawo yakho):

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: grafana
  namespace: istio-system
spec:
  hosts:
    - "grafana.istio.example.com"
  gateways:
    - public-gateway.istio-system.svc.cluster.local
  http:
    - route:
        - destination:
            host: flagger-grafana

Gcina esi sixhobo singasentla njenge-grafana-virtual-service.yaml uze usisebenzise:

kubectl apply -f ./grafana-virtual-service.yaml

Xa ufudukela kwi http://grafana.istio.example.com kumkhangeli zincwadi, kufuneka uqondiswe kwiphepha lokungena le Grafana.

Ukusasaza usetyenziso lwewebhu ngeFlegi

I-Flagger isasaza i-Kubernetes kwaye ikhetha isikali ngaphandle ngokuzenzekelayo (HPA), emva koko idale uluhlu lwezinto (i-Kubernetes deployments, iinkonzo ze-ClusterIP, kunye neenkonzo ze-Istio virtual). Ezi zinto zityhila isicelo kwi-mesh yenkonzo kunye nolawulo lohlalutyo lwe-canary kunye nenkqubela phambili.

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Yenza indawo yovavanyo ngenaliti ye-Istio Sidecar evuliweyo:

REPO=https://raw.githubusercontent.com/stefanprodan/flagger/master
kubectl apply -f ${REPO}/artifacts/namespaces/test.yaml

Yenza usasazo kunye nesixhobo sokukhupha isikali esizenzekelayo:

kubectl apply -f ${REPO}/artifacts/canaries/deployment.yaml
kubectl apply -f ${REPO}/artifacts/canaries/hpa.yaml

Faka inkonzo yovavanyo lovavanyo ukwenza itrafikhi ngexesha lohlalutyo lwe-canary:

helm upgrade -i flagger-loadtester flagger/loadtester 
--namepace=test

Yenza iresource yecanary yesiko (buyisela example.com kwindawo yakho):

apiVersion: flagger.app/v1alpha3
kind: Canary
metadata:
  name: podinfo
  namespace: test
spec:
  targetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: podinfo
  progressDeadlineSeconds: 60
  autoscalerRef:
    apiVersion: autoscaling/v2beta1
    kind: HorizontalPodAutoscaler
    name: podinfo
  service:
    port: 9898
    gateways:
    - public-gateway.istio-system.svc.cluster.local
    hosts:
    - app.istio.example.com
  canaryAnalysis:
    interval: 30s
    threshold: 10
    maxWeight: 50
    stepWeight: 5
    metrics:
    - name: istio_requests_total
      threshold: 99
      interval: 30s
    - name: istio_request_duration_seconds_bucket
      threshold: 500
      interval: 30s
    webhooks:
      - name: load-test
        url: http://flagger-loadtester.test/
        timeout: 5s
        metadata:
          cmd: "hey -z 1m -q 10 -c 2 http://podinfo.test:9898/"

Gcina esi sixhobo singasentla njenge-podinfo-canary.yaml uze usisebenzise:

kubectl apply -f ./podinfo-canary.yaml

Uhlalutyo olungentla, ukuba luphumelele, luya kuqhuba imizuzu emihlanu, ukujonga iimethrikhi ze-HTTP yonke isiqingatha somzuzu. Unokumisela ixesha elincinci elifunekayo ukuze uqinisekise kwaye ukhuthaze ukuthunyelwa kwe-canary usebenzisa le fomula ilandelayo: interval * (maxWeight / stepWeight). Imimandla ye-CRD yaseCanary ibhaliwe apha.

Emva kwemizuzwana embalwa, iFlager iya kudala izinto ze-canary:

# applied 
deployment.apps/podinfo
horizontalpodautoscaler.autoscaling/podinfo
canary.flagger.app/podinfo
# generated 
deployment.apps/podinfo-primary
horizontalpodautoscaler.autoscaling/podinfo-primary
service/podinfo
service/podinfo-canary
service/podinfo-primary
virtualservice.networking.istio.io/podinfo

Vula isikhangeli kwaye uye ku app.istio.example.com, kufuneka ubone inombolo yoguqulelo usetyenziso lwedemo.

Uhlalutyo lwe-canary oluzenzekelayo kunye nokukhuthazwa

I-Flegi iphumeza iluphu yolawulo ethi kancinane ihambise itrafikhi kwi-canary ngelixa ilinganisa iimetrikhi zokusebenza eziphambili ezifana nezinga lempumelelo yesicelo se-HTTP, ubude bexesha lesicelo, kunye nempilo ye-pod. Ngokusekelwe kuhlalutyo lwe-KPI, i-canary ikhuthazwa okanye iphazamisekile, kwaye iziphumo zohlalutyo zipapashwa kwi-Slack.

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Ukusasazwa kweCanary kuqalwa xa enye yezi zinto zilandelayo itshintsha:

  • Sebenzisa iPodSpec (umfanekiso wesiqulathi, umyalelo, izibuko, i-env, njl.)
  • IiMaphu zeConfig zixhonywe njengevolyum okanye zenziwe kwimaphu kwizinto eziguquguqukayo zemo engqongileyo
  • Iimfihlo zixhonywe njengemiqulu okanye ziguqulelwe kwizinto eziguquguqukayo zokusingqongileyo

Sebenzisa i-canary deploy xa uhlaziya umfanekiso wesikhongozeli:

kubectl -n test set image deployment/podinfo 
podinfod=quay.io/stefanprodan/podinfo:1.4.1

I-Flegi ibona ukuba uguqulelo lobeko lutshintshile kwaye iqala ukuyicalula:

kubectl -n test describe canary/podinfo

Events:

New revision detected podinfo.test
Scaling up podinfo.test
Waiting for podinfo.test rollout to finish: 0 of 1 updated replicas are available
Advance podinfo.test canary weight 5
Advance podinfo.test canary weight 10
Advance podinfo.test canary weight 15
Advance podinfo.test canary weight 20
Advance podinfo.test canary weight 25
Advance podinfo.test canary weight 30
Advance podinfo.test canary weight 35
Advance podinfo.test canary weight 40
Advance podinfo.test canary weight 45
Advance podinfo.test canary weight 50
Copying podinfo.test template spec to podinfo-primary.test
Waiting for podinfo-primary.test rollout to finish: 1 of 2 updated replicas are available
Promotion completed! Scaling down podinfo.test

Ngexesha lokuhlalutya, iziphumo zecanary zinokulandelelwa kusetyenziswa iGrafana:

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Nceda uqaphele ukuba ukuba utshintsho olutsha lusetyenziswa ekusetyenzisweni ngexesha lokuhlalutya kwe-canary, ngoko i-Flagger iya kuqalisa kwakhona isigaba sokuhlalutya.

Yenza uluhlu lwazo zonke iicanaries kwiqela lakho:

watch kubectl get canaries --all-namespaces
NAMESPACE   NAME      STATUS        WEIGHT   LASTTRANSITIONTIME
test        podinfo   Progressing   15       2019-01-16T14:05:07Z
prod        frontend  Succeeded     0        2019-01-15T16:15:07Z
prod        backend   Failed        0        2019-01-14T17:05:07Z

Ukuba wenze ukuba izaziso ze-Slack zisebenze, uya kufumana le miyalezo ilandelayo:

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Ukubuyisela umva okuzenzekelayo

Ngexesha lokuhlalutya kwe-canary, unokuvelisa iimpazamo ze-HTTP ze-500 kunye ne-latency yokuphendula okuphezulu ukuze ubone ukuba i-Flagger iya kumisa ukuthunyelwa.

Yenza ipod yovavanyo kwaye wenze oku kulandelayo kuyo:

kubectl -n test run tester 
--image=quay.io/stefanprodan/podinfo:1.2.1 
-- ./podinfo --port=9898
kubectl -n test exec -it tester-xx-xx sh

Ukuvelisa iimpazamo ze-HTTP 500:

watch curl http://podinfo-canary:9898/status/500

Ukulibaziseka:

watch curl http://podinfo-canary:9898/delay/1

Xa inani lokutshekishwa okungaphumelelanga lifikelela kumqobo, i-traffic ibuyiselwa kwi-channel ephambili, i-canary ilinganiswe kwi-zero, kwaye ukuthunyelwa kuphawulwe njengehlulekile.

Iimpazamo zeCanary kunye ne-latency spikes zilogwe njengeziganeko ze-Kubernetes kwaye zifakwe yiFlegi ngefomathi ye-JSON:

kubectl -n istio-system logs deployment/flagger -f | jq .msg

Starting canary deployment for podinfo.test
Advance podinfo.test canary weight 5
Advance podinfo.test canary weight 10
Advance podinfo.test canary weight 15
Halt podinfo.test advancement success rate 69.17% < 99%
Halt podinfo.test advancement success rate 61.39% < 99%
Halt podinfo.test advancement success rate 55.06% < 99%
Halt podinfo.test advancement success rate 47.00% < 99%
Halt podinfo.test advancement success rate 37.00% < 99%
Halt podinfo.test advancement request duration 1.515s > 500ms
Halt podinfo.test advancement request duration 1.600s > 500ms
Halt podinfo.test advancement request duration 1.915s > 500ms
Halt podinfo.test advancement request duration 2.050s > 500ms
Halt podinfo.test advancement request duration 2.515s > 500ms
Rolling back podinfo.test failed checks threshold reached 10
Canary failed! Scaling down podinfo.test

Ukuba wenze ukuba izaziso ze-Slack zisebenze, uya kufumana umyalezo xa umhla obekiweyo ugqithisiwe okanye elona nani liphezulu lokutshekishwa okungaphumelelanga kuhlalutyo lifikelelwe:

Ukuthunyelwa kwe-canary ngokuzenzekelayo kunye neFlager kunye ne-Istio

Ekugqibeleni

Ukuqhuba i-mesh yenkonzo efana ne-Istio ngaphezu kwe-Kubernetes iya kubonelela ngeemetriki ezizenzekelayo, iilogi, kunye neeprotocol, kodwa ukuthunyelwa komsebenzi kuxhomekeke kwizixhobo zangaphandle. I-Flagger ijolise ekutshintsheni oku ngokongeza amandla e-Istio ubonelelo oluqhubekayo.

I-Flagger iyahambelana nayo nayiphi na isisombululo se-Kubernetes CI / CD, kwaye uhlalutyo lwe-canary lunokwandiswa ngokulula kunye iiwebhooks ukwenza inkqubo yokudibanisa / iimvavanyo zokwamkelwa, iimvavanyo zomthwalo, okanye naluphi na olunye uhlolo lwesiko. Kuba iFlegi iyabhengeza kwaye iphendula kwiminyhadala yeKubernetes, ingasetyenziswa kwimibhobho yeGitOps kunye Weave Flux okanye JenkinsX. Ukuba usebenzisa iJenkinsX ungafaka iFlagger ngejx addons.

I-Flegi ixhasiwe Iiweaveworks kwaye ibonelela ngeCanary deployments kwi Weave Cloud. Iprojekthi iyavavanywa kwi-GKE, EKS, kunye nentsimbi engenanto ene-beadm.

Ukuba uneengcebiso zokuphucula iFlegi, nceda ungenise umba okanye iPR kwiGitHub apha stefanprodan/flagger. Igalelo lamkelekile!

Бпасибо Ray Tsang.

umthombo: www.habr.com

Yongeza izimvo