{"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\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","title":{"rendered":"Canary Deployment w 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\">B\u0119dziemy u\u017cywa\u0107 Gitlab CI oraz r\u0119cznego GitOps do wdro\u017cenia i wykorzystania Canary Deployment w Kubernetes.<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w 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\">Artyku\u0142y z tego cyklu:<\/h4>\n<p><\/p>\n<ul>\n<li>(ten artyku\u0142)<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/513118\/\">Canary Deployment przy pomocy ArgoCI<\/a><\/noindex><\/li>\n<li>Canary Deployment przy pomocy Istio<\/li>\n<li>Canary Deployment przy pomocy Jenkins-X Istio Flagger<\/li>\n<\/ul>\n<p><\/p>\n<p>Canary deployment b\u0119dziemy realizowa\u0107 r\u0119cznie poprzez GitOps i tworzenie\/zmienianie podstawowych zasob\u00f3w Kubernetes. <strong>Artyku\u0142 ten jest przede wszystkim przeznaczony do zapoznania<\/strong> si\u0119 z tym, jak dzia\u0142a Canary deployment w Kubernetes, poniewa\u017c istniej\u0105 bardziej efektywne sposoby automatyzacji, kt\u00f3re om\u00f3wimy w nast\u0119pnych artyku\u0142ach.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<img decoding=\"async\" alt=\"Canary Deployment w 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 Deployment<\/h3>\n<p><\/p>\n<p>W strategii Canary najpierw aktualizacje s\u0105 stosowane wy\u0142\u0105cznie do cz\u0119\u015bci u\u017cytkownik\u00f3w. Poprzez monitorowanie, dane z log\u00f3w, r\u0119czne testowanie lub inne kana\u0142y informacji zwrotnej, wydanie jest testowane przed zastosowaniem dla wszystkich u\u017cytkownik\u00f3w.<\/p>\n<p><\/p>\n<h3 id=\"kubernetes-deployment-rolling-update\">Kubernetes Deployment (rolling update)<\/h3>\n<p><\/p>\n<p>Domy\u015blna strategia dla Kubernetes Deployment to rolling-update, gdzie uruchamiane jest okre\u015blone ilo\u015b\u0107 pod\u00f3w z nowymi wersjami obraz\u00f3w. Je\u015bli zosta\u0142y one utworzone bez problem\u00f3w, pody ze starymi wersjami obraz\u00f3w s\u0105 ko\u0144czone, a nowe pody s\u0105 tworzone r\u00f3wnolegle.<\/p>\n<p><\/p>\n<h3 id=\"gitops\">GitOps<\/h3>\n<p><\/p>\n<p>U\u017cywamy GitOps w tym przyk\u0142adzie, poniewa\u017c:<\/p>\n<p><\/p>\n<ul>\n<li>u\u017cywamy Git jako jedynego \u017ar\u00f3d\u0142a prawdy,<\/li>\n<li>u\u017cywamy operacji Git do budowy i wdro\u017cenia (nie s\u0105 potrzebne \u017cadne komendy, opr\u00f3cz git tag\/merge).<\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"primer\">Przyk\u0142ad<\/h3>\n<p><\/p>\n<p>Przyjmijmy dobr\u0105 praktyk\u0119 \u2014 posiadanie jednego repozytorium dla kodu aplikacji i jednego dla infrastruktury.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniy\">Repozytorium dla aplikacji<\/h4>\n<p><\/p>\n<p>To bardzo prosty interfejs API w Pythonie+Flask, kt\u00f3ry zwraca odpowied\u017a w formacie JSON. Zbudujemy paczk\u0119 za pomoc\u0105 GitlabCI i wypchniemy wynik do Gitlab Registry. W rejestrze mamy dwie r\u00f3\u017cne wersje wyda\u0144:<\/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>Jedyn\u0105 r\u00f3\u017cnic\u0105 mi\u0119dzy nimi jest zmiana zwracanego pliku JSON. U\u017cywamy tej aplikacji do maksymalnie prostego wizualizowania, z jak\u0105 wersj\u0105 mamy do czynienia.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-repozitoriy\">Repozytorium infrastrukturalne<\/h4>\n<p><\/p>\n<p>W tym repozytorium b\u0119dziemy wdra\u017ca\u0107 poprzez GitlabCI w Kubernetes, <code>.gitlab-ci.yml<\/code> wygl\u0105da nast\u0119puj\u0105co:<\/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>Aby go uruchomi\u0107 samodzielnie, b\u0119dziesz potrzebowa\u0107 klastra, mo\u017cesz u\u017cy\u0107 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>Musisz zrobi\u0107 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> i stworzy\u0107 zmienn\u0105 <code>KUBECONFIG<\/code> w GitlabCI, kt\u00f3ra b\u0119dzie zawiera\u0107 konfiguracj\u0119 dost\u0119pu <code>kubectl<\/code> do twojego klastra.<\/p>\n<p><\/p>\n<p>O tym, jak uzyska\u0107 dane logowania do klastra (Gcloud), mo\u017cna przeczyta\u0107 <noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/faun\/manually-connect-to-your-kubernetes-cluster-from-the-outside-d852346a7f0a\">tutaj<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-yaml\">Infrastrukturalny Yaml<\/h4>\n<p><\/p>\n<p>W repozytorium infrastrukturalnym mamy 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>I deployment w <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>I inny deployment w <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>Zauwa\u017c, \u017ce app-deploy nie ma jeszcze zdefiniowanych replik.<\/p>\n<p><\/p>\n<h4 id=\"vypolnenie-nachalnogo-deploya\">Wykonywanie wst\u0119pnego deployu<\/h4>\n<p><\/p>\n<p>Aby uruchomi\u0107 pocz\u0105tkowy deployment, mo\u017cesz r\u0119cznie uruchomi\u0107 pipeline GitlabCI w ga\u0142\u0119zi master. Po tym <code>kubectl<\/code> powinien wy\u015bwietli\u0107 nast\u0119puj\u0105ce:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/e8ea95fe6c3925f46f6430ce2293063c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Widzimy <code>app<\/code> deployment z 10 replikami i app-canary z 0. Istnieje r\u00f3wnie\u017c LoadBalancer, do kt\u00f3rego mo\u017cemy si\u0119 odwo\u0142ywa\u0107 przez <code>curl<\/code> przez 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 Deployment w Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/06e6928002532dbe03b65356964110c7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Widzimy, \u017ce nasza aplikacja testowa zwraca tylko \u201cv1\u201d.<\/p>\n<p><\/p>\n<h3 id=\"vypolnenie-canary-deploya\">Wykonywanie Canary deployu<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-vypustit-novuyu-versiyu-dlya-chasti-polzovateley\">Krok 1: wyda\u0107 now\u0105 wersj\u0119 dla cz\u0119\u015bci u\u017cytkownik\u00f3w<\/h4>\n<p><\/p>\n<p>Ustawili\u015bmy liczb\u0119 replik na 1 w pliku deploy-canary.yaml i obraz nowej wersji:<\/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>W pliku <code>deploy.yaml<\/code> zmienili\u015bmy liczb\u0119 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>Wysy\u0142amy te zmiany do repozytorium, z kt\u00f3rego zostanie uruchomiony deploy (przez GitlabCI) i ostatecznie widzimy:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/b639716b31e41e8eac573fd365ad6780.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Nasz Service b\u0119dzie wskazywa\u0142 na oba deploye, poniewa\u017c oba maj\u0105 selektor app. Z powodu losowego rozk\u0142adu domy\u015blnego w Kubernetes powinni\u015bmy zobaczy\u0107 r\u00f3\u017cne odpowiedzi na ~ 10% zapyta\u0144:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #1: Gitlab CI\" src=\"\/wp-content\/uploads\/2020\/07\/d1177207ebd8952fd1994ed0ebdda6a3.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Bie\u017c\u0105cy stan naszej aplikacji (GitOps, wzi\u0119ty z Gita jako Single Source Of Truth) to obecno\u015b\u0107 dw\u00f3ch deployment\u00f3w z aktywnymi replikami, po jednym dla ka\u017cdej wersji.<\/p>\n<p><\/p>\n<p>~10% u\u017cytkownik\u00f3w zapoznaje si\u0119 z now\u0105 wersj\u0105 i niezamierzanie j\u0105 testuje. Teraz nasta\u0142 czas, aby sprawdzi\u0107 obecno\u015b\u0107 b\u0142\u0119d\u00f3w w logach i danych monitoruj\u0105cych w celu wyszukania problem\u00f3w.<\/p>\n<p><\/p>\n<h4 id=\"shag-2-vypustit-novuyu-versiyu-dlya-vseh-polzovateley\">Krok 2: wypu\u015bci\u0107 now\u0105 wersj\u0119 dla wszystkich u\u017cytkownik\u00f3w<\/h4>\n<p><\/p>\n<p>Zdecydowali\u015bmy, \u017ce wszystko przebieg\u0142o pomy\u015blnie i teraz musimy wdro\u017cy\u0107 now\u0105 wersj\u0119 dla wszystkich u\u017cytkownik\u00f3w. Aby to zrobi\u0107, po prostu aktualizujemy <code>deploy.yaml<\/code> instaluj\u0105c now\u0105 wersj\u0119 obrazu i liczba replik wynosi 10. W <code>deploy-canary.yaml<\/code> ustalamy liczb\u0119 replik z powrotem na 0. Po wdro\u017ceniu rezultat b\u0119dzie nast\u0119puj\u0105cy:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w 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\">Podsumowuj\u0105c<\/h3>\n<p><\/p>\n<p>Dla mnie r\u0119czne uruchomienie wdro\u017cenia w ten spos\u00f3b pomaga zrozumie\u0107, jak \u0142atwo mo\u017cna to skonfigurowa\u0107 za pomoc\u0105 k8s. Poniewa\u017c Kubernetes pozwala na aktualizacj\u0119 wszystkich za po\u015brednictwem API, te kroki mo\u017cna zautomatyzowa\u0107 za pomoc\u0105 skrypt\u00f3w.<\/p>\n<p><\/p>\n<p>Jeszcze jedn\u0105 rzecz\u0105, kt\u00f3r\u0105 nale\u017cy wdro\u017cy\u0107, jest punkt wej\u015bcia testera (LoadBalancer lub przez Ingress), przez kt\u00f3ry mo\u017cna uzyska\u0107 dost\u0119p tylko do nowej wersji. Mo\u017ce by\u0107 u\u017cywany do manualnego podgl\u0105du.<\/p>\n<p><\/p>\n<p>W nast\u0119pnych artyku\u0142ach sprawdzimy inne zautomatyzowane rozwi\u0105zania, kt\u00f3re wdra\u017caj\u0105 wi\u0119kszo\u015b\u0107 tego, co zrobili\u015bmy.<\/p>\n<p><\/p>\n<h2 id=\"takzhe-chitayte-drugie-stati-v-nashem-bloge\">Przeczytaj r\u00f3wnie\u017c inne artyku\u0142y na naszym blogu:<\/h2>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/468779\/\">Jakie by\u0142y skutki migracji z ClickHouse bez autoryzacji na ClickHouse z autoryzacj\u0105<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473578\/\">Budowanie dynamicznych modu\u0142\u00f3w dla Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/news\/t\/502658\/\">Aktualizacja nxs-build-tools \u2014 narz\u0119dzia do budowy pakiet\u00f3w deb i rpm<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473014\/\">Wprowadzenie do autoryzacji Hashicorp Consul dla Kubernetes<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/504762\/\">Z czym musieli\u015bmy si\u0119 zmierzy\u0107 przy u\u017cyciu narz\u0119dzia Csync2<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/347526\/\">Bot Telegram dla Redmine. Jak upro\u015bci\u0107 \u017cycie sobie i innym<\/a><\/noindex><\/li>\n<\/ul>\n<p>\u0179r\u00f3d\u0142o: <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.1.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 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\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"pl_PL\" \/>\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\/pl\/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\udd47Wdro\u017cenie Canary w Kubernetes #1: Gitlab CI | ProHoster","description":"B\u0119dziemy u\u017cywa\u0107 Gitlab CI oraz r\u0119cznego GitOps do wprowadzenia i u\u017cycia wdro\u017cenia Canary w.","canonical_url":"https:\/\/prohoster.info\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pl_PL","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\/pl\/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\/pl\/wp-json\/wp\/v2\/posts\/90272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/comments?post=90272"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/posts\/90272\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media\/90273"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media?parent=90272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/categories?post=90272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/tags?post=90272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}