{"id":90272,"date":"2020-07-30T13:42:02","date_gmt":"2020-07-30T11:42:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci"},"modified":"2020-07-30T13:42:02","modified_gmt":"2020-07-30T11:42:02","slug":"canary-deployment-v-kubernetes-1-gitlab-ci","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","title":{"rendered":"Canary nasadenie v Kubernetes #1: Gitlab CI","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<h4 id=\"my-budem-ispolzovat-gitlab-ci-i-ruchnoy-gitops-dlya-vnedreniya-i-ispolzovaniya-canary-deploya-v-kubernetes\">Na implement\u00e1ciu a pou\u017e\u00edvanie Canary nasadenia v Kubernetes budeme pou\u017e\u00edva\u0165 Gitlab CI a manu\u00e1lny GitOps.<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/03a53dec150529deb3438efaeaa8a1bd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h4 id=\"stati-iz-etogo-cikla\">\u010cl\u00e1nky z tejto s\u00e9rie:<\/h4>\n<p><\/p>\n<ul>\n<li>(tento \u010dl\u00e1nok)<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/513118\/\">Canary nasadenie pomocou ArgoCI<\/a><\/noindex><\/li>\n<li>Canary nasadenie pomocou Istio<\/li>\n<li>Canary nasadenie pomocou Jenkins-X Istio Flagger<\/li>\n<\/ul>\n<p><\/p>\n<p>Canary nasadenie budeme vykon\u00e1va\u0165 ru\u010dne prostredn\u00edctvom GitOps a vytvoren\u00edm\/zmenou z\u00e1kladn\u00fdch zdrojov Kubernetes. <strong>Tento \u010dl\u00e1nok je prim\u00e1rne ur\u010den\u00fd na zozn\u00e1menie<\/strong> s t\u00fdm, ako funguje Canary nasadenie v Kubernetes, preto\u017ee existuj\u00fa efekt\u00edvnej\u0161ie sp\u00f4soby automatiz\u00e1cie, ktor\u00e9 si prejdeme v \u010fal\u0161\u00edch \u010dl\u00e1nkoch.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/d5127cf7dcec695bd8872b1704eb7e90.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.norberteder.com\/canary-deployment\/\">https:\/\/www.norberteder.com\/canary-deployment\/<\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"canary-deployment\">Canary nasadenie<\/h3>\n<p><\/p>\n<p>Pri strat\u00e9gii Canary aktualiz\u00e1cie sa najprv aplikuj\u00fa iba na \u010das\u0165 pou\u017e\u00edvate\u013eov. Prostredn\u00edctvom monitorovania, \u00fadajov z logov, manu\u00e1lneho testovania alebo in\u00fdch kan\u00e1lov sp\u00e4tnej v\u00e4zby sa vydanie testuje pred jeho aplikovan\u00edm pre v\u0161etk\u00fdch pou\u017e\u00edvate\u013eov.<\/p>\n<p><\/p>\n<h3 id=\"kubernetes-deployment-rolling-update\">Kubernetes Deployment (rolling update)<\/h3>\n<p><\/p>\n<p>Predvolen\u00e1 strat\u00e9gia pre Kubernetes Deployment je rolling-update, kde sa sp\u00fa\u0161\u0165a ur\u010dit\u00e9 mno\u017estvo podov s nov\u00fdmi verziami obrazov. Ak sa vytvoria bez probl\u00e9mov, pody so star\u00fdmi verzami obrazov sa ukon\u010dia a nov\u00e9 pody sa vytvoria paralelne.<\/p>\n<p><\/p>\n<h3 id=\"gitops\">GitOps<\/h3>\n<p><\/p>\n<p>V tomto pr\u00edklade pou\u017e\u00edvame GitOps, preto\u017ee:<\/p>\n<p><\/p>\n<ul>\n<li>pou\u017e\u00edvame Git ako jedin\u00fd zdroj pravdy<\/li>\n<li>pou\u017e\u00edvame Git oper\u00e1cie na zostavenie a nasadenie (nie s\u00fa potrebn\u00e9 \u017eiadne pr\u00edkazy okrem git tag\/merge)<\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"primer\">Pr\u00edklad<\/h3>\n<p><\/p>\n<p>Pre dobr\u00fa prax si zoberieme, \u017ee m\u00e1me jeden repozit\u00e1r pre k\u00f3d aplik\u00e1ci\u00ed a jeden pre infra\u0161trukt\u00faru.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniy\">Repozit\u00e1r pre aplik\u00e1cie<\/h4>\n<p><\/p>\n<p>Toto je ve\u013emi jednoduch\u00e9 API na Python+Flask, ktor\u00e9 vracia odpove\u010f vo form\u00e1te JSON. Zostav\u00edme bal\u00edk prostredn\u00edctvom GitlabCI a v\u00fdsledok nahod\u00edme do Gitlab Registry. V registri m\u00e1me dve r\u00f4zne verzie vydan\u00ed:<\/p>\n<p><\/p>\n<ul>\n<li><code>wuestkamp\/k8s-deployment-example-app:v1<\/code><\/li>\n<li><code>wuestkamp\/k8s-deployment-example-app:v2<\/code><\/li>\n<\/ul>\n<p><\/p>\n<p>Jedin\u00fd rozdiel medzi nimi je zmena vracaj\u00faceho JSON s\u00faboru. 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 nasadzova\u0165 prostredn\u00edctvom GitlabCI do Kubernetes, <code>.gitlab-ci.yml<\/code> vyzer\u00e1 nasledovne:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">image: traherom\/kustomize-docker\n\nbefore_script:\n   - printenv\n   - kubectl version\n\nstages:\n - deploy\n\ndeploy test:\n   stage: deploy\n   before_script:\n     - echo $KUBECONFIG\n   script:\n     - kubectl get all\n     - kubectl apply -f i\/k8s\n\n   only:\n     - master\n<\/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\n\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>O tom, ako z\u00edska\u0165 poverenia pre klaster (Gcloud) sa m\u00f4\u017eete do\u010d\u00edta\u0165 <noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/faun\/manually-connect-to-your-kubernetes-cluster-from-the-outside-d852346a7f0a\">tu<\/a><\/noindex>.<\/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: app\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 deployment v <code>deploy.yaml<\/code>:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">apiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: app\nspec:\n replicas: 10\n selector:\n   matchLabels:\n     id: app\n     type: main\n template:\n   metadata:\n     labels:\n       id: app\n       type: main\n   spec:\n     containers:\n     - image: registry.gitlab.com\/wuestkamp\/k8s-deployment-example-app:v1\n       name: app\n       resources:\n         limits:\n           cpu: 100m\n           memory: 100Mi<\/code><\/pre>\n<p><\/p>\n<p>A \u010fal\u0161\u00ed deployment v <code>deploy-canary.yaml<\/code>:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">kind: Deployment\nmetadata:\n name: app-canary\nspec:\n replicas: 0\n selector:\n   matchLabels:\n     id: app\n     type: canary\n template:\n   metadata:\n     labels:\n       id: app\n       type: canary\n   spec:\n     containers:\n     - image: registry.gitlab.com\/wuestkamp\/k8s-deployment-example-app:v2\n       name: app\n       resources:\n         limits:\n           cpu: 100m\n           memory: 100Mi<\/code><\/pre>\n<p><\/p>\n<p>V\u0161imnite si, \u017ee app-deploy zatia\u013e nem\u00e1 ur\u010den\u00e9 repliky.<\/p>\n<p><\/p>\n<h4 id=\"vypolnenie-nachalnogo-deploya\">Realiz\u00e1cia po\u010diato\u010dn\u00e9ho depozitu<\/h4>\n<p><\/p>\n<p>Pre spustenie po\u010diato\u010dn\u00e9ho deploymentu m\u00f4\u017eete spusti\u0165 pipeline GitlabCI manu\u00e1lne v hlavnej branchi. Potom <code>kubectl<\/code> by mal vyk\u00e1za\u0165 nasleduj\u00face:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/e8ea95fe6c3925f46f6430ce2293063c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Vid\u00edme <code>app<\/code> deployment s 10 replikami a app-canary s 0. Tak isto je tu LoadBalancer, cez ktor\u00fd m\u00f4\u017eeme pristupova\u0165 cez <code>curl<\/code> po External IP:<\/p>\n<p><\/p>\n<p><code>while true; do curl -s 35.198.149.232 | grep label; sleep 0.1; done<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/06e6928002532dbe03b65356964110c7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Vid\u00edme, \u017ee na\u0161a testovacia aplik\u00e1cia vracia iba \u201cv1\u201d.<\/p>\n<p><\/p>\n<h3 id=\"vypolnenie-canary-deploya\">Realiz\u00e1cia Canary depozitu<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-vypustit-novuyu-versiyu-dlya-chasti-polzovateley\">Krok 1: uvo\u013eni\u0165 nov\u00fa verziu pre \u010das\u0165 pou\u017e\u00edvate\u013eov<\/h4>\n<p><\/p>\n<p>Nastavili sme po\u010det replik na 1 v s\u00fabore deploy-canary.yaml a obraz novej verzie:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">kind: Deployment\nmetadata:\n name: app-canary\nspec:\n replicas: 1\n selector:\n   matchLabels:\n     id: app\n     type: canary\n template:\n   metadata:\n     labels:\n       id: app\n       type: canary\n   spec:\n     containers:\n     - image: registry.gitlab.com\/wuestkamp\/k8s-deployment-example-app:v2\n       name: app\n       resources:\n         limits:\n           cpu: 100m\n           memory: 100Mi<\/code><\/pre>\n<p><\/p>\n<p>V s\u00fabore <code>deploy.yaml<\/code> zmenili sme po\u010det replik na 9:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">kind: Deployment\nmetadata:\n name: app\nspec:\n replicas: 9\n selector:\n   matchLabels:\n     id: app\n...<\/code><\/pre>\n<p><\/p>\n<p>T\u00fato zmenu posielame do repozit\u00e1ra, z ktor\u00e9ho sa spust\u00ed deployment (cez GitlabCI) a nakoniec vid\u00edme:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/b639716b31e41e8eac573fd365ad6780.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Na\u0161a slu\u017eba bude ukazova\u0165 na oba deploy, preto\u017ee obe maj\u00fa selektor app. V d\u00f4sledku n\u00e1hodn\u00e9ho rozdelenia pod\u013ea predvolen\u00e9ho nastavenia v Kubernetes by sme mali vidie\u0165 r\u00f4zne odpovede na pribli\u017ene 10 % po\u017eiadaviek:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/d1177207ebd8952fd1994ed0ebdda6a3.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Aktu\u00e1lny stav na\u0161ej aplik\u00e1cie (GitOps, bran\u00e9 z Git ako z Jedin\u00e9ho zdroja pravdy) je pr\u00edtomnos\u0165 dvoch deploymentov s akt\u00edvnymi replikami, po jednom pre ka\u017ed\u00fa verziu.<\/p>\n<p><\/p>\n<p>~10 % pou\u017e\u00edvate\u013eov sa oboznamuje s novou verziou a ne\u00famyselne ju testuj\u00fa. Teraz je \u010das skontrolova\u0165 pr\u00edtomnos\u0165 ch\u00fdb v logoch a monitorovac\u00edch d\u00e1tach na identifik\u00e1ciu probl\u00e9mov.<\/p>\n<p><\/p>\n<h4 id=\"shag-2-vypustit-novuyu-versiyu-dlya-vseh-polzovateley\">Krok 2: uvo\u013eni\u0165 nov\u00fa verziu pre v\u0161etk\u00fdch pou\u017e\u00edvate\u013eov<\/h4>\n<p><\/p>\n<p>Rozhodli sme sa, \u017ee v\u0161etko prebehlo dobre a teraz mus\u00edme roz\u0161\u00edri\u0165 nov\u00fa verziu na v\u0161etk\u00fdch pou\u017e\u00edvate\u013eov. Na to jednoducho aktualizujeme <code>deploy.yaml<\/code> nain\u0161talovan\u00edm novej verzie obrazu a po\u010det replik je nastaven\u00fd na 10. V <code>deploy-canary.yaml<\/code> nastavujeme po\u010det replik sp\u00e4\u0165 na 0. Po nasaden\u00ed bude v\u00fdsledok nasleduj\u00faci:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary nasadenie v Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/a31aafe96a09c6d2651b2bf7add4dd29.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3 id=\"podvodya-itog\">Na z\u00e1ver<\/h3>\n<p><\/p>\n<p>Pre m\u0148a spustenie nasadenia ru\u010dne takto pom\u00e1ha pochopi\u0165, ako \u013eahko m\u00f4\u017ee by\u0165 nakonfigurovan\u00e9 pomocou k8s. Preto\u017ee Kubernetes umo\u017e\u0148uje aktualizova\u0165 v\u0161etko cez API, tieto kroky je mo\u017en\u00e9 automatizova\u0165 pomocou skriptov.<\/p>\n<p><\/p>\n<p>\u010eal\u0161ia vec, ktor\u00fa je potrebn\u00e9 implementova\u0165, je vstupn\u00e1 bod testera (LoadBalancer alebo cez Ingress), cez ktor\u00fd sa d\u00e1 z\u00edska\u0165 pr\u00edstup iba k novej verzii. M\u00f4\u017ee by\u0165 pou\u017eit\u00e1 na manu\u00e1lny preh\u013ead.<\/p>\n<p><\/p>\n<p>V nasleduj\u00facich \u010dl\u00e1nkoch presk\u00famame \u010fal\u0161ie automatizovan\u00e9 rie\u0161enia, ktor\u00e9 implementuj\u00fa v\u00e4\u010d\u0161inu z toho, \u010do sme urobili.<\/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\/ru\/company\/nixys\/blog\/468779\/\">Ak\u00e9 d\u00f4sledky mala migr\u00e1cia z ClickHouse bez autoriz\u00e1cie na ClickHouse s autoriz\u00e1ciou<\/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\/news\/t\/502658\/\">Aktualiz\u00e1cia nxs-build-tools \u2013 asistenta pri zostavovan\u00ed deb a rpm bal\u00edkov<\/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\/ru\/company\/nixys\/blog\/504762\/\">S \u010d\u00edm sme sa museli vysporiada\u0165 pri pou\u017e\u00edvan\u00ed n\u00e1stroja Csync2<\/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\/512766\/\">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 Gitlab CI \u0438 \u0440\u0443\u0447\u043d\u043e\u0439 GitOps \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f Canary-\u0434\u0435\u043f\u043b\u043e\u044f \u0432 Kubernetes \u0421\u0442\u0430\u0442\u044c\u0438 \u0438\u0437 \u044d\u0442\u043e\u0433\u043e \u0446\u0438\u043a\u043b\u0430: (\u044d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f) Canary Deployment \u043f\u0440\u0438 \u043f\u043e\u043c\u043e\u0449\u0438 ArgoCI Canary Deployment \u043f\u0440\u0438 \u043f\u043e\u043c\u043e\u0449\u0438 Istio Canary Deployment \u043f\u0440\u0438 \u043f\u043e\u043c\u043e\u0449\u0438 Jenkins-X Istio Flagger \u0412\u044b\u043f\u043e\u043b\u043d\u044f\u0442\u044c Canary-\u0434\u0435\u043f\u043b\u043e\u0439 \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0440\u0443\u043a\u0430\u043c\u0438 \u0447\u0435\u0440\u0435\u0437 GitOps \u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0435\/\u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u0435 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 Kubernetes. \u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u043f\u0440\u0435\u0434\u043d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0430 \u0432 \u043f\u0435\u0440\u0432\u0443\u044e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":90273,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-90272","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 Gitlab CI \u0438 \u0440\u0443\u0447\u043d\u043e\u0439 GitOps \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f Canary-\u0434\u0435\u043f\u043b\u043e\u044f \u0432.\" \/>\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-1-gitlab-ci\" \/>\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 #1: Gitlab CI | 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 Gitlab CI \u0438 \u0440\u0443\u0447\u043d\u043e\u0439 GitOps \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f Canary-\u0434\u0435\u043f\u043b\u043e\u044f \u0432.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci\" \/>\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-30T11:42:02+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-30T11:42:02+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 #1: Gitlab CI | ProHoster","description":"Budeme pou\u017e\u00edva\u0165 Gitlab CI a manu\u00e1lny GitOps na zavedenie a pou\u017eitie Canary nasadenia v.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","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 #1: Gitlab CI | ProHoster","og:description":"\u041c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Gitlab CI \u0438 \u0440\u0443\u0447\u043d\u043e\u0439 GitOps \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f Canary-\u0434\u0435\u043f\u043b\u043e\u044f \u0432.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","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-30T11:42:02+00:00","article:modified_time":"2020-07-30T11:42:02+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"90272","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:55:28","updated":"2022-09-27 23:09:11","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\/90272","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=90272"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/90272\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/90273"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=90272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=90272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=90272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}