ProHoster > Π‘Π»ΠΎΠ³ > Maamulka > Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

CD-ga waxaa loo aqoonsan yahay inuu yahay ku-dhaqanka softiweerka ganacsiga waana natiijada horumarka dabiiciga ah ee mabaadi'da CI ee la aasaasay. Si kastaba ha ahaatee, CD-ga wali waa naadir, laga yaabee inay sabab u tahay kakanaanta maamulka iyo cabsida geynta fashilantay ee saameeya helitaanka nidaamka.

Calanka waa il furan oo ku shaqeeya Kubernetes kaas oo ujeedadiisu tahay in la baabi'iyo cilaaqaadka jahawareer leh. Waxay otomaatig ka dhigtaa dhiirigelinta geynta kanariyada iyadoo la isticmaalayo istio trafic offset iyo Prometheus metrics si ay u falanqeyso habdhaqanka codsiga inta lagu jiro duubista la maareeyay.

Hoos waxaa ah tillaabo tillaabo tilmaan u ah dejinta iyo adeegsiga Flagger ee Google Kubernetes Engine (GKE).

Dejinta kooxda Kubernetes

Waxaad ku bilaabaysaa inaad abuurto koox GKE ah istio add-on (haddii aanad lahayn akoon GCP, waad iska qori kartaa halkan - si aad u hesho credits bilaash ah).

Soo gal Google Cloud, samee mashruuc, oo awood biilasha. Ku rakib utility line amarka gcloud oo ku deji mashruucaaga gcloud init.

Deji mashruuca caadiga ah, aagga xisaabinta, iyo aagga (beddel PROJECT_ID mashruucaaga):

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

Daar adeega GKE oo samee koox leh HPA iyo 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

Amarka kore wuxuu abuuri doonaa barkad node ah oo ay ku jiraan laba VMs n1-standard-2 (vCPU: 2, RAM 7,5 GB, disk: 30 GB). Fikrad ahaan, waa inaad ka soocdo qaybaha Istio culeyska shaqadaada, laakiin ma jirto hab sahlan oo lagu socodsiiyo Istio Pods barkad nood ah oo go'an. Muujinta Istio waxa loo tixgaliyaa in la akhriyo-kaliya GKE-na waxa ay dib u dhigi doontaa wixii isbedel ah, sida ku xidhidhiyaha noodhka ama ka go'ida boodhka.

U deji warqadaha aqoonsiga kubectl:

gcloud container clusters get-credentials istio

Samee xidhitaan door maamule kooxeed:

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

Ku rakib qalabka khadka taliska Helm:

brew install kubernetes-helm

Homebrew 2.0 hadda sidoo kale waa diyaar Linux.

U samee akoon adeeg iyo door ku xidhitaan kooxeed Tiller:

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

Ku balaadhi Tiller meel magaceed ah kube-system:

helm init --service-account tiller

Waa inaad tixgelisaa inaad isticmaasho SSL inta u dhaxaysa Helm iyo Tiller. Wixii macluumaad dheeraad ah oo ku saabsan ilaalinta rakibaada Helm, eeg docs.helm.sh

Xaqiiji dejinta

kubectl -n istio-system get svc

Dhawr ilbiriqsi ka dib, GCP waa in uu u qoondeeyaa ciwaanka IP-ga dibadda ee adeega istio-ingressgateway.

Habaynta Kadinka Ingress-ka ee Istio

Samee cinwaan IP taagan oo magac leh istio-gatewayAdigoo isticmaalaya ciwaanka IP-ga ee Istio gateway:

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

Hadda waxaad u baahan tahay bogga internetka oo aad gasho diiwaan-hayaha DNS. Ku dar laba diiwaan A (bedel example.com boggaaga):

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

Xaqiiji in kaarka duurjoogta ah ee DNS uu shaqeynayo:

watch host test.istio.example.com

Samee gateway istio guud si aad u bixiso adeegyo ka baxsan mesh adeega 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:
        - "*"

U keydi kheyraadka sare sida public-gateway.yaml ka dibna ku isticmaal:

