{"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\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","title":{"rendered":"Canary Deployment w 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\">B\u0119dziemy u\u017cywa\u0107 natywnego kontrolera wdra\u017cania Argo Rollouts w k8s oraz GitlabCI do uruchomienia wdro\u017cenia typu Canary w Kubernetes<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w 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\">Artyku\u0142y z tej serii<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">Canary Deployment w Kubernetes #1: Gitlab CI<\/a><\/noindex><\/li>\n<li>(Ten artyku\u0142)<\/li>\n<li>Wdro\u017cenie Canary z u\u017cyciem Istio<\/li>\n<li>Wdro\u017cenie Canary z u\u017cyciem 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>Mamy nadziej\u0119, \u017ce przeczyta\u0142e\u015b <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/512766\/\">pierwsz\u0105 cz\u0119\u015b\u0107<\/a><\/noindex>, w kt\u00f3rym kr\u00f3tko wyja\u015bniali\u015bmy, czym s\u0105 wdro\u017cenia typu Canary. Pokazali\u015bmy r\u00f3wnie\u017c, jak je zrealizowa\u0107 z u\u017cyciem standardowych zasob\u00f3w Kubernetes.<\/p>\n<p><\/p>\n<h3 id=\"argo-rollouts\">Argo Rollouts<\/h3>\n<p><\/p>\n<p>Argo Rollouts to natywny kontroler wdra\u017cania dla Kubernetes. Oferuje CRD (Custom Resource Definition) dla Kubernetes. Dzi\u0119ki niemu mo\u017cemy korzysta\u0107 z nowej jednostki: <code>Rollout<\/code>, kt\u00f3ra zarz\u0105dza wdro\u017ceniami blue-green i canary z r\u00f3\u017cnymi opcjami konfiguracji.<\/p>\n<p><\/p>\n<blockquote><p>Kontroler Argo Rollouts, u\u017cywany przez zas\u00f3b <code>Rollout,<\/code> pozwala na u\u017cycie dodatkowych strategii wdra\u017cania, takich jak blue-green i canary w Kubernetes. Zas\u00f3b <code>Rollout<\/code> oferuje funkcjonalno\u015b\u0107 r\u00f3wnowa\u017cn\u0105 <code>Deployment<\/code>, tylko z dodatkowymi strategiami wdra\u017cania.<br \/>\nZas\u00f3b <code>Deployments<\/code> ma dwie strategie dla wdro\u017cenia: <code>RollingUpdate<\/code> i <code>Recreate<\/code>. Pomimo \u017ce te strategie s\u0105 odpowiednie dla wi\u0119kszo\u015bci przypadk\u00f3w, do wdro\u017ce\u0144 na serwery w bardzo du\u017cej skali stosuje si\u0119 dodatkowe strategie, takie jak blue-green lub canary, kt\u00f3re nie s\u0105 dost\u0119pne w kontrolerze Deployment. Aby u\u017cywa\u0107 tych strategii w Kubernetes, u\u017cytkownicy musieli pisa\u0107 skrypty na swoich Wdro\u017ceniach. Kontroler Argo Rollouts oferuje te strategie jako \u0142atwe do skonfigurowania parametry deklaratywne.<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>Istnieje r\u00f3wnie\u017c Argo CI, kt\u00f3ry zapewnia wygodny interfejs webowy do u\u017cycia razem z Rollouts, przyjrzymy si\u0119 mu w nast\u0119pnym artykule.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-argo-rollouts\">Instalacja Argo Rollouts<\/h3>\n<p><\/p>\n<h4 id=\"na-storone-servera\">Po stronie serwera<\/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>W naszej repozytorium infrastrukturalnej (patrz poni\u017cej) dodali\u015bmy ju\u017c install.yaml jako i\/k8s\/argo-rollouts\/install.yaml. Dzi\u0119ki temu GitlabCI zainstaluje go w klastrze.<\/p>\n<p><\/p>\n<h4 id=\"na-storone-klienta-kubectl-plugin\">Po stronie klienta (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\">Aplikacja przyk\u0142ad<\/h3>\n<p><\/p>\n<p>Dobr\u0105 praktyk\u0105 jest posiadanie oddzielnych repozytori\u00f3w dla kodu aplikacji i dla infrastruktury.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniya\">Repozytorium dla aplikacji<\/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>Jest to bardzo proste API w Pythonie + Flask, zwracaj\u0105ce odpowied\u017a w formacie JSON. Zbudujemy pakiet, u\u017cywaj\u0105c GitlabCI i wypchniemy wynik do Gitlab Registry. W rejestrze mamy dwie r\u00f3\u017cne wersje wydania:<\/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>Jedyn\u0105 r\u00f3\u017cnic\u0105 mi\u0119dzy nimi jest zwracany plik JSON. U\u017cywamy tej aplikacji do maksymalnie prostego wizualizowania, z jak\u0105 wersj\u0105 si\u0119 komunikujemy.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-repozitoriy\">Repozytorium infrastrukturalne<\/h4>\n<p><\/p>\n<p>W tym repozytorium b\u0119dziemy u\u017cywa\u0107 GitlabCI do wdra\u017cania w Kubernetes, plik .gitlab-ci.yml wygl\u0105da nast\u0119puj\u0105co:<\/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>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\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><noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/faun\/manually-connect-to-your-kubernetes-cluster-from-the-outside-d852346a7f0a\">Tutaj<\/a><\/noindex> mo\u017cna przeczyta\u0107 o tym, jak uzyska\u0107 dane uwierzytelniaj\u0105ce dla klastra (Gcloud).<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-yaml\">Infrastrukturalny Yaml<\/h4>\n<p><\/p>\n<p>Wewn\u0105trz repozytorium infrastrukturalnego mamy 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>i 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 can be manually resumed by running `kubectl argo rollouts promote ROLLOUT`\n     - pause: {}\n     - setWeight: 50\n     - pause: { duration: 120 } # dwie minuty<\/code><\/pre>\n<p><\/p>\n<p><code>Rollout<\/code> dzia\u0142a tak samo jak Deployment. Je\u015bli nie zdefiniujemy strategii aktualizacji (jak canary tutaj), b\u0119dzie zachowywa\u0107 si\u0119 jak domy\u015blny rolling-update Deployment.<\/p>\n<p><\/p>\n<p>Okre\u015blamy dwa kroki w yaml dla wdro\u017cenia canary:<\/p>\n<p><\/p>\n<ol>\n<li>10% ruchu na canary (czekaj na r\u0119czn\u0105 zgod\u0119)<\/li>\n<li>50% ruchu na canary (czekaj 2 minuty, a nast\u0119pnie kontynuuj do 100%)<\/li>\n<\/ol>\n<p><\/p>\n<h3 id=\"vypolnenie-nachalnogo-deploya\">Wykonywanie wst\u0119pnego deployu<\/h3>\n<p><\/p>\n<p>Po pocz\u0105tkowym wdro\u017ceniu nasze zasoby b\u0119d\u0105 wygl\u0105da\u0142y tak:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/2f161eb3c80382bbe4f14a1fd199f1d6.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>I otrzymujemy odpowied\u017a tylko od pierwszej wersji aplikacji:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w 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\">Wykonujemy wdro\u017cenie canary<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-10-trafika\">Krok 1: 10% ruchu<\/h4>\n<p><\/p>\n<p>Aby rozpocz\u0105\u0107 wdro\u017cenie canary, wystarczy zmieni\u0107 wersj\u0119 obrazu, jak zwykle zrobimy to w przypadku wdro\u017ce\u0144:<\/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>I puszczamy zmiany, wi\u0119c Gitlab CI wykonuje wdro\u017cenie i widzimy zmiany:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/ee069d8108e6ac211827b01390c45910.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Teraz, je\u015bli zwr\u00f3cimy si\u0119 do us\u0142ugi:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/0be8a02c6ab6166d230818c43bbae3d1.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u015awietnie! Jeste\u015bmy w trakcie naszego wdro\u017cenia canary. Mo\u017cemy zobaczy\u0107 post\u0119p, uruchamiaj\u0105c:<\/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 w 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% ruchu:<\/h4>\n<p><\/p>\n<p>Teraz przechodzimy do nast\u0119pnego kroku: przekierowanie 50% ruchu. Ustawili\u015bmy, aby ten krok by\u0142 uruchamiany r\u0119cznie:<\/p>\n<p><\/p>\n<p><code>kubectl argo rollouts promote rollout-canary # kontynuuj do kroku 2<\/code><\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/c856b7a60930cd5f6484ebe5a9080ffd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>I nasza aplikacja zwr\u00f3ci\u0142a 50% odpowiedzi od nowych wersji:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/502638210f546c5d973fc284beea1ec5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>I przegl\u0105d rollout:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/64e996d9681a88475af31b09ecf61a3f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>\u015awietnie.<\/p>\n<p><\/p>\n<h4 id=\"shag-3-100-trafika\">Krok 3: 100% ruchu:<\/h4>\n<p><\/p>\n<p>Ustawili\u015bmy, aby po 2 minutach krok z 50% ko\u0144czy\u0142 si\u0119 automatycznie i uruchamia\u0142 krok ze 100%:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/d7eee8f41fcbd9c186b37666ea6c10fe.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>I wynik aplikacji:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/f66c21e326f2bf52b29b460fc6e84957.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>I przegl\u0105d rollout:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Canary Deployment w Kubernetes #2: Argo Rollouts\" src=\"\/wp-content\/uploads\/2020\/07\/5485ddc238b4eaad9e14d338acc116a8.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Wdro\u017cenie canary zako\u0144czone.<\/p>\n<p><\/p>\n<h4 id=\"eschyo-primery-s-argo-rollouts\">Jeszcze przyk\u0142ady z Argo Rollouts<\/h4>\n<p><\/p>\n<p>Oto kolejne przyk\u0142ady, na przyk\u0142ad jak skonfigurowa\u0107 podgl\u0105d \u015brodowiska i por\u00f3wnania oparte na 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\">Wideo o Argo Rollouts i Argo CI<\/h4>\n<p><\/p>\n<p>Naprawd\u0119 polecam to wideo, pokazuje, jak Argo Rollouts i Argo CI wsp\u00f3\u0142dzia\u0142aj\u0105:<\/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=\"Odtwarzaj wideo\" 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\">Podsumowanie<\/h2>\n<p><\/p>\n<p>Bardzo podoba mi si\u0119 pomys\u0142 u\u017cywania CRD, kt\u00f3re zarz\u0105dzaj\u0105 tworzeniem dodatkowych typ\u00f3w deployments lub replicasets, kierowaniem ruchu itd. Praca z nimi przebiega g\u0142adko. Nast\u0119pnie chcia\u0142bym przetestowa\u0107 integracj\u0119 z Argo CI.<\/p>\n<p><\/p>\n<p>Jednak wydaje si\u0119, \u017ce nadchodzi du\u017ce po\u0142\u0105czenie Argo CI i Flux CI, wi\u0119c mog\u0119 poczeka\u0107 na now\u0105 wersj\u0119: <noindex><a rel=\"nofollow\" href=\"https:\/\/www.weave.works\/blog\/argo-flux-join-forces\">Argo Flux<\/a><\/noindex>. <\/p>\n<p><\/p>\n<p>Czy mieli Pa\u0144stwo do\u015bwiadczenie z Argo Rollouts lub Argo CI?<\/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\/en\/company\/nixys\/blog\/470568\/\">Blue-Green Deployment aplikacji na Spring z serwerem Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/480072\/\">Kubernetes: dlaczego tak wa\u017cne jest skonfigurowanie zarz\u0105dzania zasobami systemu?<\/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\/en\/company\/nixys\/blog\/481992\/\">Tekton Pipeline \u2014 pipelines natywne dla Kubernetes<\/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\/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\/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.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 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\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts\" \/>\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 #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\/pl\/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 w Kubernetes #2: Argo Rollouts | ProHoster","description":"B\u0119dziemy korzysta\u0107 z natywnego kontrolera wdro\u017ce\u0144 k8s Argo Rollouts oraz GitlabCI.","canonical_url":"https:\/\/prohoster.info\/pl\/blog\/administrirovanie\/canary-deployment-v-kubernetes-2-argo-rollouts","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 #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\/pl\/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\/pl\/wp-json\/wp\/v2\/posts\/90373","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=90373"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/posts\/90373\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media\/90374"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media?parent=90373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/categories?post=90373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/tags?post=90373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}