{"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\/no\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","title":{"rendered":"Kort introduksjon til Kustomize","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Obs. overs.<\/b>: Artikkelen er skrevet av Scott Lowe \u2013 en ingeni\u00f8r med lang erfaring innen IT, som er forfatter\/medforfatter av syv trykte b\u00f8ker (f\u00f8rst og fremst om VMware vSphere). Han jobber n\u00e5 i datterselskapet til VMware \u2013 Heptio (oppkj\u00f8pt i 2016), og spesialiserer seg p\u00e5 skybasert databehandling og Kubernetes. Selve teksten fungerer som en konsis og lettfattelig innf\u00f8ring i konfigurasjonsadministrasjon for Kubernetes ved hjelp av teknologi <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/\">Kustomize<\/a><\/noindex>, nylig integrert i K8s.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Kort introduksjon til Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/099d2281c06d7a294532a816bb6aab21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKustomize \u2013 er et verkt\u00f8y som lar brukere \u00abtilpasse enkle og malfrie YAML-filer for ulike form\u00e5l, mens original-YAML forblir intakt og brukbart\u00bb (beskrivelsen er direkte hentet fra <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\">kustomize-repositoriet p\u00e5 GitHub<\/a><\/noindex>). Kustomize kan kj\u00f8res direkte eller, fra og med Kubernetes 1.14, bruke <code>kubectl -k<\/code> for \u00e5 f\u00e5 tilgang til funksjonene sine (selv om en egen bin\u00e6rfil fra Kubernetes 1.15 er nyere enn funksjonene innebygd i kubectl). <i>(<b>Obs. overs.<\/b>: Med den nyeste utgivelsen av <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/467477\/\">Kubernetes 1.16<\/a><\/noindex> (forresten, utviklingen hans foreg\u00e5r n\u00e5 i et eget repository), alts\u00e5 for behandling av tillegg YAML-filer fra spesielle kustomiseringsmapper (detaljer om deres bruk finnes i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/1177\">st\u00f8ttes<\/a><\/noindex> ogs\u00e5 i kubeadm-verkt\u00f8yet.)<\/i> I denne publikasjonen \u00f8nsker jeg \u00e5 introdusere leserne for grunnleggende om kustomize.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>I sin enkleste form\/bruk er kustomize bare et sett med ressurser (YAML-filer som definerer Kubernetes-objekter: Deployment, Services osv.) pluss en liste med instruksjoner for endringene som m\u00e5 gj\u00f8res i disse ressursene. P\u00e5 samme m\u00e5te som make bruker et sett med instruksjoner som finnes i <code>Makefile<\/code>, og Docker bygger et container basert p\u00e5 instruksjoner fra <code>Dockerfile<\/code>, bruker kustomize <code>kustomization.yaml<\/code> for \u00e5 lagre foreskriftene om hvilke endringer brukeren \u00f8nsker \u00e5 gj\u00f8re i settet av ressurser.<\/p>\n<p>Her er et eksempel p\u00e5 en fil <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>\nJeg skal ikke pr\u00f8ve \u00e5 fortelle om alle mulige felt i filen <code>kustomization.yaml<\/code> (dette er godt beskrevet <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/fields.md\">her<\/a><\/noindex>), men jeg vil gi en kort forklaring p\u00e5 et spesifikt eksempel:<\/p>\n<ul>\n<li> Felt <code>resources<\/code> angir hvilke (ressurser) kustomize vil endre. I dette tilfellet vil den s\u00f8ke etter ressurser i filene <code>deployment.yaml<\/code> og <code>service.yaml<\/code> i sin mappe (fullstendige eller relative baner kan angis om n\u00f8dvendig).<\/li>\n<li> Felt <code>namePrefix<\/code> instruerer kustomize til \u00e5 legge til et bestemt prefiks (i dette tilfellet \u2014 <code>dev-<\/code>) til attributtet <code>name<\/code> til alle ressursene definert i feltet <code>resources<\/code>. Dermed, hvis det er i Deployment, <code>name<\/code> med verdien <code>nginx-deployment<\/code>, vil kustomize lage <code>dev-nginx-deployment<\/code>.<\/li>\n<li> Felt <code>namespace<\/code> instruerer kustomize til \u00e5 legge til et angitt navnrom til alle ressurser. I dette tilfellet vil Deployment og Service havne i navnerommet <code>utvikling<\/code>.<\/li>\n<li> Endelig, feltet <code>commonLabels<\/code> inneholder et sett med etiketter som vil bli lagt til alle ressursene. I v\u00e5rt eksempel vil kustomize tildele ressursene en etikett med navnet <code>milj\u00f8<\/code> og verdien <code>utvikling<\/code>.<\/li>\n<\/ul>\n<p>\nHvis brukeren kj\u00f8rer <code>kustomize build .<\/code> i katalogen med filen <code>kustomization.yaml<\/code> og n\u00f8dvendige ressurser (dvs. filer <code>deployment.yaml<\/code> og <code>service.yaml<\/code>), vil utdataene bli tekst med endringene spesifisert i <code>kustomization.yaml<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"Kort introduksjon til Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/f15c7ccb5f200c7e9b5a25142c364cb8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Obs. overs.<\/b>: Illustrasjon fra prosjektets dokumentasjon om \u00abenkelt\u00bb bruk av kustomize<\/i><\/p>\n<p>Utdataene kan viderekobles hvis det er n\u00f8dvendig \u00e5 faste endringer:<\/p>\n<pre><code class=\"bash\">kustomize build . &gt; custom-config.yaml<\/code><\/pre>\n<p>\nUtdataene er deterministiske (med samme inngangsdata vil alltid gi de samme utdataene), s\u00e5 det er ikke n\u00f8dvendig \u00e5 lagre resultatet i en fil. I stedet kan det umiddelbart sendes til en annen kommando:<\/p>\n<pre><code class=\"bash\">kustomize build . | kubectl apply -f -<\/code><\/pre>\n<p>\nTilgang til kustomize-funksjoner kan ogs\u00e5 f\u00e5s gjennom <code>kubectl -k<\/code> (fra versjon 1.14 av Kubernetes). Men v\u00e6r oppmerksom p\u00e5 at den separate kustomize-pakken oppdateres raskere enn den som er integrert i kubectl (i det minste er det tilfelle med Kubernetes-utgivelsen 1.15).<\/p>\n<p>Leserne kan sp\u00f8rre: \u00abHvorfor alle disse kompleksitetene, hvis man kan redigere filene direkte?\u00bb. Flott sp\u00f8rsm\u00e5l. I v\u00e5rt eksempel kan man faktisk <i>i<\/i> endre filene <code>deployment.yaml<\/code> og <code>service.yaml<\/code> direkte, men hva hvis de er en fork av et prosjekt? \u00c5 endre filene direkte kompliserer (om ikke gj\u00f8r det umulig) rebase av forken n\u00e5r det blir gjort endringer i kilden. \u00c5 bruke kustomize gj\u00f8r at man kan sentralisere disse endringene i filen <code>kustomization.yaml<\/code>, noe som lar de originale filene v\u00e6re uspolerte og dermed gj\u00f8r det lettere \u00e5 rebase de opprinnelige filene om n\u00f8dvendig.<\/p>\n<p>Fordelene med kustomize blir \u00e5penbare i mer komplekse bruksscenarier. I det ovennevnte eksemplet <code>kustomization.yaml<\/code> og ressursene er i samme katalog. Men kustomize st\u00f8tter scenarier der det er en grunnleggende konfigurasjon og mange varianter av den, ogs\u00e5 kjent som <i>kubectl create cronjob<\/i>. For eksempel \u00f8nsket brukeren \u00e5 ta Deployment og Service for nginx, som jeg har brukt som eksempel, og lage utviklings-, staging- og produksjonsversjoner (eller varianter) av disse filene. For dette vil han trenge de nevnte overlayene og de grunnleggende ressursene.<\/p>\n<p>For \u00e5 illustrere ideen om overlays og grunnleggende ressurser <i>(base resources)<\/i>, la oss anta at katalogene har f\u00f8lgende struktur:<\/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>\nI filen <code>base\/kustomization.yaml<\/code> brukere med feltet <code>resources<\/code> enkelt erkl\u00e6rer ressursene som skal inkluderes i kustomize.<\/p>\n<p>I hver av filene <code>overlays\/{dev,staging,prod}\/kustomization.yaml<\/code> brukere refererer til den grunnleggende konfigurasjonen i feltet <code>resources<\/code>, og angir deretter spesifikke endringer for <i>det aktuelle milj\u00f8et<\/i>. For eksempel kan filen <code>overlays\/dev\/kustomization.yaml<\/code> se ut som eksempelet nevnt tidligere:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/base\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nDerfor kan filen <code>overlays\/prod\/kustomization.yaml<\/code> v\u00e6re helt annerledes:<\/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>\nN\u00e5r brukeren kj\u00f8rer <code>kustomize build .<\/code> i katalogen <code>overlays\/dev<\/code>, vil kustomize generere versjonen for utvikling. Hvis man derimot kj\u00f8rer <code>kustomize build .<\/code> i katalogen <code>overlays\/prod<\/code> , vil man f\u00e5 produksjonsversjonen. Og alt dette skjer uten \u00e5 gj\u00f8re noen endringer i de opprinnelige <i>(base)<\/i> filene, og alt blir gjort p\u00e5 en deklarativ og deterministisk m\u00e5te. Man kan kommitte den grunnleggende konfigurasjonen og overleggkatalogene direkte til versjonskontrollsystemet, vel vitende om at man n\u00e5r som helst kan gjenskape den \u00f8nskede konfigurasjonen basert p\u00e5 disse filene.<\/p>\n<p><img decoding=\"async\" alt=\"Kort introduksjon til Kustomize\" src=\"\/wp-content\/uploads\/2019\/10\/959af6422f6ae4c1b8d755e9c5728d38.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Obs. overs.<\/b>: Illustrasjon fra prosjektets dokumentasjon om bruk av overlays i kustomize<\/i><\/p>\n<p>Kustomize kan <i>mye<\/i> mer enn det som er beskrevet i denne artikkelen. Jeg h\u00e5per imidlertid at den vil fungere som en god introduksjon.<\/p>\n<h2>Ytterligere ressurser<\/h2>\n<p>\nDet finnes mange gode artikler og publikasjoner om kustomize. Her er noen som jeg har funnet spesielt nyttige:<\/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\">Endre base YAML-konfigurasjon for forskjellige milj\u00f8er prod\/test ved hjelp av Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.stack-labs.com\/code\/kustomize-101\/\">Kustomize - Den riktige m\u00e5ten \u00e5 gj\u00f8re templating i Kubernetes<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-kubernetes-objects\/kustomization\/\">Deklarativ administrasjon av Kubernetes-objekter ved hjelp av Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/testingclouds.wordpress.com\/2018\/07\/20\/844\/\">Tilpassede upstream Helm-diagrammer med Kustomize<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<i><b>Obs. overs.<\/b>: Det kan ogs\u00e5 anbefales en lenkeblok, publisert som <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/#resources\">Ressurser<\/a><\/noindex> p\u00e5 verkt\u00f8yet sitt nettsted, etterfulgt av en samling videoer med de nyeste innleggene om kustomize.<\/i><\/p>\n<p>Hvis du har sp\u00f8rsm\u00e5l eller forslag til forbedringer av dette materialet, er jeg alltid \u00e5pen for tilbakemeldinger. Du kan kontakte meg i <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/scott_lowe\">Twitter<\/a><\/noindex> eller inn i <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">Kubernetes Slack-kanal<\/a><\/noindex>. Ha det moro med \u00e5 modifisere manifestene dine med kustomize!<\/p>\n<h2>P.S. from the translator<\/h2>\n<p>\nAlso read in our blog:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/462707\/\">Verkt\u00f8y for utviklere av applikasjoner som kj\u00f8rer i Kubernetes<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445196\/\">Kubernetes 1.14: oversikt over hovednyhetene.<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468259\/\">Fem hovedpunkter fra Helm Summit 2019 i Amsterdam<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/420437\/\">Praktisk introduksjon til pakkeh\u00e5ndtereren for Kubernetes \u2014 Helm<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Kilde: <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.5 - 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\/no\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"nn_NO\" \/>\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\/no\/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\udd47Kort introduksjon til Kustomize | ProHoster","description":"Anm. overs.: Artikkelen er skrevet av Scott Lowe \u2014 en erfaren IT-ingeni\u00f8r og forfatter\/medforfatter av syv trykte b\u00f8ker (for det meste om VMware vSphere).","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","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\/no\/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\/no\/wp-json\/wp\/v2\/posts\/38648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=38648"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/38648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/28991"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=38648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=38648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=38648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}