kubectl apply -f ./public-gateway.yaml

Nidaam wax-soo-saarku waa inuu ku bixiyaa adeegyada internetka SSL la'aanteed. Si aad u ilaaliso albaabka Istio soo galitaanka maamulaha shahaadada, CloudDNS iyo Aynu Sirinno, fadlan akhri dukumeenti Calanka G.K.E.

Rakibaadda Calanka

Ku-darka GKE Istio kuma jiro tusaale Prometheus oo nadiifiya adeegga telemetry ee Istio. Sababtoo ah Flagger wuxuu isticmaalaa Istio HTTP mitir si uu u sameeyo falanqaynta canary, waxaad u baahan tahay inaad geyso qaabka Prometheus ee soo socda, oo la mid ah midka la socda qorshaha rasmiga ah ee Istio Helm.

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

Kudar kaydka calanka Helm:

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

Ku fidi calanka ilaa magaca istio-systemadoo awood u siinaya ogeysiisyada Slack:

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

Waxaad ku rakibi kartaa Flagger meel kasta oo magac ah ilaa inta ay la xiriiri karto adeegga Istio Prometheus ee dekedda 9090.

Flagger wuxuu leeyahay dashboard-ka Grafana ee falanqaynta canary. Ku rakib Grafana booska magaca 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

U soo bandhig Grafana albaab furan adiga oo abuuraya adeeg macmal ah (beddel example.com boggaaga):

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

U keydi kheyraadka kor ku xusan grafana-virtual-service.yaml ka dibna isticmaal:

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

Markaad u guurto http://grafana.istio.example.com browserka, waa in lagu jiheeyaa bogga gelitaanka Grafana.

Ku daabulida codsiyada shabakadda ee Flagger

Flagger wuxuu hawlgeliyaa Kubernetes wuxuuna si toos ah u miisaamaa si toos ah (HPA), dabadeed wuxuu abuuraa shay taxane ah (Diirista Kubernetes, Adeegyada ClusterIP, iyo adeegyada Istio). Walxahani waxay arjiga u soo bandhigaan mesh-ka adeega waxayna xakameeyaan falanqaynta iyo horumarka canary-ga.

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Samee meel magac tijaabo ah oo leh Istio Sidecar irbad karti leh:

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

Samee geyn iyo qalab si toos ah loo cabbiro:

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

Geli adeega culayska tijaabada si aad u abuurto taraafikada inta lagu jiro falanqaynta canary:

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

Samee kheyraad canary gaar ah (bedel example.com boggaaga):

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/"

U keydi kheyraadka kor ku xusan sida podinfo-canary.yaml ka dibna isticmaal:

kubectl apply -f ./podinfo-canary.yaml

Falanqaynta sare, haddii lagu guuleysto, waxay socon doontaa shan daqiiqo, hubinta mitirka HTTP nuskii daqiiqo kasta. Waxaad go'aamin kartaa wakhtiga ugu yar ee loo baahan yahay si aad u ansixiso oo aad u dhiirigeliso keenista canary adigoo isticmaalaya qaacidada soo socota: interval * (maxWeight / stepWeight). Goobaha Canary CRD waa la diiwaangeliyay halkan.

Dhowr ilbiriqsi ka dib, Flagger wuxuu abuuri doonaa walxaha 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

Fur browser oo tag app.istio.example.com, waa inaad aragto lambarka nooca barnaamijyada demo.

Falanqaynta tooska ah iyo dhiirrigelinta canary

Flagger wuxuu fuliyaa wareegga kontoroolka kaas oo si tartiib tartiib ah ugu dhaqaaqa taraafikada canary-ga isagoo cabbiraya cabbirada waxqabadka muhiimka ah sida heerka guusha codsiga HTTP, celceliska muddada codsiga, iyo caafimaadka podska. Iyada oo ku saleysan falanqaynta KPI, canary-ga waa la dallacsiiyay ama la hakiyaa, natiijooyinka falanqaynta waxaa loo daabacay Slack.

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Soo dejinta Canary waxay kicisaa marka mid ka mid ah walxahan soo socda ay isbedelaan:

  • Geli PodSpec (sawirka weelka, taliska, dekedaha, env, iwm.)
  • ConfigMaps waxaa lagu rakibay sida mug ahaan ama loo habeeyey doorsoomayaasha deegaanka
  • Siraha waxaa loo dhejiyaa mug ahaan ama waxaa loo rogaa doorsoomayaasha deegaanka

