I-ProHoster > Π‘Π»ΠΎΠ³ > Ukuphatha > Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

I-CD ibonwa njengomkhuba wesofthiwe yebhizinisi futhi iwukuguquguquka okungokwemvelo kwezimiso ezimisiwe ze-CI. Kodwa-ke, i-CD iseyivelakancane, mhlawumbe ngenxa yobunzima bokuphatha kanye nokwesaba ukuthunyelwa okuhlulekile okuthinta ukutholakala kwesistimu.

Hlaba umkhosi iwumthombo ovulekile we-Kubernetes opharetha ohlose ukuqeda ubudlelwano obudidayo. Izenzela ngokuzenzakalelayo ukuphromothwa kokufakwa kwe-canary isebenzisa i-Istio traffic offsets kanye namamethrikhi e-Prometheus ukuze ihlaziye ukuziphatha kohlelo lokusebenza phakathi nokukhishwa okuphethwe.

Ngezansi umhlahlandlela wesinyathelo ngesinyathelo sokusetha nokusebenzisa i-Flagger ku-Google Kubernetes Engine (GKE).

Isetha iqoqo le-Kubernetes

Uqala ngokwakha iqoqo le-GKE ngesengezo se-Istio (uma ungenayo i-akhawunti ye-GCP, ungabhalisa lapha - ukuthola amakhredithi mahhala).

Ngena ngemvume ku-Google Cloud, dala iphrojekthi, futhi uvule inkokhelo yayo. Faka insiza yomugqa womyalo gcloud futhi ulungiselele iphrojekthi yakho nge gcloud init.

Setha iphrojekthi ezenzakalelayo, indawo yokubala, nendawo (shintshanisa PROJECT_ID kuphrojekthi yakho):

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

Nika amandla isevisi ye-GKE futhi udale iqoqo elinezengezo ze-HPA ne-Istio:

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

Umyalo ongenhla uzodala i-node pool ezenzakalelayo ehlanganisa ama-VM amabili n1-standard-2 (vCPU: 2, RAM 7,5 GB, idiski: 30 GB). Ngokufanelekile, izingxenye ze-Istio kufanele zihlukaniswe nemithwalo yazo yokusebenza, kodwa ayikho indlela elula yokusebenzisa ama-pods e-Istio echibini le-node elizinikele. Ukubonakaliswa kwe-Istio kubhekwa njengokufunda kuphela, futhi i-GKE izobuyisela noma yiziphi izinguquko ezifana nokubophezela ku-node noma ukukhipha ku-pod.

Setha imininingwane ye kubectl:

gcloud container clusters get-credentials istio

Dala indima yomlawuli weqoqo:

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

Faka ithuluzi lomugqa womyalo Helm:

brew install kubernetes-helm

I-Homebrew 2.0 manje isiyatholakala futhi Linux.

Dala i-akhawunti yesevisi kanye neqhaza elibophezela uTiller:

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

Nweba iTiller endaweni yamagama kube-system:

helm init --service-account tiller

Kufanele ucabange ukusebenzisa i-SSL phakathi kweHelm neTiller. Ukuze uthole ulwazi olwengeziwe mayelana nokuvikela ukufakwa kwakho kwe-Helm, bheka docs.helm.sh

Qinisekisa izilungiselelo:

kubectl -n istio-system get svc

Ngemva kwemizuzwana embalwa i-GCP kufanele yabele ikheli le-IP langaphandle kusevisi istio-ingressgateway.

Ukusetha i-Istio Ingress Gateway

Dala ikheli le-IP elimile negama istio-gatewayusebenzisa ikheli le-IP lesango 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

Manje udinga isizinda se-inthanethi kanye nokufinyelela kusibhalisi sakho se-DNS. Engeza amarekhodi amabili A (shintsha example.com esizindeni sakho):

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

Qinisekisa ukuthi i-wildcard ye-DNS iyasebenza:

watch host test.istio.example.com

Dala isango elijwayelekile le-Istio ukuze unikeze amasevisi ngaphandle kwe-mesh yesevisi nge-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:
        - "*"

Londoloza insiza engenhla njenge-public-gateway.yaml bese uyayisebenzisa:

kubectl apply -f ./public-gateway.yaml

