{"id":22669,"date":"2022-06-09T15:17:43","date_gmt":"2022-06-09T13:17:43","guid":{"rendered":"https:\/\/www.websupport.sk\/podpora\/?post_type=ht_kb&p=22669"},"modified":"2022-06-14T14:28:30","modified_gmt":"2022-06-14T12:28:30","slug":"kubernetes-4-node-affinity-resource-requests-a-limits","status":"publish","type":"ht_kb","link":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/","title":{"rendered":"Kubernetes – 4. Node Affinity, Resource Requests a Limits"},"content":{"rendered":"\n

V tretej \u010dasti<\/a> sme si uk\u00e1zali z\u00e1klady textov\u00e9ho konfigura\u010dn\u00e9ho s\u00fabor vo form\u00e1te YAML. Na jednoduch\u00fdch YAML s\u00faboroch sme si uk\u00e1zali, ako spusti\u0165 job a deployment. Ru\u010dne sme teda nasadili pody na pripraven\u00e9 worker nody, pri\u010dom sme dopredu neur\u010dili, ktor\u00e9 pody sa (ne)m\u00f4\u017eu nasadi\u0165 na ur\u010dit\u00e9 nody.<\/p>\n\n\n\n

Chcete si vytvori\u0165 vlastn\u00fd Kubernetes (K8s) klaster? Vysk\u00fa\u0161ajte si ho vo Virtu\u00e1lnom d\u00e1tovom centre<\/a> od Websupportu.<\/p>\n\n\n\n

Tento diel bude o obmedzovan\u00ed nasadenia podov iba na vybran\u00e9 nody. Niekedy je toti\u017e \u017eiaduce, aby sme ist\u00e9 nody neza\u0165a\u017eovali pr\u00edli\u0161, preto\u017ee ve\u013ek\u00e9 za\u0165a\u017eenie by mohlo negat\u00edvne ovplyvni\u0165 r\u00fdchlos\u0165, stabilitu a bezpe\u010dnos\u0165 Kubernetes Clustra ako celku. Budeme tie\u017e obmedzova\u0165 vyu\u017eitie procesora (CPU) a opera\u010dnej pam\u00e4te (RAM), aby sa nestalo, \u017ee cel\u00fd node bude vyu\u017e\u00edva\u0165 nepatri\u010dne ve\u013ea prostriedkov.<\/p>\n\n\n\n

Ma\u017eeme nepotrebn\u00e9 slu\u017eby a nasadenia<\/h2>\n\n\n\n

Pred t\u00fdm, ako budeme pokra\u010dova\u0165, vyma\u017eeme nepotrebn\u00e9 slu\u017eby (services) a nasadenia (deployments), aby sme Kubernetes Cluster zbyto\u010dne neza\u0165azovali. Najsk\u00f4r vyp\u00ed\u0161eme zoznam spusten\u00fdch slu\u017eieb (prv\u00fd riadok) a akt\u00edvnych nasaden\u00ed (druh\u00fd riadok) na VPS master<\/code>:<\/p>\n\n\n\n

kubectl get services<\/code><\/pre>\n\n\n\n
kubectl get deployments<\/code><\/pre>\n\n\n\n
Potom nepotrebn\u00e9 slu\u017eby (prv\u00fd riadok) a nasadenia (druh\u00fd riadok) na VPS master<\/code> zma\u017eeme (tu je nepotrebn\u00e1 slu\u017eba nazvan\u00e1 nginx-service<\/code> a nepotrebn\u00e9 nasadenie nginx-deployment<\/code>):<\/p>\n\n\n\n
kubectl delete service nginx-service<\/code><\/pre>\n\n\n\n
kubectl delete deployment nginx-deployment<\/code><\/pre>\n\n\n\n
Obmedzujeme nasadenie podov na konkr\u00e9tne nody<\/h2>\n\n\n\n
Node Affinity je n\u00e1zov pre s\u00fabor pravidiel ur\u010duj\u00facich podom, na ktor\u00e9 nody sa m\u00f4\u017eu nasadi\u0165. Pravidl\u00e1 ur\u010dujeme vo vz\u0165ahu k \u0161t\u00edtkom (labels) na nodoch. Na nod ozna\u010den\u00fd \u0161t\u00edtkom n\u00e1sledne dok\u00e1\u017eeme nasadi\u0165 iba ur\u010dit\u00e9 pody.<\/p>\n\n\n\n
Existuj\u00fa dva typy Node Affinity v Kubernetes Cluster: requiredDuringSchedulingIgnoredDuringExecution<\/code> a preferredDuringSchedulingIgnoredDuringExecution<\/code>, pri\u010dom v tomto n\u00e1vode budeme pou\u017e\u00edva\u0165 ten prv\u00fd (required…).<\/p>\n\n\n\n
Aby sme mohli worker nodom nastavi\u0165 Node Affinity, mus\u00edme ich ozna\u010di\u0165 \u0161t\u00edtkami. Ozna\u010d\u00edme iba node worker-1<\/code>:<\/p>\n\n\n\n
kubectl label node worker-1 app=test<\/code><\/pre>\n\n\n\n
Over\u00edme, \u017ee sa \u0161t\u00edtok zap\u00edsal:<\/p>\n\n\n\n
kubectl describe node worker-1 | grep Labels<\/code><\/pre>\n\n\n\n
Vytvor\u00edme textov\u00fd konfigura\u010dn\u00fd s\u00fabor vo form\u00e1te YAML s n\u00e1zvom deployment-without-affinity.yaml<\/code> (prv\u00fd riadok), do ktor\u00e9ho zap\u00ed\u0161eme defin\u00edciu nasadenia bez Node Affinity (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/deployment-without-affinity.yaml<\/code><\/pre>\n\n\n\n
apiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: app-without-affinity\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      run: nginx\n  template:\n    metadata:\n      labels:\n        run: nginx\n    spec:\n      containers:\n      - image: nginx\n        imagePullPolicy: Always\n        name: nginx\n<\/code><\/pre>\n\n\n\n
Vlo\u017e\u00edme skop\u00edrovan\u00fd obsah, ulo\u017e\u00edme pomocou kl\u00e1vesovej skratky Ctrl + X<\/code> a n\u00e1sledne stla\u010den\u00edm kl\u00e1vesu y<\/code> a potvrden\u00edm kl\u00e1vesom Enter<\/code>.<\/p>\n\n\n\n
Nasadenie spust\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/deployment-without-affinity.yaml<\/code><\/pre>\n\n\n\n
Takto zist\u00edme (st\u013apec NODE), \u017ee pody s n\u00e1zvom za\u010d\u00ednaj\u00facim na app-without-affinity-<\/code> sa nasadili na oba nody (worker-1<\/code> aj worker-2<\/code>):<\/p>\n\n\n\n
kubectl get pods -o wide<\/code><\/pre>\n\n\n\n
Ak ale potrebujeme v\u0161etky pody nasadi\u0165 iba na nod worker-1<\/code>, mus\u00edme konfigura\u010dn\u00fd s\u00fabor upravi\u0165 (prv\u00fd riadok) s pou\u017eit\u00edm Node Affinity takto (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/deployment-with-affinity.yaml<\/code><\/pre>\n\n\n\n
apiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: app-with-affinity\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      run: nginx\n  template:\n    metadata:\n      labels:\n        run: nginx\n    spec:\n      containers:\n      - image: nginx\n        imagePullPolicy: Always\n        name: nginx\n      affinity:\n        nodeAffinity:\n          requiredDuringSchedulingIgnoredDuringExecution:\n            nodeSelectorTerms:\n            - matchExpressions:\n              - key: app\n                operator: In\n                values:\n                - test\n<\/code><\/pre>\n\n\n\n
Vlo\u017e\u00edme skop\u00edrovan\u00fd obsah, ulo\u017e\u00edme pomocou kl\u00e1vesovej skratky Ctrl + X<\/code> a n\u00e1sledne stla\u010den\u00edm kl\u00e1vesu y<\/code> a potvrden\u00edm kl\u00e1vesom Enter<\/code>.<\/p>\n\n\n\n
Nasadenie spust\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/deployment-with-affinity.yaml<\/code><\/pre>\n\n\n\n
Takto zist\u00edme (st\u013apec NODE), \u017ee pody s n\u00e1zvom za\u010d\u00ednaj\u00facim na app-with-affinity-<\/code> sa nasadili iba na nod worker-1<\/code>:<\/p>\n\n\n\n
kubectl get pods -o wide<\/code><\/pre>\n\n\n\n
Za pomoci odk\u00e1zania na \u0161t\u00edtok app=test<\/code> nodu worker-1<\/code> sme teda pri nasaden\u00ed dosiahli, \u017ee sa pody vytvorili iba na \u0161t\u00edtkom ozna\u010denom node.<\/p>\n\n\n\n
Obmedzujeme spodn\u00fa a horn\u00fa hranicu vyu\u017eitia prostriedkov<\/h2>\n\n\n\n
Na VPS master<\/code> vyma\u017eeme obe nasadenia, ktor\u00e9 sme vy\u0161\u0161ie spustili:<\/p>\n\n\n\n
kubectl delete deployment app-with-affinity<\/code><\/pre>\n\n\n\n
kubectl delete deployment app-without-affinity<\/code><\/pre>\n\n\n\n
Na VPS master nain\u0161talujeme n\u00e1stroj kubernetes-metrics-server:<\/p>\n\n\n\n
sudo apt install git -y<\/code><\/pre>\n\n\n\n
cd ~<\/code><\/pre>\n\n\n\n
git clone https:\/\/github.com\/kodekloudhub\/kubernetes-metrics-server.git<\/code><\/pre>\n\n\n\n
cd ~\/kubernetes-metrics-server\/<\/code><\/pre>\n\n\n\n
kubectl create -f .<\/code><\/pre>\n\n\n\n
V z\u00e1vislosti na r\u00fdchlosti VPS a sie\u0165ov\u00e9ho pripojenia po\u010dk\u00e1me, pok\u00fdm sa nain\u0161talovan\u00fd n\u00e1stroj spust\u00ed a z\u00edska prv\u00e9 \u0161tatistiky od nodov. N\u00e1sledne zad\u00e1me pr\u00edkaz, ktor\u00fdm budeme monitorova\u0165 vy\u0165a\u017eenie procesora (CPU) a opera\u010dnej pam\u00e4te (RAM):<\/p>\n\n\n\n
kubectl top node<\/code><\/pre>\n\n\n\n
Teraz m\u00e1me pripraven\u00e9 v\u0161etko potrebn\u00e9, aby sme mohli aplikova\u0165 spodn\u00fa hranicu vyu\u017eitia CPU a RAM (Resource Requests) a horn\u00fa hranicu vyu\u017eitia CPU a RAM (Resource Limits).<\/p>\n\n\n\n
Vytvor\u00edme textov\u00fd konfigura\u010dn\u00fd s\u00fabor vo form\u00e1te YAML s n\u00e1zvom pod-with-ram.yaml<\/code> (prv\u00fd riadok), do ktor\u00e9ho zap\u00ed\u0161eme defin\u00edciu nasadenia podu s obmedzen\u00edm vyu\u017eitia opera\u010dnej pam\u00e4te RAM (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/pod-with-ram.yaml<\/code><\/pre>\n\n\n\n
apiVersion: v1\nkind: Pod\nmetadata:\n  name: pod-ram\nspec:\n  containers:\n  - name: container-ram\n    image: polinux\/stress\n    resources:\n      limits:\n        memory: \"50Mi\"\n      requests:\n        memory: \"20Mi\"\n    command: [\"stress\"]\n    args: [\"--vm\", \"1\", \"--vm-bytes\", \"30M\", \"--vm-hang\", \"1\"]\n<\/code><\/pre>\n\n\n\n
Vlo\u017e\u00edme skop\u00edrovan\u00fd obsah, ulo\u017e\u00edme pomocou kl\u00e1vesovej skratky Ctrl + X<\/code> a n\u00e1sledne stla\u010den\u00edm kl\u00e1vesu y<\/code> a potvrden\u00edm kl\u00e1vesom Enter<\/code>.<\/p>\n\n\n\n
Nasadenie spust\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/pod-with-ram.yaml<\/code><\/pre>\n\n\n\n
Over\u00edme, \u010di pod s n\u00e1zvom pod-ram<\/code> nezaber\u00e1 menej ako 20 Mi a viac ako 50 Mi opera\u010dnej pam\u00e4te RAM (st\u013apec MEMORY):<\/p>\n\n\n\n
kubectl top pods<\/code><\/pre>\n\n\n\n
Vytvor\u00edme textov\u00fd konfigura\u010dn\u00fd s\u00fabor vo form\u00e1te YAML s n\u00e1zvom pod-with-cpu.yaml<\/code> (prv\u00fd riadok), do ktor\u00e9ho zap\u00ed\u0161eme defin\u00edciu nasadenia podu s obmedzen\u00edm vyu\u017eitia procesora (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/pod-with-cpu.yaml<\/code><\/pre>\n\n\n\n
apiVersion: v1\nkind: Pod\nmetadata:\n  name: pod-cpu\nspec:\n  containers:\n  - name: container-cpu\n    image: vish\/stress\n    resources:\n      limits:\n        cpu: \"1\"\n      requests:\n        cpu: \"0.5\"\n    args:\n    - -cpus\n    - \"2\"<\/code><\/pre>\n\n\n\n
Vlo\u017e\u00edme skop\u00edrovan\u00fd obsah, ulo\u017e\u00edme pomocou kl\u00e1vesovej skratky Ctrl + X<\/code> a n\u00e1sledne stla\u010den\u00edm kl\u00e1vesu y<\/code> a potvrden\u00edm kl\u00e1vesom Enter<\/code>.<\/p>\n\n\n\n
Nasadenie spust\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/pod-with-cpu.yaml<\/code><\/pre>\n\n\n\n
Over\u00edme, \u010di pod s n\u00e1zvom pod-cpu<\/code> nezaber\u00e1 menej ako 0,5 a viac ako 1 procesora (st\u013apec CPU):<\/p>\n\n\n\n
kubectl top pods<\/code><\/pre>\n\n\n\n
Aj ke\u010f sme vo vy\u0161\u0161ie uvedenom konfigura\u010dnom s\u00fabore \u017eiadali 2 CPU (args), limit n\u00e1s nepustil na viac ako 1 CPU (ekvivalent 999m).<\/p>\n\n\n\n
H\u013ead\u00e1te mana\u017eovan\u00fd Kubernetes? Vyu\u017eite slu\u017eby na\u0161ich sk\u00fasen\u00fdch profesion\u00e1lov na cloud native – radi v\u00e1m priprav\u00edme rie\u0161nie na mieru<\/a>.<\/p>\n\n\n\n
Zhrnutie<\/h2>\n\n\n\n
Vo \u0161tvrtom diele sme uk\u00e1zali, ako obmedzi\u0165 nasadenie podov iba na konkr\u00e9tne nody za pomoci \u0161t\u00edtkov (labels), ktor\u00fdmi sme ozna\u010dili po\u017eadovan\u00fd nod. Z\u00edskali sme tak lep\u0161iu kontrolu nad za\u0165a\u017eovan\u00edm jednotliv\u00fdch nodov. Rovnako sme nastavili aj minim\u00e1lne a maxim\u00e1lne vyu\u017eitie procesora (CPU) a opera\u010dnej pam\u00e4te (RAM). Predi\u0161li sme tak pr\u00edpadn\u00e9mu v\u00fdpadku podov, pr\u00edpadne cel\u00e9ho Kubernetes Clustra.<\/p>\n","protected":false},"excerpt":{"rendered":"
V tretej \u010dasti sme si uk\u00e1zali z\u00e1klady textov\u00e9ho konfigura\u010dn\u00e9ho s\u00fabor vo form\u00e1te YAML. Na jednoduch\u00fdch YAML s\u00faboroch sme si uk\u00e1zali, ako spusti\u0165 job a deployment. Ru\u010dne sme teda nasadili pody na pripraven\u00e9 worker nody, pri\u010dom sme dopredu neur\u010dili, ktor\u00e9 pody sa (ne)m\u00f4\u017eu nasadi\u0165 na ur\u010dit\u00e9 nody. Tento diel bude o…<\/p>\n","protected":false},"author":28,"template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[468],"ht-kb-tag":[336,474,396,471,330,339,381,198,192],"class_list":["post-22669","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-kubernetes","ht_kb_tag-cli","ht_kb_tag-cloud-native","ht_kb_tag-kontajnery","ht_kb_tag-kubernetes","ht_kb_tag-linux","ht_kb_tag-open-source","ht_kb_tag-server","ht_kb_tag-ubuntu","ht_kb_tag-vdc"],"yoast_head":"\nKubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/\" \/>\n<meta property=\"og:locale\" content=\"sk_SK\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory\" \/>\n<meta property=\"og:description\" content=\"V tretej \u010dasti sme si uk\u00e1zali z\u00e1klady textov\u00e9ho konfigura\u010dn\u00e9ho s\u00fabor vo form\u00e1te YAML. Na jednoduch\u00fdch YAML s\u00faboroch sme si uk\u00e1zali, ako spusti\u0165 job a deployment. Ru\u010dne sme teda nasadili pody na pripraven\u00e9 worker nody, pri\u010dom sme dopredu neur\u010dili, ktor\u00e9 pody sa (ne)m\u00f4\u017eu nasadi\u0165 na ur\u010dit\u00e9 nody. Tento diel bude o...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/\" \/>\n<meta property=\"og:site_name\" content=\"Websupport centrum podpory\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-14T12:28:30+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Predpokladan\u00fd \u010das \u010d\u00edtania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 min\u00fat\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-4-node-affinity-resource-requests-a-limits\\\/\",\"url\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-4-node-affinity-resource-requests-a-limits\\\/\",\"name\":\"Kubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/#website\"},\"datePublished\":\"2022-06-09T13:17:43+00:00\",\"dateModified\":\"2022-06-14T12:28:30+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-4-node-affinity-resource-requests-a-limits\\\/#breadcrumb\"},\"inLanguage\":\"sk-SK\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-4-node-affinity-resource-requests-a-limits\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-4-node-affinity-resource-requests-a-limits\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kubernetes – 4. Node Affinity, Resource Requests a Limits\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/#website\",\"url\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/\",\"name\":\"Websupport centrum podpory\",\"description\":\"Radi v\u00e1m pom\u00f4\u017eeme s va\u0161im probl\u00e9mom\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"sk-SK\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Kubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/","og_locale":"sk_SK","og_type":"article","og_title":"Kubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory","og_description":"V tretej \u010dasti sme si uk\u00e1zali z\u00e1klady textov\u00e9ho konfigura\u010dn\u00e9ho s\u00fabor vo form\u00e1te YAML. Na jednoduch\u00fdch YAML s\u00faboroch sme si uk\u00e1zali, ako spusti\u0165 job a deployment. Ru\u010dne sme teda nasadili pody na pripraven\u00e9 worker nody, pri\u010dom sme dopredu neur\u010dili, ktor\u00e9 pody sa (ne)m\u00f4\u017eu nasadi\u0165 na ur\u010dit\u00e9 nody. Tento diel bude o...","og_url":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/","og_site_name":"Websupport centrum podpory","article_modified_time":"2022-06-14T12:28:30+00:00","twitter_card":"summary_large_image","twitter_misc":{"Predpokladan\u00fd \u010das \u010d\u00edtania":"6 min\u00fat"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/","url":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/","name":"Kubernetes - 4. Node Affinity, Resource Requests a Limits - Websupport centrum podpory","isPartOf":{"@id":"https:\/\/www.websupport.sk\/podpora\/#website"},"datePublished":"2022-06-09T13:17:43+00:00","dateModified":"2022-06-14T12:28:30+00:00","breadcrumb":{"@id":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/#breadcrumb"},"inLanguage":"sk-SK","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-4-node-affinity-resource-requests-a-limits\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.websupport.sk\/podpora\/"},{"@type":"ListItem","position":2,"name":"Kubernetes – 4. Node Affinity, Resource Requests a Limits"}]},{"@type":"WebSite","@id":"https:\/\/www.websupport.sk\/podpora\/#website","url":"https:\/\/www.websupport.sk\/podpora\/","name":"Websupport centrum podpory","description":"Radi v\u00e1m pom\u00f4\u017eeme s va\u0161im probl\u00e9mom","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.websupport.sk\/podpora\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"sk-SK"}]}},"_links":{"self":[{"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb\/22669","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/users\/28"}],"version-history":[{"count":2,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb\/22669\/revisions"}],"predecessor-version":[{"id":22951,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb\/22669\/revisions\/22951"}],"wp:attachment":[{"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/media?parent=22669"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb-category?post=22669"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb-tag?post=22669"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}