Orod kanary geynta marka aad cusboonaysiinayso sawirka weelka:

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

Flagger waxa uu ogaaday in nooca dirida uu isbedelay oo bilaabay falanqayntiisa:

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

Inta lagu jiro falanqaynta, natiijooyinka canary-ga waxaa lagula socon karaa iyadoo la adeegsanayo Grafana:

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Fadlan la soco in haddii isbeddello cusub lagu dabaqo hawlgelinta inta lagu jiro falanqaynta canary, markaas Flagger wuxuu dib u bilaabi doonaa marxaladda falanqaynta.

Samee liis dhammaan canary-ga ku jira kooxdaada:

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

Haddii aad karti u yeelatay ogeysiisyada Slack, waxaad heli doontaa fariimaha soo socda:

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Dib u laabasho toos ah

Inta lagu jiro falanqaynta canary, waxaad dhalin kartaa khaladaadka HTTP 500 ee synthetic iyo daahitaanka jawaabta sare si aad u aragto haddii Flagger uu joojin doono hawlgelinta.

Samee sanduuq tijaabo ah oo ku samee waxyaabaha soo socda:

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

Abuurista khaladaadka HTTP 500:

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

Jiilka dib u dhaca:

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

Marka tirada jeegaga guuldarraystay ay gaadho marinka, taraafikada ayaa dib loogu celinayaa kanaalka koowaad, kanary-ga waxa la miisaamayaa eber, diristiina waxa loo calaamadeeyay mid fashilmay.

Khaladaadka Canary-ga iyo daahitaanka daahitaanka waxaa loo diiwaan galiyay sidii dhacdooyinka Kubernetes oo uu u galiyay Flagger qaab JSON ah:

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

Haddii aad karti u siisay ogaysiisyada Slack, waxaad heli doontaa fariin marka wakhtiga kama dambaysta ahi dhaafo ama tirada ugu badan ee jeegaga guul daraystay ee falanqaynta la gaadho:

Si toos ah u geynta kanariyada oo wata Flagger iyo Istio

Gabagabada

Ku shaqeynta mesh adeega sida Istio marka lagu daro Kubernetes waxay bixin doontaa cabbirada otomaatiga ah, logs, iyo borotokoollada, laakiin keenista culeyska shaqada ayaa wali ku xiran aaladaha dibadda. Flagger wuxuu higsanayaa inuu tan beddelo isagoo ku daraya awoodaha Istio sahayda horusocod leh.

Flagger wuxuu la jaan qaadayaa xal kasta oo Kubernetes CI / CD ah, iyo falanqaynta canary si fudud ayaa loo kordhin karaa webhoos si loo sameeyo imtixaanada is dhexgalka/aqbalaadda nidaamka, imtixaanada culayska, ama jeegag kasta oo caado ah. Maadaama Flagger uu yahay mid caddaynaya oo ka jawaabaya dhacdooyinka Kubernetes, waxaa loo isticmaali karaa dhuumaha GitOps oo ay weheliso Weave Flux ama JenkinsX. Haddii aad isticmaalayso JenkinsX waxaad ku rakibi kartaa Flagger leh jx addons.

Calanka ayaa taageeray Weaveworks oo ay siisaa in la geeyo canary gudaha Weave Cloud. Mashruuca waxaa lagu tijaabiyay GKE, EKS, iyo biro qaawan oo leh kubeadm.

Haddii aad hayso talooyin aad ku horumarinayso Flagger, fadlan ku soo gudbi arrin ama PR GitHub at stefanprodan/flagger. Wax ku biirinta ayaa aad loo soo dhawaynayaa!

Бпасибо Ray Tsang.

Source: www.habr.com

Add a comment