{"id":90373,"date":"2020-07-31T13:42:12","date_gmt":"2020-07-31T11:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts"},"modified":"2020-07-31T13:42:12","modified_gmt":"2020-07-31T11:42:12","slug":"canary-deployment-v-kubernetes-2-argo-rollouts","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","title":{"rendered":"Canary Deployment \u00een Kubernetes #2: Argo Rollouts","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<h4 id=\"my-budem-ispolzovat-k8s-nativnyy-kontroller-razvertyvaniya-argo-rollouts-i-gitlabci-dlya-zapuska-canary-deploya-v-kubernetes\">Vom utiliza un controller nativ k8s pentru implementare Argo Rollouts \u0219i GitlabCI pentru a lansa Canary deployment \u00een Kubernetes<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/0748c0dc9a71e59b8a42f39481d365da.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><em><noindex><a rel=\"nofollow\" href=\"https:\/\/unsplash.com\/photos\/V41PulGL1z0\">https:\/\/unsplash.com\/photos\/V41PulGL1z0<\/a><\/noindex><\/em><\/p>\n<p><\/p>\n<h3 id=\"stati-etogo-cikla\">Articolele acestui ciclu<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">Canary Deployment \u00een Kubernetes #1: Gitlab CI<\/a><\/noindex><\/li>\n<li>(Aceast\u0103 articol)<\/li>\n<li>Canary Deployment folosind Istio<\/li>\n<li>Canary Deployment folosind Jenkins-X Istio Flagger<\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3 id=\"canary-deployment\">Canary Deployment<\/h3>\n<p><\/p>\n<p>Sper\u0103m c\u0103 a\u021bi citit <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">prima parte<\/a><\/noindex>, unde am explicat pe scurt ce sunt Canary Deployments. De asemenea, am ar\u0103tat cum s\u0103 le implement\u0103m folosind resursele standard Kubernetes.<\/p>\n<p><\/p>\n<h3 id=\"argo-rollouts\">Argo Rollouts<\/h3>\n<p><\/p>\n<p>Argo Rollouts este un controller de implementare nativ Kubernetes. Ofer\u0103 CRD (Custom Resource Definition) pentru Kubernetes. Gra\u021bie lui, putem utiliza o nou\u0103 entitate: <code>Rollout<\/code>, care gestioneaz\u0103 deployments blue-green \u0219i canary cu diverse op\u021biuni de configurare.<\/p>\n<p><\/p>\n<blockquote><p>Controllerul Argo Rollouts, utilizat cu resursa personalizat\u0103 <code>Rollout,<\/code> permite utilizarea unor strategii suplimentare de implementare, cum ar fi blue-green \u0219i canary pentru Kubernetes. Resursa <code>Rollout<\/code> ofer\u0103 func\u021bionalitate echivalent\u0103 <code>Deployment<\/code>, doar cu strategii suplimentare de implementare.<br \/>\nResurs\u0103 <code>Deployments<\/code> are dou\u0103 strategii pentru implementare: <code>RollingUpdate<\/code> \u0219i <code>Recreate<\/code>. De\u0219i aceste strategii sunt potrivite pentru cele mai multe cazuri, pentru implement\u0103ri pe servere la scar\u0103 foarte mare se folosesc strategii suplimentare, cum ar fi blue-green sau canary, care nu sunt disponibile \u00een controllerul Deployment. Pentru a utiliza aceste strategii \u00een Kubernetes, utilizatorii erau nevoi\u021bi s\u0103 scrie scripturi peste Deployments-urile lor. Controllerul Argo Rollouts ofer\u0103 aceste strategii sub forma unor parametrii declara\u021bi personalizabili.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/argoproj.github.io\/argo-rollouts\">https:\/\/argoproj.github.io\/argo-rollouts<\/a><\/noindex><\/p><\/blockquote>\n<p>Exist\u0103, de asemenea, Argo CI, care ofer\u0103 o interfa\u021b\u0103 web convenabil\u0103 pentru utilizare \u00eempreun\u0103 cu Rollouts, ne vom uita la ea \u00een articolul urm\u0103tor.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-argo-rollouts\">Instalarea Argo Rollouts<\/h3>\n<p><\/p>\n<h4 id=\"na-storone-servera\">Pe partea serverului<\/h4>\n<p><\/p>\n<p><code>kubectl create namespace argo-rolloutskubectl apply -n argo-rollouts -f https:\/\/raw.githubusercontent.com\/argoproj\/argo-rollouts\/stable\/manifests\/install.yaml<\/code><\/p>\n<p><\/p>\n<p>\u00cen repository-ul nostru de infrastructur\u0103 (vezi mai jos) am ad\u0103ugat deja install.yaml ca i\/k8s\/argo-rollouts\/install.yaml. Astfel, GitlabCI \u00eel va instala \u00een cluster.<\/p>\n<p><\/p>\n<h4 id=\"na-storone-klienta-kubectl-plugin\">Pe partea clientului (plugin kubectl)<\/h4>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/argoproj.github.io\/argo-rollouts\/features\/kubectl-plugin\">https:\/\/argoproj.github.io\/argo-rollouts\/features\/kubectl-plugin<br \/>\n<\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"prilozhenie-dlya-primera\">Aplica\u021bia de exemplu<\/h3>\n<p><\/p>\n<p>O practic\u0103 bun\u0103 este s\u0103 existe repository-uri separate pentru codul aplica\u021biei \u0219i pentru infrastructur\u0103.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniya\">Repository-ul pentru aplica\u021bie<\/h4>\n<p><\/p>\n<h4 id=\"kim-wuestkamp--k8s-deployment-example-apphttpsgitlabcomwuestkampk8s-deployment-example-app\"><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/wuestkamp\/k8s-deployment-example-app\">Kim Wuestkamp \/ k8s-deployment-example-app<\/a><\/noindex><\/h4>\n<p><\/p>\n<p>Aceasta este o API foarte simpl\u0103 pe Python+Flask, return\u00e2nd un r\u0103spuns sub form\u0103 de JSON. Vom construi pachetul folosind GitlabCI \u0219i vom \u00eempinge rezultatul \u00een Gitlab Registry. \u00cen registry avem dou\u0103 versiuni diferite ale lans\u0103rilor:<\/p>\n<p><\/p>\n<ul>\n<li>wuestkamp\/k8s-deployment-example-app:v1<\/li>\n<li>wuestkamp\/k8s-deployment-example-app:v2<\/li>\n<\/ul>\n<p><\/p>\n<p>Singura diferen\u021b\u0103 dintre ele este fi\u0219ierul JSON returnat. Folosim aceast\u0103 aplica\u021bie pentru a vizualiza c\u00e2t mai simplu versiunea cu care interac\u021bion\u0103m.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-repozitoriy\">Repozitoriu de infrastructur\u0103<\/h4>\n<p><\/p>\n<p>\u00cen acest repository, vom folosi GitlabCI pentru a desf\u0103\u0219ura \u00een Kubernetes, fi\u0219ierul .gitlab-ci.yml arat\u0103 astfel:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">imagine: traherom\/kustomize-dockerbefore_script:\n   - printenv\n   - kubectl versionstages:\n - desf\u0103\u0219uraredeploy test:\n   stage: desf\u0103\u0219urare\n   before_script:\n     - echo $KUBECONFIG\n   script:\n     - kubectl get all\n     - kubectl apply -f i\/k8s    only:\n     - master<\/code><\/pre>\n<p><\/p>\n<p>Pentru a-l rula local, ave\u021bi nevoie de un cluster, pute\u021bi folosi Gcloud:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">gcloud container clusters create canary --num-nodes 3 --zone europe-west3-b\ngcloud compute firewall-rules create incoming-80 --allow tcp:80<\/code><\/pre>\n<p><\/p>\n<p>Trebuie s\u0103 face\u021bi un fork <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/wuestkamp\/k8s-deployment-example-canary-infrastructure\">https:\/\/gitlab.com\/wuestkamp\/k8s-deployment-example-canary-infrastructure<\/a><\/noindex> \u0219i s\u0103 crea\u021bi o variabil\u0103 <code>KUBECONFIG<\/code> \u00een GitlabCI, care va con\u021bine configura\u021bia de acces <code>kubectl<\/code> la clusterul dvs.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/faun\/manually-connect-to-your-kubernetes-cluster-from-the-outside-d852346a7f0a\">Aici<\/a><\/noindex> po\u021bi citi despre cum s\u0103 ob\u021bii acreditivele pentru cluster (Gcloud).<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-yaml\">Yaml de infrastructur\u0103<\/h4>\n<p><\/p>\n<p>\u00cen interiorul repository-ului de infrastructur\u0103 avem service:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: v1\nkind: Service\nmetadata:\n labels:\n   id: rollout-canary\n name: app\nspec:\n ports:\n - port: 80\n   protocol: TCP\n   targetPort: 5000\n selector:\n   id: app\n type: LoadBalancer<\/code><\/pre>\n<p><\/p>\n<p>\u0219i rollout.yaml :<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: argoproj.io\/v1alpha1\nkind: Rollout\nmetadata:\n name: rollout-canary\nspec:\n replicas: 10\n revisionHistoryLimit: 2\n selector:\n   matchLabels:\n     id: rollout-canary\n template:\n   metadata:\n     labels:\n       id: rollout-canary\n   spec:\n     containers:\n     - name: rollouts-demo\n       image: registry.gitlab.com\/wuestkamp\/k8s-deployment-example-app:v1\n       imagePullPolicy: Always\n strategy:\n   canary:\n     steps:\n     - setWeight: 10\n     # Rollouts pot fi reluate manual prin rularea `kubectl argo rollouts promote ROLLOUT`\n     - pause: {}\n     - setWeight: 50\n     - pause: { duration: 120 } # dou\u0103 minute<\/code><\/pre>\n<p><\/p>\n<p><code>Rollout<\/code> func\u021bioneaz\u0103 la fel ca un Deployment. Dac\u0103 nu definim o strategie de actualizare (ca canary aici), se va comporta ca un deployment rolling-update implicit.<\/p>\n<p><\/p>\n<p>Definim dou\u0103 etape \u00een yaml pentru canary deployment:<\/p>\n<p><\/p>\n<ol>\n<li>10% din trafic pe canary (\u00eentre\u021binere manual\u0103 OK)<\/li>\n<li>50% din trafic pe canary (a\u0219teapt\u0103 2 minute, apoi continu\u0103 la 100%)<\/li>\n<\/ol>\n<p><\/p>\n<h3 id=\"vypolnenie-nachalnogo-deploya\">Executarea deployment-ului ini\u021bial<\/h3>\n<p><\/p>\n<p>Dup\u0103 desf\u0103\u0219urarea ini\u021bial\u0103, resursele noastre vor ar\u0103ta astfel:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/2f161eb3c80382bbe4f14a1fd199f1d6.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u0218i primim r\u0103spuns doar de la prima versiune a aplica\u021biei:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/117526d90b2fb5c765bb13f18230e9d5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3 id=\"vypolnyaem-canary-deployment\">Execut\u0103m Canary Deployment<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-10-trafika\">Pasul 1: 10% din trafic<\/h4>\n<p><\/p>\n<p>Pentru a \u00eencepe desf\u0103\u0219urarea canary, trebuie doar s\u0103 schimb\u0103m versiunea imaginii, a\u0219a cum facem de obicei cu desf\u0103\u0219ur\u0103rile:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: argoproj.io\/v1alpha1\nkind: Rollout\nmetadata:\n name: rollout-canary\nspec:\n...\n template:\n   metadata:\n     labels:\n       id: rollout-canary\n   spec:\n     containers:\n     - name: rollouts-demo\n       image: registry.gitlab.com\/wuestkamp\/k8s-deployment-example-app:v2\n...<\/code><\/pre>\n<p><\/p>\n<p>\u0218i trimitem modific\u0103rile, astfel \u00eenc\u00e2t Gitlab CI s\u0103 fac\u0103 desf\u0103\u0219urarea \u0219i vedem schimb\u0103rile:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/ee069d8108e6ac211827b01390c45910.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Acum, dac\u0103 ne adres\u0103m serviciului:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/0be8a02c6ab6166d230818c43bbae3d1.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Excelent! Suntem \u00een mijlocul desf\u0103\u0219ur\u0103rii canary. Putem vedea progresul pentru rul\u00e2nd:<\/p>\n<p><\/p>\n<p><code>kubectl argo rollouts get rollout rollout-canary<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/5b8a9fae9f92520b62cfcb5dd12fb7ba.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h4 id=\"shag-2-50-trafika\">Pasul 2: 50% din trafic:<\/h4>\n<p><\/p>\n<p>Acum trecem la pasul urm\u0103tor: redirec\u021bionarea a 50% din trafic. Am configurat astfel \u00eenc\u00e2t acest pas s\u0103 fie declan\u0219at manual:<\/p>\n<p><\/p>\n<p><code>kubectl argo rollouts promote rollout-canary # continu\u0103 la pasul 2<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/c856b7a60930cd5f6484ebe5a9080ffd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u0218i aplica\u021bia noastr\u0103 a \u00eentors 50% din r\u0103spunsuri de la versiunile noi:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/502638210f546c5d973fc284beea1ec5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u0218i un rezumat al desf\u0103\u0219ur\u0103rii:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/64e996d9681a88475af31b09ecf61a3f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Minunat.<\/p>\n<p><\/p>\n<h4 id=\"shag-3-100-trafika\">Pasul 3: 100% din trafic:<\/h4>\n<p><\/p>\n<p>Am configurat astfel \u00eenc\u00e2t, dup\u0103 2 minute, pasul cu 50% s\u0103 se finalizeze automat \u0219i s\u0103 se lanseze pasul cu 100%:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/d7eee8f41fcbd9c186b37666ea6c10fe.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u0218i ie\u0219irea aplica\u021biei:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/f66c21e326f2bf52b29b460fc6e84957.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u0218i un rezumat al desf\u0103\u0219ur\u0103rii:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment \u00een Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/5485ddc238b4eaad9e14d338acc116a8.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Desf\u0103\u0219urarea Canary s-a \u00eencheiat.<\/p>\n<p><\/p>\n<h4 id=\"eschyo-primery-s-argo-rollouts\">\u00cenc\u0103 exemple cu Argo Rollouts<\/h4>\n<p><\/p>\n<p>Aici sunt \u0219i alte exemple, cum ar fi configurarea previzualiz\u0103rii mediului \u0219i a compara\u021biilor bazate pe canary:<\/p>\n<p><\/p>\n<p><u><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/argoproj\/argo-rollouts\/tree\/master\/examples\">https:\/\/github.com\/argoproj\/argo-rollouts\/tree\/master\/examples<\/a><\/noindex><\/u><\/p>\n<p><\/p>\n<h4 id=\"video-ob-argo-rollouts-i-argo-ci\">Video despre Argo Rollouts \u0219i Argo CI<\/h4>\n<p><\/p>\n<p>\u00ce\u021bi recomand cu c\u0103ldur\u0103 acest video, deoarece arat\u0103 cum func\u021bioneaz\u0103 \u00eempreun\u0103 Argo Rollouts \u0219i Argo CI:<\/p>\n<p>\n<center><div class=\"youtube-placeholder\" data-id=\"yeVkTTO9nOA\" onclick=\"loadVideo(this)\">\r\n        <img decoding=\"async\" src=\"https:\/\/img.youtube.com\/vi\/yeVkTTO9nOA\/hqdefault.jpg\" alt=\"Reda\u021bi video\" loading=\"lazy\" width=\"480\" height=\"360\" style=\"width:100%;height:auto;\">\r\n        <div class=\"play-button\"><\/div>\r\n    <\/div><\/center><\/p>\n<h2 id=\"itog\">Rezultatul<\/h2>\n<p><\/p>\n<p>\u00cemi place foarte mult ideea de a folosi CRD-uri care gestioneaz\u0103 crearea de tipuri suplimentare de deploymente sau replicasets, redirec\u021bion\u00e2nd traficul etc. Lucrul cu ele decurge f\u0103r\u0103 probleme. \u00cen continuare, a\u0219 dori s\u0103 testez integrarea cu Argo CI.<\/p>\n<p><\/p>\n<p>Totu\u0219i, se pare c\u0103 va avea loc o fuzionare important\u0103 \u00eentre Argo CI \u0219i Flux CI, a\u0219a c\u0103 a\u0219 putea a\u0219tepta p\u00e2n\u0103 la lansarea noului release: <noindex><a rel=\"nofollow\" href=\"https:\/\/www.weave.works\/blog\/argo-flux-join-forces\">Argo Flux<\/a><\/noindex>. <\/p>\n<p><\/p>\n<p>A\u021bi avut experien\u021be cu Argo Rollouts sau Argo CI?<\/p>\n<p><\/p>\n<h2 id=\"takzhe-chitayte-drugie-stati-v-nashem-bloge\">Citi\u021bi \u0219i alte articole de pe blogul nostru:<\/h2>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/470568\/\">Implementarea Blue-Green a aplica\u021biilor pe Spring cu server web Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/480072\/\">Kubernetes: de ce este at\u00e2t de important s\u0103 configur\u0103m gestionarea resurselor sistemului?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473014\/\">Introducerea \u00een Autorizarea Kubernetes a Hashicorp Consul<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/481992\/\">Tekton Pipeline \u2014 pipelines nativ Kubernetes<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473578\/\">Compilarea modulelor dinamice pentru Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/347526\/\">Bot Telegram pentru Redmine. Cum s\u0103 \u00ee\u021bi simplifici via\u021ba \u021bie \u0219i celorlal\u021bi<\/a><\/noindex><\/li>\n<\/ul>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/513118\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c k8s-\u043d\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f Argo Rollouts \u0438 GitlabCI \u0434\u043b\u044f \u0437\u0430\u043f\u0443\u0441\u043a\u0430 Canary \u0434\u0435\u043f\u043b\u043e\u044f \u0432 Kubernetes https:\/\/unsplash.com\/photos\/V41PulGL1z0 \u0421\u0442\u0430\u0442\u044c\u0438 \u044d\u0442\u043e\u0433\u043e \u0446\u0438\u043a\u043b\u0430 Canary Deployment \u0432 Kubernetes #1: Gitlab CI (\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f) Canary Deployment using Istio Canary Deployment using Jenkins-X Istio Flagger Canary Deployment \u041d\u0430\u0434\u0435\u0435\u043c\u0441\u044f, \u0447\u0442\u043e \u0412\u044b \u0447\u0438\u0442\u0430\u043b\u0438 \u043f\u0435\u0440\u0432\u0443\u044e \u0447\u0430\u0441\u0442\u044c, \u0433\u0434\u0435 \u043c\u044b \u043a\u0440\u0430\u0442\u043a\u043e \u043e\u0431\u044a\u044f\u0441\u043d\u044f\u043b\u0438 \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 Canary Deployments. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":90374,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-90373","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c k8s-\u043d\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f Argo Rollouts \u0438 GitlabCI.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Canary Deployment \u0432 Kubernetes #2: Argo Rollouts | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c k8s-\u043d\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f Argo Rollouts \u0438 GitlabCI.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-07-31T11:42:12+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-31T11:42:12+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Canary Deployment \u00een Kubernetes #2: Argo Rollouts | ProHoster","description":"Vom folosi controlerul de deployment nativ k8s Argo Rollouts \u0219i GitlabCI.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Canary Deployment \u0432 Kubernetes #2: Argo Rollouts | ProHoster","og:description":"\u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c k8s-\u043d\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f Argo Rollouts \u0438 GitlabCI.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-07-31T11:42:12+00:00","article:modified_time":"2020-07-31T11:42:12+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"90373","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 12:53:48","updated":"2022-09-30 17:28:16","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/90373","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=90373"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/90373\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/90374"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=90373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=90373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=90373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}