Alukho uhlelo lokukhiqiza okufanele luhlinzeke ngamasevisi ku-inthanethi ngaphandle kwe-SSL. Ukuze uvikele isango lakho lokungena le-Istio nge-cert-manager, CloudDNS kanye ne-Let's Encrypt, sicela ufunde imibhalo Umalagi G.K.E.

Ukufakwa komaka

Isengezo se-GKE Istio asifaki isibonelo se-Prometheus esihlanza isevisi ye-Istio telemetry. Njengoba i-Flagger isebenzisa amamethrikhi e-Istio HTTP ukwenza ukuhlaziya kwe-canary, udinga ukusebenzisa ukulungiselelwa kwe-Prometheus okulandelayo, okufana nalokhu okuza ne-schema ye-Istio Helm esemthethweni.

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

Engeza inqolobane ye-Flager Helm:

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

Nweba ifulegi libe yindawo yamagama istio-systemngokunika amandla izaziso ze-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

Ungakwazi ukufaka i-Flagger kunoma iyiphi indawo yamagama inqobo nje uma ikwazi ukuxhumana nesevisi ye-Istio Prometheus ku-port 9090.

U-Flager unedeshibhodi ye-Grafana yokuhlaziya i-canary. Faka i-Grafana endaweni 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 i-Grafana ngesango elivuliwe ngokudala isevisi ebonakalayo (shintshanisa example.com esizindeni sakho):

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

Londoloza insiza engenhla njenge-grafana-virtual-service.yaml bese uyayisebenzisa:

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

Uma uya http://grafana.istio.example.com Isiphequluli sakho kufanele sikuqondise kabusha ekhasini lokungena le-Grafana.

Isebenzisa izinhlelo zokusebenza zewebhu nge-Flagger

I-Flager isebenzisa i-Kubernetes futhi, uma kunesidingo, i-autoscaling evundlile (HPA), bese idala uchungechunge lwezinto (ukuthunyelwa kwe-Kubernetes, amasevisi e-ClusterIP kanye nezinsizakalo ezibonakalayo ze-Istio). Lezi zinto ziveza uhlelo lokusebenza ku-mesh yesevisi futhi zilawula ukuhlaziya nokukhushulwa kwe-canary.

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Dala indawo yokuhlola usebenzisa i-Istio Sidecar enikwe amandla:

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

Dala ukuthunyelwa kanye nethuluzi lokukala elivundlile elizenzakalelayo le-pod:

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

Sebenzisa isevisi yokuhlola umthwalo ukuze ukhiqize ithrafikhi phakathi nokuhlaziywa kwe-canary:

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

Dala insiza ye-canary yangokwezifiso (shintshanisa example.com esizindeni sakho):

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

Londoloza insiza engenhla njenge-podinfo-canary.yaml bese uyayisebenzisa:

kubectl apply -f ./podinfo-canary.yaml

Ukuhlaziya okungenhla, uma kuphumelele, kuzosebenza imizuzu emihlanu, kubheka amamethrikhi e-HTTP njalo ngesigamu semizuzu. Ungakwazi ukunquma ubuncane besikhathi esidingekayo ukuze uhlole futhi ukhuthaze ukuthunyelwa kwe-canary usebenzisa ifomula elandelayo: interval * (maxWeight / stepWeight). Izinkambu ze-Canary CRD zibhaliwe lapha.

Ngemuva kwemizuzwana embalwa, i-Flagger izodala 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 isiphequluli sakho bese uya ku app.istio.example.com, kufanele ubone inombolo yenguqulo izicelo zedemo.

Ukuhlaziywa kwe-canary okuzenzakalelayo nokukhuthazwa

I-Flager isebenzisa iluphu yokulawula ehambisa kancane kancane ithrafikhi ku-canary kuyilapho ikala izinkomba zokusebenza ezibalulekile ezifana nezinga lempumelelo yesicelo se-HTTP, isilinganiso sobude besikhathi sokucela, kanye nempilo ye-pod. Ngokusekelwe ekuhlaziyweni kwe-KPI, i-canary iyakhuthazwa noma iyanqanyulwa, futhi imiphumela yokuhlaziya ishicilelwa ku-Slack.

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Ukuthunyelwa kwe-Canary kuqalwa lapho enye yezinto ezilandelayo ishintsha:

  • Sebenzisa i-PodSpec (isithombe sesitsha, umyalo, izimbobo, i-env, njll.)
  • I-ConfigMaps ifakwe njengevolumu noma iguqulelwe kokuguquguqukayo kwemvelo
  • Izimfihlo zifakwa njengevolumu noma ziguqulelwe kokuguquguqukayo kwemvelo

