{"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\/ro\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","title":{"rendered":"\ud83e\udd47Kubernetes 1.16: revizuirea caracteristicilor cheie | ProHoster","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Nota traduc\u0103torului.<\/b>: Articolul a fost scris de Scott Lowe \u2014 un inginer cu mult\u0103 experien\u021b\u0103 \u00een IT, autor\/co-autor al \u0219apte c\u0103r\u021bi tip\u0103rite (\u00een principal despre VMware vSphere). Acum lucreaz\u0103 la filiala VMware \u2014 Heptio (achizi\u021bionat\u0103 \u00een 2016), specializ\u00e2ndu-se \u00een cloud computing \u0219i Kubernetes. Textul serve\u0219te drept o introducere concis\u0103 \u0219i u\u0219or de \u00een\u021beles \u00een managementul configura\u021biilor pentru Kubernetes folosind tehnologia <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/\">Kustomize<\/a><\/noindex>, recent integrat\u0103 \u00een K8s.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: revizuirea caracteristicilor cheie | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/099d2281c06d7a294532a816bb6aab21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKustomize este un instrument care permite utilizatorilor \u201es\u0103 personalizeze fi\u0219iere YAML simple \u0219i f\u0103r\u0103 \u0219abloane pentru diferite scopuri, l\u0103s\u00e2nd YAML-ul original intact \u0219i utilizabil\u201d (descriere preluat\u0103 direct din <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\">repository-ul kustomize de pe GitHub<\/a><\/noindex>). Kustomize poate fi rulat direct sau, \u00eencep\u00e2nd cu Kubernetes 1.14, utilizat cu <code>kubectl -k<\/code> pentru a accesa func\u021bionalit\u0103\u021bile sale (de\u0219i la Kubernetes 1.15 un binar separat este mai nou dec\u00e2t func\u021bionalit\u0103\u021bile \u00eencorporate \u00een kubectl). <i>(<b>Nota traduc\u0103torului.<\/b>: Cu lansarea recent\u0103 a <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/467477\/\">Kubernetes 1.16<\/a><\/noindex> kustomize <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/1177\">sus\u021binut\u0103<\/a><\/noindex> \u0219i \u00een utilitarul kubeadm.)<\/i> \u00cen aceast\u0103 publica\u021bie vreau s\u0103 familiarizez cititorii cu no\u021biunile de baz\u0103 ale kustomize.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>\u00cen cea mai simpl\u0103 form\u0103\/aplicare, kustomize este pur \u0219i simplu un set de resurse (fi\u0219iere YAML care definesc obiecte Kubernetes: Deployments, Services etc.) plus o list\u0103 de instruc\u021biuni de modificare care trebuie aplicate acestor resurse. Asem\u0103n\u0103tor cu faptul c\u0103 make folose\u0219te un set de instruc\u021biuni din <code>Makefile<\/code>, iar Docker construie\u0219te un container pe baza instruc\u021biunilor din <code>Dockerfile<\/code>, kustomize folose\u0219te <code>kustomization.yaml<\/code> pentru a stoca prescrip\u021biile despre ce modific\u0103ri dore\u0219te utilizatorul s\u0103 fac\u0103 \u00een setul de resurse.<\/p>\n<p>Iat\u0103 un exemplu de fi\u0219ier <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>\nNu voi \u00eencerca s\u0103 explic toate c\u00e2mpurile posibile din fi\u0219ier <code>kustomization.yaml<\/code> (despre acest lucru s-a scris destul de bine <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/fields.md\">aici<\/a><\/noindex>), dar voi oferi o scurt\u0103 explica\u021bie a unui exemplu specific:<\/p>\n<ul>\n<li> C\u00e2mp <code>resources<\/code> indic\u0103 ce (resurse) va modifica kustomize. \u00cen acest caz, va c\u0103uta resurse \u00een fi\u0219ierele <code>deployment.yaml<\/code> \u0219i <code>service.yaml<\/code> din directorul s\u0103u (dac\u0103 este necesar, se pot specifica c\u0103i absolute sau relative).<\/li>\n<li> C\u00e2mp <code>namePrefix<\/code> cereaz\u0103 un prefix specific pentru kustomize (\u00een acest caz \u2014 <code>dev-<\/code>) la atributul <code>name<\/code> al tuturor resurselor definite \u00een c\u00e2mpul <code>resources<\/code>. Astfel, dac\u0103 \u00een Deployment exist\u0103 <code>name<\/code> cu valoarea <code>nginx-deployment<\/code>, kustomize \u00eel va transforma \u00een <code>dev-nginx-deployment<\/code>.<\/li>\n<li> C\u00e2mp <code>namespace<\/code> cereaz\u0103 kustomize s\u0103 adauge un anumit spa\u021biu de nume pentru toate resursele. \u00cen acest caz, Deployment \u0219i Service vor fi incluse \u00een spa\u021biul de nume <code>dezvoltare<\/code>.<\/li>\n<li> \u00cen cele din urm\u0103, c\u00e2mpul <code>commonLabels<\/code> con\u021bine un set de etichete care va fi ad\u0103ugat tuturor resurselor. \u00cen exemplul nostru, kustomize va atribui resurselor o etichet\u0103 cu numele <code>environment<\/code> \u0219i valoarea <code>dezvoltare<\/code>.<\/li>\n<\/ul>\n<p>\nDac\u0103 utilizatorul va executa <code>kustomize build .<\/code> \u00een directorul cu fi\u0219ierul <code>kustomization.yaml<\/code> \u0219i resursele necesare (adic\u0103 fi\u0219ierele <code>deployment.yaml<\/code> \u0219i <code>service.yaml<\/code>), va ob\u021bine un text cu modific\u0103rile specificate \u00een <code>kustomization.yaml<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: revizuirea caracteristicilor cheie | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/f15c7ccb5f200c7e9b5a25142c364cb8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Nota traduc\u0103torului.<\/b>: Ilustra\u021bie din documenta\u021bia proiectului pentru utilizarea \u201esimpl\u0103\u201d a kustomize<\/i><\/p>\n<p>Iesirea poate fi redirec\u021bionat\u0103, dac\u0103 este necesar s\u0103 se \u00eenregistreze modific\u0103rile:<\/p>\n<pre><code class=\"bash\">kustomize build . &gt; custom-config.yaml<\/code><\/pre>\n<p>\nIe\u0219irea este determinat\u0103 (cu acelea\u0219i date de intrare se vor ob\u021bine acelea\u0219i rezultate la ie\u0219ire), prin urmare, nu este necesar s\u0103 se salveze rezultatul \u00eentr-un fi\u0219ier. \u00cen schimb, acesta poate fi transmis direct unei alte comenzi:<\/p>\n<pre><code class=\"bash\">kustomize build . | kubectl apply -f -<\/code><\/pre>\n<p>\nAccesul la func\u021biile kustomize poate fi ob\u021binut \u0219i prin <code>kubectl -k<\/code> (\u00eencep\u00e2nd cu versiunea 1.14 Kubernetes). Cu toate acestea, re\u021bine\u021bi c\u0103 pachetul kustomize separat se actualizeaz\u0103 mai repede dec\u00e2t cel integrat \u00een kubectl (cel pu\u021bin, a\u0219a stau lucrurile cu lansarea Kubernetes 1.15).<\/p>\n<p>Cititorii s-ar putea \u00eentreba: \u201eDe ce sunt necesare toate aceste complic\u0103\u021bii, dac\u0103 se pot edita fi\u0219ierele direct?\u201d. O \u00eentrebare excelent\u0103. \u00cen exemplul nostru chiar <i>poate<\/i> modificarea fi\u0219ierelor <code>deployment.yaml<\/code> \u0219i <code>service.yaml<\/code> direct, dar ce se \u00eent\u00e2mpl\u0103 dac\u0103 acestea sunt un fork al unui alt proiect? Schimbarea direct\u0103 a fi\u0219ierelor \u00eengreuneaz\u0103 (dac\u0103 nu face imposibil) rebase-ul fork-ului, atunci c\u00e2nd se fac modific\u0103ri \u00een surs\u0103\/\u00een original. Utilizarea kustomize permite centralizarea acestor modific\u0103ri \u00eentr-un fi\u0219ier <code>kustomization.yaml<\/code>, l\u0103s\u00e2nd fi\u0219ierele originale intacte \u0219i, astfel, facilit\u00e2nd, dac\u0103 este necesar, rebase-ul fi\u0219ierelor originale.<\/p>\n<p>Avantajele kustomize devin evidente \u00een cazuri de utilizare mai complexe. \u00cen exemplul de mai sus, <code>kustomization.yaml<\/code> \u0219i resursele se afl\u0103 \u00een acela\u0219i director. Cu toate acestea, kustomize suport\u0103 scenarii de utilizare, c\u00e2nd exist\u0103 o configura\u021bie de baz\u0103 \u0219i multiplele sale varia\u021bii, de asemenea cunoscute sub numele de <i>overlays<\/i>. De exemplu, utilizatorul a dorit s\u0103 ia Deployment \u0219i Service pentru nginx, pe care l-am folosit ca exemplu, \u0219i s\u0103 creeze versiuni (sau variante) de development, staging \u0219i production ale acestor fi\u0219iere. Pentru aceasta, utilizatorul va avea nevoie de overlays-urile men\u021bionate mai sus \u0219i, desigur, de resursele de baz\u0103.<\/p>\n<p>Pentru a ilustra ideea de overlays \u0219i resurse de baz\u0103 <i>(resurse de baz\u0103)<\/i>, s\u0103 presupunem c\u0103 directorul are urm\u0103toarea structur\u0103:<\/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>\n\u00cen fi\u0219ierul <code>base\/kustomization.yaml<\/code> utilizatorii prin intermediul c\u00e2mpului <code>resources<\/code> declar\u0103 simplu resursele pe care trebuie s\u0103 le includ\u0103 kustomize.<\/p>\n<p>\u00cen fiecare dintre fi\u0219iere <code>overlays\/{dev,staging,prod}\/kustomization.yaml<\/code> utilizatorii se refer\u0103 la configura\u021bia de baz\u0103 \u00een c\u00e2mpul <code>resources<\/code>, apoi specific\u0103 modific\u0103rile concrete pentru <i>aceast\u0103 mediu<\/i>. De exemplu, fi\u0219ierul <code>overlays\/dev\/kustomization.yaml<\/code> ar putea ar\u0103ta ca exemplul men\u021bionat anterior:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/.. \/base\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\n\u00cen acest caz, fi\u0219ierul <code>overlays\/prod\/kustomization.yaml<\/code> ar putea fi complet diferit:<\/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>\nC\u00e2nd utilizatorul va rula <code>kustomize build .<\/code> \u00een catalogul <code>overlays\/dev<\/code>, kustomize va genera o variant\u0103 de development. Dac\u0103 se lanseaz\u0103 <code>kustomize build .<\/code> \u00een catalogul <code>overlays\/prod<\/code> \u2014 se va ob\u021bine o variant\u0103 de production. \u0218i toate acestea \u2014 f\u0103r\u0103 a face vreo modificare \u00een fi\u0219ierele ini\u021biale <i>(de baz\u0103)<\/i> \u0219i toate acestea \u2014 \u00eentr-un mod declarat \u0219i determinat. Se poate comite configura\u021bia de baz\u0103 \u0219i directoarele overlays direct \u00een sistemul de control al versiunilor, \u0219tiind c\u0103 pe baza acestor fi\u0219iere, oric\u00e2nd, se poate reproduce configura\u021bia dorit\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: revizuirea caracteristicilor cheie | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/959af6422f6ae4c1b8d755e9c5728d38.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Nota traduc\u0103torului.<\/b>: Ilustra\u021bie din documenta\u021bia proiectului privind utilizarea overlays \u00een kustomize<\/i><\/p>\n<p>Kustomize \u0219tie <i>mult<\/i> mai mult dec\u00e2t ceea ce este prezentat \u00een acest articol. Totu\u0219i, sper c\u0103 acesta va servi ca o introducere bun\u0103.<\/p>\n<h2>Resurse suplimentare<\/h2>\n<p>\nExist\u0103 multe articole \u0219i publica\u021bii bune despre kustomize. Iat\u0103 c\u00e2teva pe care le-am g\u0103sit deosebit de utile:<\/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\">Schimbarea configura\u021biei YAML de baz\u0103 pentru medii diferite prod\/test utiliz\u00e2nd Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.stack-labs.com\/code\/kustomize-101\/\">Kustomize \u2014 Calea corect\u0103 de a face templating \u00een Kubernetes<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-kubernetes-objects\/kustomization\/\">Managementul Declara\u021biei Obiectelor Kubernetes folosind Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/testingclouds.wordpress.com\/2018\/07\/20\/844\/\">Personalizarea Graficele Helm din surs\u0103 cu Kustomize<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<i><b>Nota traduc\u0103torului.<\/b>: De asemenea, se poate recomanda blocul de linkuri publicate ca <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/#resources\">Resurse<\/a><\/noindex> pe site-ul utilitarului \u0219i urmate de o colec\u021bie de videoclipuri cu ultimele prezent\u0103ri despre kustomize.<\/i><\/p>\n<p>Dac\u0103 ave\u021bi \u00eentreb\u0103ri sau sugestii pentru \u00eembun\u0103t\u0103\u021birea acestui material, sunt \u00eentotdeauna deschis la feedback. M\u0103 pute\u021bi contacta \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/scott_lowe\">Twitter<\/a><\/noindex> sau pe <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">canalul Slack Kubernetes<\/a><\/noindex>. Bucura\u021bi-v\u0103 de modularea manifestelor dvs. cu ajutorul kustomize!<\/p>\n<h2>P.S. de la traduc\u0103tor<\/h2>\n<p>\nCiti\u021bi \u0219i \u00een blogul nostru:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/462707\/\">Instrumente pentru dezvoltatori de aplica\u021bii, care ruleaz\u0103 \u00een Kubernetes<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445196\/\">Kubernetes 1.14: o privire asupra principalelor nout\u0103\u021bi<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468259\/\">Cele cinci rezultate principale ale Helm Summit 2019 din Amsterdam<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/420437\/\">Introducere practic\u0103 \u00een managerul de pachete pentru Kubernetes - Helm<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Sursa: <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.2.1 - 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\/ro\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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\udd47Introducere scurt\u0103 \u00een Kustomize | ProHoster","description":"Not\u0103 de traducere: Articolul a fost scris de Scott Lowe \u2014 un inginer cu experien\u021b\u0103 vast\u0103 \u00een IT, autor\/co-autor al \u0219apte c\u0103r\u021bi tip\u0103rite (preponderent despre VMware vSphere).","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/38648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=38648"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/38648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/28991"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=38648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=38648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=38648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}