{"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\/pt\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","title":{"rendered":"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster","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\">Usaremos Gitlab CI e GitOps manual para implementar e utilizar o Canary deployment no Kubernetes<\/h4>\n<p>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/03a53dec150529deb3438efaeaa8a1bd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h4 id=\"stati-iz-etogo-cikla\">Artigos desta s\u00e9rie:<\/h4>\n<p><\/p>\n<ul>\n<li>(este artigo)<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/en\/company\/nixys\/blog\/513118\/\">Canary Deployment usando ArgoCI<\/a><\/noindex><\/li>\n<li>Canary Deployment usando Istio<\/li>\n<li>Canary Deployment usando Jenkins-X Istio Flagger<\/li>\n<\/ul>\n<p><\/p>\n<p>Faremos o Canary deployment manualmente atrav\u00e9s de GitOps e cria\u00e7\u00e3o\/modifica\u00e7\u00e3o de recursos principais do Kubernetes. <strong>Este artigo \u00e9 destinado principalmente para familiariza\u00e7\u00e3o<\/strong> com o funcionamento do Canary deployment no Kubernetes, pois existem m\u00e9todos mais eficientes de automa\u00e7\u00e3o que abordaremos nos pr\u00f3ximos artigos.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" 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>Na estrat\u00e9gia de Canary, as atualiza\u00e7\u00f5es s\u00e3o inicialmente aplicadas apenas para uma parte dos usu\u00e1rios. Por meio de monitoramento, dados de logs, testes manuais ou outros canais de feedback, a vers\u00e3o \u00e9 testada antes de sua aplica\u00e7\u00e3o para todos os usu\u00e1rios.<\/p>\n<p><\/p>\n<h3 id=\"kubernetes-deployment-rolling-update\">Kubernetes Deployment (atualiza\u00e7\u00e3o gradual)<\/h3>\n<p><\/p>\n<p>A estrat\u00e9gia padr\u00e3o para o Kubernetes Deployment \u00e9 a atualiza\u00e7\u00e3o gradual, onde um determinado n\u00famero de pods com novas vers\u00f5es de imagens \u00e9 iniciado. Se forem criados sem problemas, os pods com as vers\u00f5es antigas das imagens s\u00e3o encerrados e novos pods s\u00e3o criados em paralelo.<\/p>\n<p><\/p>\n<h3 id=\"gitops\">GitOps<\/h3>\n<p><\/p>\n<p>Usamos GitOps neste exemplo, pois:<\/p>\n<p><\/p>\n<ul>\n<li>usamos o Git como a \u00fanica fonte da verdade<\/li>\n<li>usamos opera\u00e7\u00f5es Git para constru\u00e7\u00e3o e deployment (sem comandos, exceto git tag\/merge s\u00e3o necess\u00e1rios)<\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"primer\">Exemplo<\/h3>\n<p><\/p>\n<p>Vamos seguir uma boa pr\u00e1tica \u2014 ter um reposit\u00f3rio para o c\u00f3digo dos aplicativos e outro para a infraestrutura.<\/p>\n<p><\/p>\n<h4 id=\"repozitoriy-dlya-prilozheniy\">Reposit\u00f3rio para aplicativos<\/h4>\n<p><\/p>\n<p>Esta \u00e9 uma API muito simples em Python+Flask, que retorna uma resposta em formato JSON. Compilaremos o pacote atrav\u00e9s do GitlabCI e enviaremos o resultado para o Gitlab Registry. No registry temos duas vers\u00f5es diferentes de releases:<\/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>A \u00fanica diferen\u00e7a entre elas \u00e9 a altera\u00e7\u00e3o no arquivo JSON retornado. Usamos esta aplica\u00e7\u00e3o para visualiza\u00e7\u00e3o m\u00e1xima do qual vers\u00e3o estamos interagindo.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-repozitoriy\">Reposit\u00f3rio de infraestrutura<\/h4>\n<p><\/p>\n<p>Neste reposit\u00f3rio, faremos o deployment atrav\u00e9s do GitlabCI no Kubernetes, <code>.gitlab-ci.yml<\/code> fica da seguinte forma:<\/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>Para execut\u00e1-lo por conta pr\u00f3pria, voc\u00ea precisar\u00e1 de um cluster, podendo usar o 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>Voc\u00ea precisa fazer um 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> e criar uma vari\u00e1vel <code>KUBECONFIG<\/code> no GitlabCI, que conter\u00e1 a configura\u00e7\u00e3o para acesso <code>kubectl<\/code> ao seu cluster.<\/p>\n<p><\/p>\n<p>Sobre como obter credenciais para o cluster (Gcloud) voc\u00ea pode ler <noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/faun\/manually-connect-to-your-kubernetes-cluster-from-the-outside-d852346a7f0a\">aqui<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h4 id=\"infrastrukturnyy-yaml\">Yaml de infraestrutura<\/h4>\n<p><\/p>\n<p>No reposit\u00f3rio de infraestrutura, temos um 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>E deployment em <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>E outro deployment em <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>Observe que o app-deploy ainda n\u00e3o tem r\u00e9plicas definidas.<\/p>\n<p><\/p>\n<h4 id=\"vypolnenie-nachalnogo-deploya\">Execu\u00e7\u00e3o da implanta\u00e7\u00e3o inicial<\/h4>\n<p><\/p>\n<p>Para iniciar o deployment inicial, voc\u00ea pode executar o pipeline do GitlabCI manualmente no branch principal. Depois disso, <code>kubectl<\/code> deve apresentar o seguinte:<\/p>\n<p>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/e8ea95fe6c3925f46f6430ce2293063c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>N\u00f3s vemos <code>app<\/code> deployment com 10 r\u00e9plicas e app-canary com 0. Tamb\u00e9m h\u00e1 um LoadBalancer que podemos acessar atrav\u00e9s do <code>curl<\/code> IP Externo:<\/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=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/06e6928002532dbe03b65356964110c7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>N\u00f3s vemos que nosso aplicativo de teste retorna apenas 'v1'.<\/p>\n<p><\/p>\n<h3 id=\"vypolnenie-canary-deploya\">Execu\u00e7\u00e3o do Canary deployment<\/h3>\n<p><\/p>\n<h4 id=\"shag-1-vypustit-novuyu-versiyu-dlya-chasti-polzovateley\">Passo 1: liberar uma nova vers\u00e3o para parte dos usu\u00e1rios<\/h4>\n<p><\/p>\n<p>Definimos o n\u00famero de r\u00e9plicas como 1 no arquivo deploy-canary.yaml e a imagem da nova vers\u00e3o:<\/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>No arquivo <code>deploy.yaml<\/code> n\u00f3s mudamos o n\u00famero de r\u00e9plicas para 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>Estamos enviando essas altera\u00e7\u00f5es para o reposit\u00f3rio, de onde o deployment ser\u00e1 iniciado (via GitlabCI) e vemos o resultado:<\/p>\n<p>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/b639716b31e41e8eac573fd365ad6780.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>Nosso Service apontar\u00e1 para ambos os deployments, j\u00e1 que ambos t\u00eam o seletor app. Devido \u00e0 distribui\u00e7\u00e3o aleat\u00f3ria padr\u00e3o no Kubernetes, devemos ver respostas diferentes em ~ 10% das solicita\u00e7\u00f5es:<\/p>\n<p>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/d1177207ebd8952fd1994ed0ebdda6a3.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<p>O estado atual do nosso aplicativo (GitOps, retirado do Git como a \u00danica Fonte da Verdade) consiste na presen\u00e7a de dois deployments com r\u00e9plicas ativas, um para cada vers\u00e3o.<\/p>\n<p><\/p>\n<p>~10% dos usu\u00e1rios est\u00e3o se familiarizando com a nova vers\u00e3o e testando-a inadvertidamente. Agora \u00e9 hora de verificar se h\u00e1 erros nos logs e nos dados de monitoramento para encontrar problemas.<\/p>\n<p><\/p>\n<h4 id=\"shag-2-vypustit-novuyu-versiyu-dlya-vseh-polzovateley\">Passo 2: liberar uma nova vers\u00e3o para todos os usu\u00e1rios<\/h4>\n<p><\/p>\n<p>Decidimos que tudo correu bem e agora precisamos implementar a nova vers\u00e3o para todos os usu\u00e1rios. Para isso, simplesmente atualizamos <code>deploy.yaml<\/code> instalando a nova vers\u00e3o da imagem e setando o n\u00famero de r\u00e9plicas igual a 10. No <code>deploy-canary.yaml<\/code> Definimos o n\u00famero de r\u00e9plicas como igual a zero. Ap\u00f3s o deployment, o resultado ser\u00e1 o seguinte:<\/p>\n<p>\n<img decoding=\"async\" alt=\"\ud83e\udd47StealthWatch: an\u00e1lise e investiga\u00e7\u00e3o de incidentes. Parte 3 | ProHoster\" src=\"\/wp-content\/uploads\/2020\/07\/a31aafe96a09c6d2651b2bf7add4dd29.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3 id=\"podvodya-itog\">Resumindo<\/h3>\n<p><\/p>\n<p>Para mim, iniciar o deployment manualmente dessa forma ajuda a entender como ele pode ser facilmente configurado com o k8s. Como o Kubernetes permite atualizar tudo atrav\u00e9s da API, esses passos podem ser automatizados por scripts.<\/p>\n<p><\/p>\n<p>Outra coisa que precisamos implementar \u00e9 a entrada do testador (LoadBalancer ou atrav\u00e9s do Ingress), pela qual podemos acessar apenas a nova vers\u00e3o. Isso pode ser usado para visualiza\u00e7\u00e3o manual.<\/p>\n<p><\/p>\n<p>Nos pr\u00f3ximos artigos, iremos explorar outras solu\u00e7\u00f5es automatizadas que implementam a maior parte do que fizemos.<\/p>\n<p><\/p>\n<h2 id=\"takzhe-chitayte-drugie-stati-v-nashem-bloge\">Leia tamb\u00e9m outros artigos em nosso blog:<\/h2>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/468779\/\">Para onde nos levou a migra\u00e7\u00e3o do ClickHouse sem autentica\u00e7\u00e3o para o ClickHouse com autentica\u00e7\u00e3o<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473578\/\">Compila\u00e7\u00e3o de m\u00f3dulos din\u00e2micos para Nginx<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/news\/t\/502658\/\">Atualiza\u00e7\u00e3o do nxs-build-tools \u2014 assistente para a constru\u00e7\u00e3o de pacotes deb e rpm<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/473014\/\">Introdu\u00e7\u00e3o \u00e0 Autoriza\u00e7\u00e3o do Kubernetes do Hashicorp Consul<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/504762\/\">Com o que tivemos que lidar ao usar a ferramenta Csync2<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/nixys\/blog\/347526\/\">Bot do Telegram para Redmine. Como facilitar a vida para voc\u00ea e para os outros<\/a><\/noindex><\/li>\n<\/ul>\n<p>Fonte: <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.3 - 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\/pt\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"pt_PT\" \/>\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\/pt\/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 no Kubernetes #1: Gitlab CI | ProHoster","description":"Usaremos o Gitlab CI e GitOps manual para implementar e utilizar o Canary deployment.","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/canary-deployment-v-kubernetes-1-gitlab-ci","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","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\/pt\/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\/pt\/wp-json\/wp\/v2\/posts\/90272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=90272"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/90272\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/90273"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=90272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=90272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=90272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}