Qalisa ukusetshenziswa kwe-canary lapho ubuyekeza isithombe sesiqukathi:

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

I-Flager ithola ukuthi inguqulo yokusebenzisa ishintshile futhi iqala ukuyihlaziya:

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

Ngesikhathi sokuhlaziya, imiphumela ye-canary ingagadwa kusetshenziswa i-Grafana:

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Sicela uqaphele: uma izinguquko ezintsha zisetshenziswa ekusetshenzisweni phakathi nokuhlaziywa kwe-canary, i-Flager izoqala kabusha isigaba sokuhlaziya.

Yenza uhlu lwawo wonke ama-canaries kuqoqo 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

Uma unike amandla izaziso ze-Slack, uzothola imilayezo elandelayo:

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Ukubuyisela emuva okuzenzakalelayo

Ngesikhathi sokuhlaziya i-canary, ungakhiqiza amaphutha okwenziwa e-HTTP 500 kanye nokubambezeleka kwempendulo ephezulu ukuze uhlole ukuthi i-Flagger izomisa yini ukusetshenziswa.

Dala i-pod yokuhlola bese wenza okulandelayo 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

Ikhiqiza amaphutha e-HTTP 500:

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

Ukukhiqiza ukubambezeleka:

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

Uma inani lokuhlola okuhlulekile lifinyelela emngceleni, ithrafikhi iphindiselwa emuva esiteshini esiyinhloko, i-canary ilinganiswa ku-zero, futhi ukuthunyelwa kumakwa njengokuhlulekile.

Amaphutha e-Canary kanye ne-latency spikes kufakwe njengemicimbi ye-Kubernetes futhi kurekhodwa i-Flagger ngefomethi 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

Uma unike amandla izaziso ze-Slack, uzothola umlayezo lapho umnqamulajuqu wokugcwalisa noma wokufinyelela inombolo enkulu yezibuyekezo ezihlulekile ekuhlaziyeni weqiwe:

Ukuthunyelwa okuzenzakalelayo kwe-canary nge-Flagger ne-Istio

Ekuphethweni

Ukusebenzisa i-mesh yesevisi efana ne-Istio phezu kwe-Kubernetes kuzohlinzeka ngamamethrikhi azenzakalelayo, amalogi, namalogi, kodwa ukuthunyelwa kwemithwalo yomsebenzi kusancike kumathuluzi angaphandle. I-Flager ihlose ukushintsha lokhu ngokwengeza amakhono e-Istio ukulethwa okuqhubekayo.

I-Flager iyahambisana nanoma yisiphi isisombululo se-CI/CD se-Kubernetes, futhi ukuhlaziywa kwe-canary kunganwetshwa kalula ama-webhooks ukwenza ukuhlolwa kokuhlanganiswa kwesistimu/ukwamukela, ukuhlolwa kokulayisha nanoma yiziphi ezinye izivivinyo zangokwezifiso. Ngenxa yokuthi i-Flager iyadalula futhi iphendula imicimbi ye-Kubernetes, ingasetshenziswa kumapayipi e-GitOps kanye Faka i-Flux noma I-JenkinsX. Uma usebenzisa i-JenkinsX, ungafaka i-Flagger ngezengezo ze-jx.

Ukuhlaba umkhosi kusekelwe Ama-Weaveworks futhi inikeza ukuthunyelwa kwe-canary ku Weave Cloud. Iphrojekthi ihlolwe ku-GKE, EKS kanye nensimbi engenalutho nge-beadm.

Uma uneziphakamiso zokuthuthukisa i-Flager, sicela uthumele inkinga noma i-PR ku-GitHub kokuthi i-stefanprodan/flagger. Iminikelo yamukelekile!

Бпасибо Ray Tsang.

Source: www.habr.com

Engeza amazwana