{"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\/da\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","title":{"rendered":"\ud83e\udd47Kubernetes 1.16: oversigt over de vigtigste nyheder | ProHoster","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Bem. overs.<\/b>: Artiklen er skrevet af Scott Lowe \u2013 en ingeni\u00f8r med mange \u00e5rs erfaring inden for IT, som er forfatter\/medforfatter til syv trykte b\u00f8ger (prim\u00e6rt om VMware vSphere). Han arbejder nu i VMware's datterselskab Heptio (opk\u00f8bt i 2016), hvor han specialiserer sig i cloud computing og Kubernetes. Selve teksten fungerer som en kortfattet og letforst\u00e5elig introduktion til konfigurationsstyring for Kubernetes ved hj\u00e6lp af teknologien <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/\">Kustomize<\/a><\/noindex>, som for nylig er blevet en del af K8s.<\/i><\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: oversigt over de vigtigste nyheder | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/099d2281c06d7a294532a816bb6aab21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKustomize er et v\u00e6rkt\u00f8j, der giver brugerne mulighed for at 'tilpasse enkle og skabelonfrie YAML-filer til forskellige form\u00e5l, samtidig med at den originale YAML forbliver u\u00e6ndret og brugbar' (beskrivelsen er taget direkte fra <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\">kustomize-repositoriet p\u00e5 GitHub<\/a><\/noindex>). Kustomize kan k\u00f8res direkte eller, fra Kubernetes 1.14, bruges med <code>kubectl -k<\/code> for at f\u00e5 adgang til dens funktioner (selvom pr. Kubernetes 1.15 er den separate bin\u00e6re fil nyere end de funktioner, der er indbygget i kubectl). <i>(<b>Bem. overs.<\/b>: Og med den nylige udgivelse af <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\">underst\u00f8ttes<\/a><\/noindex> ogs\u00e5 i kubeadm-v\u00e6rkt\u00f8jet.)<\/i> I denne publikation vil jeg introducere l\u00e6serne til grundl\u00e6ggende om kustomize.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>I sin enkleste form\/anvendelse er kustomize blot et s\u00e6t ressourcer (YAML-filer, der definerer Kubernetes-objekter: Deployments, Services osv.) plus en liste over instrukser om de \u00e6ndringer, der skal foretages i disse ressourcer. Ligesom make bruger et s\u00e6t instrukser, der findes i <code>Makefil<\/code>, og Docker bygger en container baseret p\u00e5 instrukser fra <code>Dockerfile<\/code>, bruger kustomize <code>kustomization.yaml<\/code> til at gemme anvisningerne om, hvilke \u00e6ndringer brugeren \u00f8nsker at foretage i s\u00e6t af ressourcer.<\/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 vil ikke fors\u00f8ge at tale om alle de mulige felter 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 give en kort forklaring af et specifikt eksempel:<\/p>\n<ul>\n<li> Felt <code>resources<\/code> angiver, hvilke ressourcer kustomize vil \u00e6ndre. I dette tilf\u00e6lde vil det lede efter ressourcer i filer <code>deployment.yaml<\/code> og <code>service.yaml<\/code> i sin mappe (det er muligt at angive fulde eller relative stier, hvis n\u00f8dvendigt).<\/li>\n<li> Felt <code>namePrefix<\/code> beder kustomize til at tilf\u00f8je et bestemt pr\u00e6fiks (i dette tilf\u00e6lde \u2014 <code>dev-<\/code>) til attributten <code>name<\/code> for alle ressourcer, der er defineret i feltet <code>resources<\/code>. S\u00e5 hvis der er i Deployment, <code>name<\/code> med v\u00e6rdien <code>nginx-deployment<\/code>, vil kustomize g\u00f8re det til <code>dev-nginx-deployment<\/code>.<\/li>\n<li> Felt <code>namespace<\/code> beder kustomize om at tilf\u00f8je det angivne namespaces til alle ressourcer. I dette tilf\u00e6lde vil Deployment og Service komme ind i namespace <code>udvikling<\/code>.<\/li>\n<li> Endelig feltet <code>commonLabels<\/code> indeholder et s\u00e6t labels, der vil blive tilf\u00f8jet til alle ressourcer. I vores eksempel vil kustomize tildele ressourcerne en label med navnet <code>environment<\/code> og v\u00e6rdi <code>udvikling<\/code>.<\/li>\n<\/ul>\n<p>\nHvis brugeren udf\u00f8rer <code>kustomize build .<\/code> i mappen med filen <code>kustomization.yaml<\/code> og de n\u00f8dvendige ressourcer (dvs. filerne <code>deployment.yaml<\/code> og <code>service.yaml<\/code>), vil output v\u00e6re tekst med \u00e6ndringerne angivet i <code>kustomization.yaml<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: oversigt over de vigtigste nyheder | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/f15c7ccb5f200c7e9b5a25142c364cb8.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Bem. overs.<\/b>: Illustration fra projektets dokumentation om \"simpel\" brug af kustomize<\/i><\/p>\n<p>Output kan omdirigeres, hvis det er n\u00f8dvendigt at registrere \u00e6ndringer:<\/p>\n<pre><code class=\"bash\">kustomize build . &gt; custom-config.yaml<\/code><\/pre>\n<p>\nOutput er deterministisk (med de samme inputdata vil man opn\u00e5 de samme outputresultater), s\u00e5 der er ikke behov for at gemme resultatet i en fil. I stedet kan det straks overf\u00f8res til en anden kommando:<\/p>\n<pre><code class=\"bash\">kustomize build . | kubectl apply -f -<\/code><\/pre>\n<p>\nAdgang til kustomize funktioner kan ogs\u00e5 f\u00e5s gennem <code>kubectl -k<\/code> (fra version 1.14 Kubernetes). Men v\u00e6r opm\u00e6rksom p\u00e5, at det separate kustomize-pakke opdateres hurtigere end den, der er integreret i kubectl (i det mindste er det s\u00e5dan, det st\u00e5r til med Kubernetes version 1.15).<\/p>\n<p>L\u00e6sere kan sp\u00f8rge: \"Hvorfor alt dette besv\u00e6r, n\u00e5r man kan redigere filerne direkte?\". Godt sp\u00f8rgsm\u00e5l. I vores eksempel kan man faktisk <i>you can<\/i> modificere filer <code>deployment.yaml<\/code> og <code>service.yaml<\/code> direkte, men hvad hvis de er en fork af et andet projekt? Direkte \u00e6ndring af filer g\u00f8r det besv\u00e6rligt (hvis overhovedet muligt) at rebase fork\u2019en, n\u00e5r der foretages \u00e6ndringer i kilden\/originalen. Brug af kustomize muligg\u00f8r centralisering af disse \u00e6ndringer i filen <code>kustomization.yaml<\/code>, hvilket efterlader de originale filer intakte og dermed letter rebase af de originale filer, n\u00e5r det er n\u00f8dvendigt.<\/p>\n<p>Fordelene ved kustomize bliver tydelige i mere komplekse brugsscenarier. I det ovenfor n\u00e6vnte eksempel <code>kustomization.yaml<\/code> og ressourcerne er i den samme mappe. Men kustomize underst\u00f8tter brugsscenarier, hvor der er en grundl\u00e6ggende konfiguration og mange variationer af den, ogs\u00e5 kendt som <i>den nye kommando<\/i>. For eksempel \u00f8nskede brugeren at tage Deployment og Service for nginx, som jeg brugte som eksempel, og skabe udviklings-, staging- og produktionsversioner (eller variationer) af disse filer. For dette vil han have brug for de f\u00f8rn\u00e6vnte overlays og selve de grundl\u00e6ggende ressourcer.<\/p>\n<p>For at illustrere ideen om overlays og basisressourcer <i>(basisressourcer)<\/i>, lad os antage, at mapperne 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> brugere bruger feltet <code>resources<\/code> til blot at erkl\u00e6re de ressourcer, som kustomize skal inkludere.<\/p>\n<p>I hver af filerne <code>overlays\/{dev,staging,prod}\/kustomization.yaml<\/code> henviser brugere til den grundl\u00e6ggende konfiguration i feltet <code>resources<\/code>, og angiver derefter specifikke \u00e6ndringer for <i>denne milj\u00f8<\/i>. For eksempel kan filen <code>overlays\/dev\/kustomization.yaml<\/code> se ud som eksemplet, der blev givet tidligere:<\/p>\n<pre><code class=\"plaintext\">resources:\n- ..\/..\/\/base\nnamePrefix: dev-\nnamespace: development\ncommonLabels:\n  environment: development<\/code><\/pre>\n<p>\nI mellemtiden kan filen <code>overlays\/prod\/kustomization.yaml<\/code> se helt anderledes ud:<\/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 brugeren k\u00f8rer <code>kustomize build .<\/code> i katalogen <code>overlays\/dev<\/code>, vil kustomize generere en variant til development. Hvis der derimod k\u00f8res <code>kustomize build .<\/code> i katalogen <code>overlays\/prod<\/code> , f\u00e5r man en variant til production. Og alt dette \u2013 uden at \u00e6ndre noget i de oprindelige <i>(basis)<\/i> filer, og alt dette \u2013 p\u00e5 en deklarativ og deterministisk m\u00e5de. Man kan commite den grundl\u00e6ggende konfiguration og overlay-mapper direkte i versionskontrolsystemet, velvidende at den \u00f8nskede konfiguration n\u00e5r som helst kan reproduceres baseret p\u00e5 disse filer.<\/p>\n<p><img decoding=\"async\" alt=\"\ud83e\udd47Kubernetes 1.16: oversigt over de vigtigste nyheder | ProHoster\" src=\"\/wp-content\/uploads\/2019\/10\/959af6422f6ae4c1b8d755e9c5728d38.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i><b>Bem. overs.<\/b>: Illustration fra dokumentationen om brug af overlays i kustomize<\/i><\/p>\n<p>Kustomize kan <i>meget<\/i> mere, end der er beskrevet i denne artikel. Jeg h\u00e5ber dog, det vil v\u00e6re en god introduktion.<\/p>\n<h2>Yderligere ressourcer<\/h2>\n<p>\nDer er mange gode artikler og publikationer om kustomize. Her er nogle, som jeg fandt s\u00e6rligt 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\">Skift basis YAML-konfiguration for forskellige milj\u00f8er prod\/test ved hj\u00e6lp af Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.stack-labs.com\/code\/kustomize-101\/\">Kustomize \u2014 Den rigtige m\u00e5de at lave templating i Kubernetes<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-kubernetes-objects\/kustomization\/\">Deklarativ administration af Kubernetes-objekter ved hj\u00e6lp af Kustomize<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/testingclouds.wordpress.com\/2018\/07\/20\/844\/\">Tilpasning af upstream Helm Charts med Kustomize<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\n<i><b>Bem. overs.<\/b>: Det er ogs\u00e5 v\u00e6rd at n\u00e6vne et link, der er offentliggjort som <noindex><a rel=\"nofollow\" href=\"https:\/\/kustomize.io\/#resources\">Ressourcer<\/a><\/noindex> p\u00e5 v\u00e6rkt\u00f8jets hjemmeside, og den efterf\u00f8lgende samling af videoer med de seneste opl\u00e6g om kustomize.<\/i><\/p>\n<p>Hvis du har sp\u00f8rgsm\u00e5l eller forslag til forbedring af dette materiale, er jeg altid \u00e5ben for feedback. Du kan kontakte mig i <noindex><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/scott_lowe\">Twitter<\/a><\/noindex> eller p\u00e5 <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.slack.com\/\">Kubernetes Slack-kanal<\/a><\/noindex>. Hav det sjovt med at modificere dine manifester ved hj\u00e6lp af kustomize!<\/p>\n<h2>P.S. fra overs\u00e6tteren<\/h2>\n<p>\nL\u00e6s ogs\u00e5 p\u00e5 vores blog:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/462707\/\">V\u00e6rkt\u00f8jer til udviklere af applikationer, der k\u00f8res 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: oversigt over hovednyhederne<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468259\/\">Fem vigtigste konklusioner 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 introduktion til pakken manager 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.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\/da\/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=\"da_DK\" \/>\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\/da\/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 introduktion til Kustomize | ProHoster","description":"Bem\u00e6rk: Artiklen er skrevet af Scott Lowe \u2013 en erfaren IT-ingeni\u00f8r, som er forfatter\/medforfatter til syv trykte b\u00f8ger (prim\u00e6rt om VMware vSphere).","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/kratkoe-vvedenie-v-kustomize","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","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\/da\/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\/da\/wp-json\/wp\/v2\/posts\/38648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=38648"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/38648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/28991"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=38648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=38648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=38648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}