{"id":38648,"date":"2019-10-31T22:25:04","date_gmt":"2019-10-31T19:25:04","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kratkoe-vvedenie-v-kustomize\/"},"modified":"2019-10-31T22:25:04","modified_gmt":"2019-10-31T19:25:04","slug":"kratkoe-vvedenie-v-kustomize","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","title":{"rendered":"Introdu\u00e7\u00e3o breve ao Kustomize","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Nota do tradutor.<\/b>: O artigo foi escrito por Scott Lowe - um engenheiro com vasta experi\u00eancia em TI, autor\/coautor de sete livros impressos (principalmente sobre VMware vSphere). Atualmente, ele trabalha em sua filial da VMware - Heptio (adquirida em 2016), especializado em computa\u00e7\u00e3o em nuvem e Kubernetes. O texto oferece uma introdu\u00e7\u00e3o concisa e f\u00e1cil de entender sobre gerenciamento de configura\u00e7\u00f5es para Kubernetes usando a tecnologia <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/\">Kustomize<\/a><\/noindex>, que recentemente foi integrada ao K8s.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Introdu\u00e7\u00e3o breve ao Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/099d2281c06d7a294532a816bb6aab21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKustomize \u00e9 uma ferramenta que permite aos usu\u00e1rios \u201cpersonalizar arquivos YAML simples e sem modelos para v\u00e1rios prop\u00f3sitos, mantendo o YAML original intacto e utiliz\u00e1vel\u201d (descri\u00e7\u00e3o extra\u00edda diretamente do <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\">reposit\u00f3rio kustomize no GitHub<\/a><\/noindex>). Kustomize pode ser executado diretamente ou, a partir do Kubernetes 1.14, pode usar <code>kubectl -k<\/code> para acessar suas fun\u00e7\u00f5es (embora, com o Kubernetes 1.15, um bin\u00e1rio separado seja mais recente do que as capacidades embutidas no kubectl). <i>(<b>Nota do tradutor.<\/b>: E com o recente lan\u00e7amento <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/467477\/\">Kubernetes 1.16<\/a><\/noindex> (a prop\u00f3sito, seu desenvolvimento agora \u00e9 feito em um reposit\u00f3rio separado), ou seja, para processar arquivos YAML adicionais de diret\u00f3rios especiais de kustomization (detalhes sobre seu uso podem ser encontrados em <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/1177\">suportado<\/a><\/noindex> , tamb\u00e9m na ferramenta kubeadm.)<\/i> Nesta publica\u00e7\u00e3o, quero apresentar aos leitores os fundamentos do kustomize.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Em sua forma\/uso mais simples, o kustomize \u00e9 apenas um conjunto de recursos (arquivos YAML que definem objetos Kubernetes: Deployments, Services, etc.) mais uma lista de instru\u00e7\u00f5es sobre as mudan\u00e7as que precisam ser feitas nesses recursos. Assim como o make usa um conjunto de instru\u00e7\u00f5es contidas em <code>Makefile<\/code>, e o Docker constr\u00f3i um cont\u00eainer com base nas instru\u00e7\u00f5es de <code>Dockerfile<\/code>, o kustomize usa <code>kustomization.yaml<\/code> para armazenar as prescri\u00e7\u00f5es sobre quais altera\u00e7\u00f5es o usu\u00e1rio deseja fazer no conjunto de recursos.<\/p>\n<p>Aqui est\u00e1 um exemplo de arquivo <code>kustomization.yaml<\/code>:<\/p>\n<pre><code class=\"plaintext\">resources:\n- deployment.yaml\n- service.yaml\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nN\u00e3o tentarei falar sobre todos os campos poss\u00edveis no arquivo <code>kustomization.yaml<\/code> (o que \u00e9 bem escrito <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/fields.md\">aqui<\/a><\/noindex>), mas farei uma breve explica\u00e7\u00e3o de um exemplo espec\u00edfico:<\/p>\n<ul>\n<li> Campo <code>resources<\/code> indica quais (quais recursos) o kustomize far\u00e1 altera\u00e7\u00f5es. Neste caso, ele procurar\u00e1 recursos nos arquivos <code>deployment.yaml<\/code> e <code>service.yaml<\/code> em seu diret\u00f3rio (caminhos completos ou relativos podem ser especificados, se necess\u00e1rio).<\/li>\n<li> Campo <code>namePrefix<\/code> obriga o kustomize a adicionar um prefixo espec\u00edfico (neste caso \u2014 <code>dev-<\/code>) ao atributo <code>nome<\/code> de todos os recursos definidos no campo <code>resources<\/code>. Assim, se houver um Deployment <code>nome<\/code> com o valor <code>nginx-deployment<\/code>, o kustomize o transformar\u00e1 em <code>dev-nginx-deployment<\/code>.<\/li>\n<li> Campo <code>namespace<\/code> obriga o kustomize a adicionar um namespace especificado a todos os recursos. Neste caso, o Deployment e o Service estar\u00e3o no namespace <code>desenvolvimento<\/code>.<\/li>\n<li> Finalmente, o campo <code>commonLabels<\/code> cont\u00e9m um conjunto de r\u00f3tulos que ser\u00e1 adicionado a todos os recursos. No nosso exemplo, o kustomize atribuir\u00e1 aos recursos um r\u00f3tulo chamado <code>environment<\/code> e valor <code>desenvolvimento<\/code>.<\/li>\n<\/ul>\n<p>\nSe o usu\u00e1rio executar <code>kustomize build .<\/code> no diret\u00f3rio com o arquivo <code>kustomization.yaml<\/code> e os recursos necess\u00e1rios (ou seja, os arquivos <code>deployment.yaml<\/code> e <code>service.yaml<\/code>), a sa\u00edda ser\u00e1 um texto com as altera\u00e7\u00f5es definidas em <code>kustomization.yaml<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"Introdu\u00e7\u00e3o breve ao Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/f15c7ccb5f200c7e9b5a25142c364cb8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Nota do tradutor.<\/b>: Ilustra\u00e7\u00e3o da documenta\u00e7\u00e3o do projeto sobre o uso \"simples\" do kustomize<\/i><\/p>\n<p>A sa\u00edda pode ser redirecionada, se necess\u00e1rio, para registrar as altera\u00e7\u00f5es:<\/p>\n<pre><code class=\"bash\">kustomize build . &gt; custom-config.yaml<\/code><\/pre>\n<p>\nA sa\u00edda \u00e9 determin\u00edstica (com os mesmos dados de entrada, os mesmos resultados de sa\u00edda ser\u00e3o produzidos), portanto, n\u00e3o \u00e9 necess\u00e1rio salvar o resultado em um arquivo. Em vez disso, ele pode ser passado diretamente para outro comando:<\/p>\n<pre><code class=\"bash\">kustomize build . | kubectl apply -f -<\/code><\/pre>\n<p>\nO acesso \u00e0s fun\u00e7\u00f5es do kustomize tamb\u00e9m pode ser obtido atrav\u00e9s de <code>kubectl -k<\/code> (a partir da vers\u00e3o 1.14 do Kubernetes). No entanto, tenha em mente que o pacote kustomize separado \u00e9 atualizado mais rapidamente do que o integrado ao kubectl (pelo menos, assim \u00e9 com o lan\u00e7amento do Kubernetes 1.15).<\/p>\n<p>Os leitores podem perguntar: \"Por que todas essas complica\u00e7\u00f5es, se posso editar os arquivos diretamente?\". \u00d3tima pergunta. No nosso exemplo, realmente <i>\u00e9 poss\u00edvel<\/i> modificar arquivos <code>deployment.yaml<\/code> e <code>service.yaml<\/code> diretamente, mas e se eles forem um fork de algum projeto? Modificar os arquivos diretamente dificulta (se n\u00e3o impossibilita) o rebase do fork, quando mudan\u00e7as s\u00e3o feitas na fonte\/origem. O uso do kustomize permite centralizar essas altera\u00e7\u00f5es em um arquivo <code>kustomization.yaml<\/code>, mantendo os arquivos originais intocados e, assim, facilitando a necessidade de rebase dos arquivos originais.<\/p>\n<p>As vantagens do kustomize tornam-se evidentes em casos de uso mais complexos. No exemplo acima, <code>kustomization.yaml<\/code> e os recursos est\u00e3o no mesmo diret\u00f3rio. No entanto, o kustomize suporta cen\u00e1rios em que h\u00e1 uma configura\u00e7\u00e3o base e v\u00e1rias de suas variantes, tamb\u00e9m conhecidas como <i>Al\u00e9m disso:<\/i>. Por exemplo, o usu\u00e1rio pode pegar um Deployment e um Service para o nginx, que usei como exemplo, e criar vers\u00f5es (ou variantes) de desenvolvimento, staging e produ\u00e7\u00e3o desses arquivos. Para isso, ele precisar\u00e1 dos overlays mencionados acima e, de fato, dos pr\u00f3prios recursos base.<\/p>\n<p>Para ilustrar a ideia de overlays e recursos base <i>(base resources)<\/i>, suponha que os diret\u00f3rios tenham a seguinte estrutura:<\/p>\n<pre><code class=\"plaintext\">- base\n  - deployment.yaml\n  - service.yaml\n  - kustomization.yaml\n- overlays\n  - dev\n    - kustomization.yaml\n  - staging\n    - kustomization.yaml\n  - prod\n    - kustomization.yaml<\/code><\/pre>\n<p>\nNo arquivo <code>base\/kustomization.yaml<\/code> os usu\u00e1rios atrav\u00e9s do campo <code>resources<\/code> simplesmente declaram os recursos que o kustomize deve incluir.<\/p>\n<p>Em cada um dos arquivos <code>overlays\/{dev,staging,prod}\/kustomization.yaml<\/code> os usu\u00e1rios se referem \u00e0 configura\u00e7\u00e3o base no campo <code>resources<\/code>, e ent\u00e3o especificam as mudan\u00e7as espec\u00edficas para <i>este ambiente<\/i>. Por exemplo, o arquivo <code>overlays\/dev\/kustomization.yaml<\/code> pode parecer como o exemplo acima:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/base\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nEnquanto isso, o arquivo <code>overlays\/prod\/kustomization.yaml<\/code> pode ser completamente diferente:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/base\nnamePrefix: prod-\nnamespace: production\ncommonLabels:\n  environment: production\n  sre-team: blue<\/code><\/pre>\n<p>\nQuando um usu\u00e1rio executa <code>kustomize build .<\/code> no diret\u00f3rio <code>overlays\/dev<\/code>, o kustomize gerar\u00e1 a variante de desenvolvimento. Se executar <code>kustomize build .<\/code> no diret\u00f3rio <code>overlays\/prod<\/code> , obter\u00e1 a variante de produ\u00e7\u00e3o. E tudo isso \u2014 sem fazer nenhuma altera\u00e7\u00e3o nos arquivos originais <i>(base)<\/i> e tudo isso \u2014 de uma maneira declarativa e determin\u00edstica. \u00c9 poss\u00edvel fazer commit da configura\u00e7\u00e3o base e dos diret\u00f3rios de overlay diretamente no sistema de controle de vers\u00e3o, sabendo que com base nesses arquivos sempre pode-se reproduzir a configura\u00e7\u00e3o desejada.<\/p>\n<p><img decoding=\"async\" alt=\"Introdu\u00e7\u00e3o breve ao Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/959af6422f6ae4c1b8d755e9c5728d38.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Nota do tradutor.<\/b>: Ilustra\u00e7\u00e3o da documenta\u00e7\u00e3o do projeto sobre o uso de overlays no kustomize<\/i><\/p>\n<p>O Kustomize pode <i>muito<\/i> mais do que \u00e9 abordado neste artigo. No entanto, espero que ele sirva como uma boa introdu\u00e7\u00e3o.<\/p>\n<h2>Recursos adicionais<\/h2>\n<p>\nH\u00e1 muitos bons artigos e publica\u00e7\u00f5es sobre kustomize. Aqui est\u00e3o alguns que considerei especialmente \u00fateis:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/levelup.gitconnected.com\/kubernetes-change-base-yaml-config-for-different-environments-prod-test-6224bfb6cdd6\">Mude a configura\u00e7\u00e3o YAML base para diferentes ambientes prod\/test usando Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.stack-labs.com\/code\/kustomize-101\/\">Kustomize \u2014 A maneira correta de fazer modelagem no Kubernetes<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-kubernetes-objects\/kustomization\/\">Gerenciamento Declarativo de Objetos Kubernetes Usando Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/testingclouds.wordpress.com\/2018\/07\/20\/844\/\">Personalizando Gr\u00e1ficos Helm Upstream com Kustomize<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<i><b>Nota do tradutor.<\/b>: Tamb\u00e9m \u00e9 poss\u00edvel recomendar um bloco de links, publicados como <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/#resources\">Recursos<\/a><\/noindex> no site da ferramenta, e a cole\u00e7\u00e3o subsequente de v\u00eddeos com as \u00faltimas palestras sobre kustomize.<\/i><\/p>\n<p>Se voc\u00ea tiver d\u00favidas ou sugest\u00f5es para melhorar este material, estou sempre aberto a feedback. Voc\u00ea pode entrar em contato comigo no <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/scott_lowe\">Twitter<\/a><\/noindex> ou para <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">canal Slack do Kubernetes<\/a><\/noindex>. Divirta-se modificando seus manifests usando o kustomize!<\/p>\n<h2>P.S. do tradutor<\/h2>\n<p>\nConfira tamb\u00e9m em nosso blog:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/462707\/\">Ferramentas para desenvolvedores de aplicativos executados no Kubernetes<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445196\/\">Kubernetes 1.14: vis\u00e3o geral das principais inova\u00e7\u00f5es<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468259\/\">Cinco principais conclus\u00f5es do Helm Summit 2019 em Amsterd\u00e3<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/420437\/\">Introdu\u00e7\u00e3o pr\u00e1tica ao gerenciador de pacotes para Kubernetes \u2014 Helm<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Fonte: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/469179\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere). \u0421\u0435\u0439\u0447\u0430\u0441 \u043e\u043d \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0432 \u0435\u0451 \u0434\u043e\u0447\u0435\u0440\u043d\u0435\u0439 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 VMware \u2014 Heptio (\u043f\u043e\u0433\u043b\u043e\u0449\u0435\u043d\u0430 \u0432 2016 \u0433\u043e\u0434\u0443), \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0437\u0438\u0440\u0443\u044f\u0441\u044c \u043d\u0430 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f\u0445 \u0438 Kubernetes. \u0421\u0430\u043c \u0436\u0435 \u0442\u0435\u043a\u0441\u0442 \u0441\u043b\u0443\u0436\u0438\u0442 \u0451\u043c\u043a\u0438\u043c \u0438 \u043f\u0440\u043e\u0441\u0442\u044b\u043c \u0434\u043b\u044f \u043f\u043e\u043d\u0438\u043c\u0430\u043d\u0438\u044f \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435\u043c \u0432 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u044f\u043c\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28991,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38648","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=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).\" \/>\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\/kratkoe-vvedenie-v-kustomize\" \/>\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\udd47\u041a\u0440\u0430\u0442\u043a\u043e\u0435 \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 Kustomize | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize\" \/>\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=\"2019-10-31T19:25:04+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:25:04+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\udd47Uma breve introdu\u00e7\u00e3o ao Kustomize | ProHoster","description":"Nota do tradutor: O artigo foi escrito por Scott Lowe \u2014 um engenheiro experiente em TI, autor\/coautor de sete livros impressos (principalmente sobre VMware vSphere).","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","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\udd47\u041a\u0440\u0430\u0442\u043a\u043e\u0435 \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 Kustomize | ProHoster","og:description":"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u0421\u0442\u0430\u0442\u044c\u044e \u043d\u0430\u043f\u0438\u0441\u0430\u043b Scott Lowe \u2014 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u0441 \u0431\u043e\u043b\u044c\u0448\u0438\u043c \u0441\u0442\u0430\u0436\u0435\u043c \u0432 \u0418\u0422, \u044f\u0432\u043b\u044f\u044e\u0449\u0438\u0439\u0441\u044f \u0430\u0432\u0442\u043e\u0440\u043e\u043c\/\u0441\u043e\u0430\u0432\u0442\u043e\u0440\u043e\u043c \u0441\u0435\u043c\u0438 \u043f\u0435\u0447\u0430\u0442\u043d\u044b\u0445 \u043a\u043d\u0438\u0433 (\u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e VMware vSphere).","og:url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","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":"2019-10-31T19:25:04+00:00","article:modified_time":"2019-10-31T19:25:04+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38648","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":"2026-01-23 22:54:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:05:23","updated":"2026-01-23 22:54:19","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\/38648","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=38648"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/38648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/28991"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=38648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=38648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=38648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}