{"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\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","title":{"rendered":"Canary nasadenie v 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\">Budeme pou\u017e\u00edva\u0165 k8s-nat\u00edvny kontrol\u00e9r nasadenia Argo Rollouts a GitlabCI na spustenie Canary nasadenia v Kubernetes<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v 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\">\u010cl\u00e1nky v tejto s\u00e9rii<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">Canary nasadenie v Kubernetes #1: Gitlab CI<\/a><\/noindex><\/li>\n<li>(Tento \u010dl\u00e1nok)<\/li>\n<li>Canary nasadenie pomocou Istio<\/li>\n<li>Canary nasadenie pomocou Jenkins-X Istio Flagger<\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3 id=\"canary-deployment\">Canary nasadenie<\/h3>\n<p><\/p>\n<p>D\u00fafame, \u017ee ste \u010d\u00edtali <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">prv\u00fa \u010das\u0165<\/a><\/noindex>, kde sme stru\u010dne vysvetlili, \u010do s\u00fa Canary nasadenia. Taktie\u017e sme uk\u00e1zali, ako ich realizova\u0165 pomocou \u0161tandardn\u00fdch prostriedkov Kubernetes.<\/p>\n<p><\/p>\n<h3 id=\"argo-rollouts\">Argo Rollouts<\/h3>\n<p><\/p>\n<p>Argo Rollouts je Kubernetes-nat\u00edvny kontrol\u00e9r nasadenia. Poskytuje CRD (Custom Resource Definition) pre Kubernetes. V\u010faka nemu m\u00f4\u017eeme pou\u017e\u00edva\u0165 nov\u00fa entitu: <code>Rollout<\/code>, ktor\u00e1 spravuje blue-green a canary nasadenia s r\u00f4znymi mo\u017enos\u0165ami nastavenia.<\/p>\n<p><\/p>\n<blockquote><p>Kontrol\u00e9r Argo Rollouts, ktor\u00fd sa pou\u017e\u00edva s vlastn\u00fdm zdrojom <code>Rollout,<\/code> umo\u017e\u0148uje pou\u017e\u00edva\u0165 dodato\u010dn\u00e9 strat\u00e9gie nasadenia, ako s\u00fa blue-green a canary pre Kubernetes. Zdroje <code>Rollout<\/code> poskytuje funkcie rovnocenn\u00e9 <code>Nasadenie<\/code>, iba s dodato\u010dn\u00fdmi strat\u00e9giami nasadenia.<br \/>\nZ\u00e1sob <code>Deployments<\/code> m\u00e1 dve strat\u00e9gie pre nasadenie: <code>RollingUpdate<\/code> a <code>Recreate<\/code>. Napriek tomu, \u017ee tieto strat\u00e9gie s\u00fa vhodn\u00e9 pre v\u00e4\u010d\u0161inu pr\u00edpadov, pre nasadenia na serveroch v ve\u013emi ve\u013ekom meradle sa pou\u017e\u00edvaj\u00fa dodato\u010dn\u00e9 strat\u00e9gie, ako s\u00fa blue-green alebo canary, ktor\u00e9 ch\u00fdbaj\u00fa v kontrol\u00e9ri Deployment. Aby mohli pou\u017e\u00edvatelia tieto strat\u00e9gie v Kubernetes vyu\u017ei\u0165, museli p\u00edsanie skriptov nad svojimi nasadeniami. Kontrol\u00e9r Argo Rollouts poskytuje tieto strat\u00e9gie vo forme jednoduch\u00fdch deklarat\u00edvnych prisp\u00f4sobite\u013en\u00fdch parametrov.<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>Existuje tie\u017e Argo CI, ktor\u00fd poskytuje pou\u017e\u00edvate\u013esk\u00e9 webov\u00e9 rozhranie na pou\u017eitie spolu s Rollouts, na ktor\u00e9 sa pozrieme v nasleduj\u00facom \u010dl\u00e1nku.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-argo-rollouts\">In\u0161tal\u00e1cia Argo Rollouts<\/h3>\n<p><\/p>\n<h4 id=\"na-storone-servera\">Na strane servera<\/h4>\n<p><\/p>\n<p><code>kubectl create namespace argo-rollouts kubectl apply -n argo-rollouts -f https:\/\/raw.githubusercontent.com\/argoproj\/argo-rollouts\/stable\/manifests\/install.yaml<\/code><\/p>\n<p><\/p>\n<p>V na\u0161ej infra\u0161trukt\u00farnej repozit\u00e1ri (pozri ni\u017e\u0161ie) sme u\u017e pridali install.yaml ako i\/k8s\/argo-rollouts\/install.yaml. Takto GitlabCI ho nain\u0161taluje do klastra.<\/p>\n<p><\/p>\n<h4 id=\"na-storone-klienta-kubectl-plugin\">Na strane klienta (kubectl plugin)<\/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\">Pr\u00edklad aplik\u00e1cie<\/h3>\n<p><\/p>\n<p>Dobrou praxou je ma\u0165 oddelen\u00e9 repozit\u00e1re pre k\u00f3d aplik\u00e1cie a pre infra\u0161trukt\u00faru.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniya\">Repozit\u00e1r pre aplik\u00e1ciu<\/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>Je to ve\u013emi jednoduch\u00e9 API na Python+Flask, ktor\u00e9 vracia odpove\u010f vo forme JSON. Zostav\u00edme bal\u00edk pomocou GitlabCI a nahod\u00edme v\u00fdsledok do Gitlab Registry. V registri m\u00e1me dve r\u00f4zne verzie vydan\u00ed:<\/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>Jedin\u00fd rozdiel medzi nimi je vracan\u00fd JSON s\u00fabor. Pou\u017e\u00edvame t\u00fato aplik\u00e1ciu na maxim\u00e1lne jednoduch\u00fa vizualiz\u00e1ciu toho, s ktorou verziou komunikujeme.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-repozitoriy\">Infra\u0161trukt\u00farny repozit\u00e1r<\/h4>\n<p><\/p>\n<p>V tomto repozit\u00e1ri budeme pou\u017e\u00edva\u0165 GitlabCI na nasadenie do Kubernetes, .gitlab-ci.yml vyzer\u00e1 nasledovne:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">image: traherom\/kustomize-dockerbefore_script:\n   - printenv\n   - kubectl versionstages:\n - deploydeploy test:\n   stage: deploy\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>Na jeho spustenie potrebujete klaster, m\u00f4\u017eete pou\u017ei\u0165 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>Mus\u00edte si urobi\u0165 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> a vytvori\u0165 premenn\u00fa <code>KUBECONFIG<\/code> v GitlabCI, ktor\u00e1 bude obsahova\u0165 konfigur\u00e1ciu na pr\u00edstup <code>kubectl<\/code> k v\u00e1\u0161mu klastru.<\/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\">Tu<\/a><\/noindex> mo\u017eete si pre\u010d\u00edta\u0165, ako z\u00edska\u0165 poverenia pre klaster (Gcloud).<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-yaml\">Informa\u010dn\u00fd Yaml<\/h4>\n<p><\/p>\n<p>V infra\u0161trukt\u00farnom repozit\u00e1ri m\u00e1me 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>a 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 m\u00f4\u017eu by\u0165 manu\u00e1lne obnoven\u00e9 spusten\u00edm `kubectl argo rollouts promote ROLLOUT`\n     - pause: {}\n     - setWeight: 50\n     - pause: { duration: 120 } # dve min\u00faty<\/code><\/pre>\n<p><\/p>\n<p><code>Rollout<\/code> funguje rovnako ako Deployment. Ak nenastav\u00edme strat\u00e9giu aktualiz\u00e1cie (ako canary tu), bude sa spr\u00e1va\u0165 ako predvolen\u00fd rolling-update Deployment.<\/p>\n<p><\/p>\n<p>Definujeme dva kroky v yaml pre canary deployment:<\/p>\n<p><\/p>\n<ol>\n<li>10% prev\u00e1dzky na canary (\u010dakajte na manu\u00e1lne OK)<\/li>\n<li>50% prev\u00e1dzky na canary (\u010dakajte 2 min\u00faty a potom pokra\u010dujte na 100%)<\/li>\n<\/ol>\n<p><\/p>\n<h3 id=\"vypolnenie-nachalnogo-deploya\">Realiz\u00e1cia po\u010diato\u010dn\u00e9ho depozitu<\/h3>\n<p><\/p>\n<p>Po po\u010diato\u010dnom nasaden\u00ed na\u0161e zdroje bud\u00fa vyzera\u0165 takto:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/2f161eb3c80382bbe4f14a1fd199f1d6.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>A dost\u00e1vame odpove\u010f iba od prvej verzie aplik\u00e1cie:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v 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\">Vykon\u00e1vame Canary Deployment<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-10-trafika\">Krok 1: 10% prev\u00e1dzky<\/h4>\n<p><\/p>\n<p>Aby sme za\u010dali canary nasadenie, mus\u00edme jednoducho zmeni\u0165 verziu obrazu, ako to zvy\u010dajne rob\u00edme pri nasadeniach:<\/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>A posielame zmeny, tak\u017ee Gitlab CI rob\u00ed nasadenie a vid\u00edme zmeny:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/ee069d8108e6ac211827b01390c45910.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Teraz, ak sa obr\u00e1time na slu\u017ebu:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/0be8a02c6ab6166d230818c43bbae3d1.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Skvel\u00e9! Sme v strede n\u00e1\u0161ho canary nasadenia. M\u00f4\u017eeme vidie\u0165 pokrok, ak spust\u00edme:<\/p>\n<p><\/p>\n<p><code>kubectl argo rollouts get rollout rollout-canary<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v 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\">Krok 2: 50% prev\u00e1dzky:<\/h4>\n<p><\/p>\n<p>Teraz pristupujeme k \u010fal\u0161iemu kroku: presmerovanie 50% prev\u00e1dzky. Nastavili sme to tak, aby tento krok bol spusten\u00fd manu\u00e1lne:<\/p>\n<p><\/p>\n<p><code>kubectl argo rollouts promote rollout-canary # pokra\u010dova\u0165 na krok 2<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/c856b7a60930cd5f6484ebe5a9080ffd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>A na\u0161a aplik\u00e1cia vr\u00e1tila 50% odpoved\u00ed od nov\u00fdch verzi\u00ed:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/502638210f546c5d973fc284beea1ec5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>A preh\u013ead rollout:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/64e996d9681a88475af31b09ecf61a3f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>V\u00fdborne.<\/p>\n<p><\/p>\n<h4 id=\"shag-3-100-trafika\">Krok 3: 100% prev\u00e1dzky:<\/h4>\n<p><\/p>\n<p>Nastavili sme to tak, aby po 2 min\u00fatach krok so 50% bol dokon\u010den\u00fd automaticky a spusten\u00fd krok so 100%:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/d7eee8f41fcbd9c186b37666ea6c10fe.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>A v\u00fdstup aplik\u00e1cie:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/f66c21e326f2bf52b29b460fc6e84957.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>A preh\u013ead rollout:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/5485ddc238b4eaad9e14d338acc116a8.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Canary deploy je dokon\u010den\u00fd.<\/p>\n<p><\/p>\n<h4 id=\"eschyo-primery-s-argo-rollouts\">\u010eal\u0161ie pr\u00edklady s Argo Rollouts<\/h4>\n<p><\/p>\n<p>Tu s\u00fa \u010fal\u0161ie pr\u00edklady, napr\u00edklad, ako nastavi\u0165 n\u00e1h\u013ead prostredia a porovnania zalo\u017een\u00e9 na kan\u00e1li:<\/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 o Argo Rollouts a Argo CI<\/h4>\n<p><\/p>\n<p>Opr\u00e1vnene odpor\u00fa\u010dam toto video, ukazuje, ako Argo Rollouts a Argo CI spolupracuj\u00fa:<\/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=\"Prehrajte 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\">Z\u00e1ver<\/h2>\n<p><\/p>\n<p>Ve\u013emi sa mi p\u00e1\u010di my\u0161lienka vyu\u017e\u00edvania CRD, ktor\u00e9 riadia vytv\u00e1ranie \u010fal\u0161\u00edch typov nasaden\u00ed alebo replikovan\u00fdch sad, presmerov\u00e1vaj\u00fa prev\u00e1dzku at\u010f. Pr\u00e1ca s nimi prebieha hladko. Potom by som chcel otestova\u0165 integr\u00e1ciu s Argo CI.<\/p>\n<p><\/p>\n<p>Av\u0161ak, zd\u00e1 sa, \u017ee sa bl\u00ed\u017ei ve\u013ek\u00e9 zl\u00fa\u010denie Argo CI a Flux CI, tak\u017ee by som mohol po\u010dka\u0165, k\u00fdm vyjde nov\u00fd 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>M\u00e1te sk\u00fasenosti s Argo Rollouts alebo Argo CI?<\/p>\n<p><\/p>\n<h2 id=\"takzhe-chitayte-drugie-stati-v-nashem-bloge\">\u010c\u00edtajte tie\u017e \u010fal\u0161ie \u010dl\u00e1nky na na\u0161om blogu:<\/h2>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/470568\/\">Blue-Green Deployment aplik\u00e1ci\u00ed na Spring s webov\u00fdm serverom Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/480072\/\">Kubernetes: pre\u010do je d\u00f4le\u017eit\u00e9 nastavi\u0165 riadenie zdrojov syst\u00e9mu?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473014\/\">\u00davod do autoriz\u00e1cie Kubernetes v Hashicorp Consul<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/481992\/\">Tekton Pipeline \u2014 Kubernetes-nat\u00edvne pipelines<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473578\/\">Zostavenie dynamick\u00fdch modulov pre Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/347526\/\">Telegram bot pre Redmine. Ako si u\u013eah\u010di\u0165 \u017eivot sebe a ostatn\u00fdm<\/a><\/noindex><\/li>\n<\/ul>\n<p>Zdroj: <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.4 - 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\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\/sk\/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 v Kubernetes #2: Argo Rollouts | ProHoster","description":"Budeme pou\u017e\u00edva\u0165 k8s-nat\u00edvny kontrol\u00e9r nasadenia Argo Rollouts a GitlabCI.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\/sk\/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\/sk\/wp-json\/wp\/v2\/posts\/90373","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=90373"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/90373\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/90374"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=90373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=90373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=90373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}