{"id":22750,"date":"2022-06-14T13:02:00","date_gmt":"2022-06-14T11:02:00","guid":{"rendered":"https:\/\/www.websupport.sk\/podpora\/?post_type=ht_kb&p=22750"},"modified":"2022-06-14T14:29:02","modified_gmt":"2022-06-14T12:29:02","slug":"kubernetes-8-siet-ingress-a-egress","status":"publish","type":"ht_kb","link":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/","title":{"rendered":"Kubernetes – 8. Sie\u0165 – Ingress a Egress"},"content":{"rendered":"\n

V predo\u0161lom diele<\/a> sme uk\u00e1zali, ako nasaden\u00fd deployment aktualizova\u0165 bez ak\u00e9hoko\u013evek v\u00fdpadku. Tie\u017e sme demon\u0161trovali, ako sa v pr\u00edpade chyby vr\u00e1ti\u0165 do bodu, kedy v\u0161etko fungovalo spr\u00e1vne – a to bez potreby re\u0161tartovania \u010di vypnutia servera.<\/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

V tomto diele nastav\u00edme pravidl\u00e1, pod\u013ea ktor\u00fdch bud\u00fa medzi sebou pody komunikova\u0165, a tie\u017e ako bud\u00fa komunikova\u0165 s in\u00fdmi sie\u0165ami. V\u0161etko za pomoci \u0161t\u00edtkov (labels) a mo\u017enosti druhu NetworkPolicy. Predstav\u00edme si sp\u00f4sob komunik\u00e1cie typu ingress (smerom do podu) a egress (smerom von z podu).<\/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
Vytv\u00e1rame pod so sie\u0165ovou politikou Ingress<\/h2>\n\n\n\n
Nasad\u00edme pod s n\u00e1zvom hello-web<\/code> so \u0161t\u00edtkom app-destination-pod<\/code> a spust\u00edme slu\u017ebu, na ktorej povol\u00edme prich\u00e1dzaj\u00facu komunik\u00e1ciu cez port 8080:<\/p>\n\n\n\n
kubectl run hello-web --labels app=destination-pod --image=gcr.io\/google-samples\/hello-app:1.0 --port 8080 --expose<\/code><\/pre>\n\n\n\n
Over\u00edme, \u010di sa nasadil pod s n\u00e1zvom hello-web<\/code> a \u010di sa spustila slu\u017eba s n\u00e1zvom hello-web<\/code>:<\/p>\n\n\n\n
kubectl get pod | grep hello-web<\/code><\/pre>\n\n\n\n
kubectl get service | grep hello-web<\/code><\/pre>\n\n\n\n
Nasad\u00edme e\u0161te jeden pod s n\u00e1zvom test-1<\/code> a so \u0161t\u00edtkom app=unknown<\/code>, z ktor\u00e9ho sa pripoj\u00edme na pod s n\u00e1zvom hello-web<\/code>:<\/p>\n\n\n\n
kubectl run -l app=unknown --image=alpine --restart=Never --rm -i -t test-1<\/code><\/pre>\n\n\n\n
Zobraz\u00ed sa pr\u00edkazov\u00fd riadok, v ktorom budeme komunikova\u0165 s podom hello-web<\/code>:<\/p>\n\n\n\n
wget -qO- --timeout=2 http:\/\/hello-web:8080<\/code><\/pre>\n\n\n\n
Komunik\u00e1cia prebehla \u00faspe\u0161ne. M\u00f4\u017eeme ukon\u010di\u0165 pr\u00e1cu s pr\u00edkazov\u00fdm riadkom podu test-1<\/code>:<\/p>\n\n\n\n
exit<\/code><\/pre>\n\n\n\n
Dvakr\u00e1t stla\u010d\u00edme kl\u00e1vesov\u00fa skratku Ctrl + C<\/code> a vyma\u017eeme pod s n\u00e1zvom test-1<\/code>:<\/p>\n\n\n\n
kubectl delete pod test-1<\/code><\/pre>\n\n\n\n
Teraz nasad\u00edme sie\u0165ov\u00fa politiku, pod\u013ea ktorej sa u\u017e nebude da\u0165 pripoji\u0165 na pod s n\u00e1zvom hello-web<\/code> z in\u00e9ho podu, ktor\u00fd nem\u00e1 \u0161t\u00edtok app=destination-pod<\/code>. Vytvor\u00edme s\u00fabor s n\u00e1zvom pod-ingress.yaml<\/code> (prv\u00fd riadok), do ktor\u00e9ho zap\u00ed\u0161eme defin\u00edciu sie\u0165ovej politiky (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/pod-ingress.yaml<\/code><\/pre>\n\n\n\n
kind: NetworkPolicy\napiVersion: networking.k8s.io\/v1\nmetadata:\n  name: destination-pod-allow-from-source-pod\nspec:\n  policyTypes:\n  - Ingress\n  podSelector:\n    matchLabels:\n      app: destination-pod\n  ingress:\n  - from:\n    - podSelector:\n        matchLabels:\n          app: source-pod\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
Sie\u0165ov\u00fa politiku nasad\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/pod-ingress.yaml<\/code><\/pre>\n\n\n\n
Teraz op\u00e4\u0165 spust\u00edme pod, ktor\u00fd nem\u00e1 sie\u0165ovou politikou povolen\u00fd \u0161t\u00edtok (tu app=unknown<\/code>):<\/p>\n\n\n\n
kubectl run -l app=unknown --image=alpine --restart=Never --rm -i -t test-1<\/code><\/pre>\n\n\n\n
Ak teraz op\u00e4\u0165 do pr\u00edkazov\u00e9ho riadku novovytvoren\u00e9ho podu zadam\u00e9 pokus o komunik\u00e1ciu s podom hello-web, komunik\u00e1cia nebude \u00faspe\u0161n\u00e1:<\/p>\n\n\n\n
wget -qO- --timeout=2 http:\/\/hello-web:8080<\/code><\/pre>\n\n\n\n
M\u00f4\u017eeme ukon\u010di\u0165 pr\u00e1cu s pr\u00edkazov\u00fdm riadkom podu test-1<\/code>:<\/p>\n\n\n\n
exit<\/code><\/pre>\n\n\n\n
Dvakr\u00e1t stla\u010d\u00edme kl\u00e1vesov\u00fa skratku Ctrl + C<\/code> a vyma\u017eeme pod s n\u00e1zvom test-1<\/code>:<\/p>\n\n\n\n
kubectl delete pod test-1<\/code><\/pre>\n\n\n\n
Ak v\u0161ak teraz spust\u00edme pod, ktor\u00fd bude ma\u0165 sie\u0165ovou politikou povolen\u00fd \u0161t\u00edtok app=source-pod<\/code>, komunik\u00e1cia u\u017e \u00faspe\u0161n\u00e1 bude:<\/p>\n\n\n\n
kubectl run -l app=source-pod --image=alpine --restart=Never --rm -i -t test-1<\/code><\/pre>\n\n\n\n
Do pr\u00edkazov\u00e9ho riadku zad\u00e1me pokus o pripojenie na pod hello-web a zist\u00edme, \u017ee komunik\u00e1cia bola \u00faspe\u0161n\u00e1:<\/p>\n\n\n\n
wget -qO- --timeout=2 http:\/\/hello-web:8080<\/code><\/pre>\n\n\n\n
M\u00f4\u017eeme ukon\u010di\u0165 pr\u00e1cu s pr\u00edkazov\u00fdm riadkom podu test-1<\/code>:<\/p>\n\n\n\n
exit<\/code><\/pre>\n\n\n\n
Dvakr\u00e1t stla\u010d\u00edme kl\u00e1vesov\u00fa skratku Ctrl + C<\/code> a vyma\u017eeme pod s n\u00e1zvom test-1<\/code>:<\/p>\n\n\n\n
kubectl delete pod test-1<\/code><\/pre>\n\n\n\n
Z\u00e1rove\u0148 vyma\u017eeme sie\u0165ov\u00fa politiku Ingress:<\/p>\n\n\n\n
kubectl delete networkpolicy destination-pod-allow-from-source-pod<\/code><\/pre>\n\n\n\n
Vytv\u00e1rame pod so sie\u0165ovou politikou Egress<\/h2>\n\n\n\n
Nasad\u00edme pod s n\u00e1zvom hello-web<\/code> so \u0161t\u00edtkom app-destination-pod<\/code> a spust\u00edme slu\u017ebu, na ktorej povol\u00edme prich\u00e1dzaj\u00facu komunik\u00e1ciu cez port 8080<\/code>:<\/p>\n\n\n\n
kubectl run hello-web-2 --labels app=hello-2 --image=gcr.io\/google-samples\/hello-app:1.0 --port 8080 --expose<\/code><\/pre>\n\n\n\n
Over\u00edme, \u010di sa nasadil pod s n\u00e1zvom hello-web-2<\/code> a \u010di sa spustila slu\u017eba s n\u00e1zvom hello-web-2<\/code>:<\/p>\n\n\n\n
kubectl get pod | grep hello-web-2<\/code><\/pre>\n\n\n\n
kubectl get service | grep hello-web-2<\/code><\/pre>\n\n\n\n
Nasad\u00edme e\u0161te jeden pod s n\u00e1zvom test-2<\/code> a so \u0161t\u00edtkom app=source-pod<\/code>, z ktor\u00e9ho sa pripoj\u00edme na pod s n\u00e1zvom hello-web-2<\/code>:<\/p>\n\n\n\n
kubectl run -l app=source-pod --image=alpine --restart=Never --rm -i -t test-2<\/code><\/pre>\n\n\n\n
Zobraz\u00ed sa pr\u00edkazov\u00fd riadok, v ktorom budeme komunikova\u0165 s podom hello-web-2<\/code>:<\/p>\n\n\n\n
wget -qO- --timeout=2 http:\/\/hello-web-2:8080<\/code><\/pre>\n\n\n\n
Komunik\u00e1cia prebehla \u00faspe\u0161ne. M\u00f4\u017eeme ukon\u010di\u0165 pr\u00e1cu s pr\u00edkazov\u00fdm riadkom podu test-2<\/code>:<\/p>\n\n\n\n
exit<\/code><\/pre>\n\n\n\n
Dvakr\u00e1t stla\u010d\u00edme kl\u00e1vesov\u00fa skratku Ctrl + C<\/code> a vyma\u017eeme pod s n\u00e1zvom test-2<\/code>:<\/p>\n\n\n\n
kubectl delete pod test-2<\/code><\/pre>\n\n\n\n
Teraz nasad\u00edme sie\u0165ov\u00fa politiku, pod\u013ea ktorej sa u\u017e nebude da\u0165 pripoji\u0165 na pod s n\u00e1zvom hello-web-2<\/code> z in\u00e9ho podu, ktor\u00fd nem\u00e1 \u0161t\u00edtok app=source-pod<\/code>. Vytvor\u00edme s\u00fabor s n\u00e1zvom pod-egress.yaml<\/code> (prv\u00fd riadok), do ktor\u00e9ho zap\u00ed\u0161eme defin\u00edciu sie\u0165ovej politiky (ostatn\u00e9 riadky):<\/p>\n\n\n\n
nano ~\/pod-egress.yaml<\/code><\/pre>\n\n\n\n
kind: NetworkPolicy\napiVersion: networking.k8s.io\/v1\nmetadata:\n  name: source-pod-allow-to-destination-pod\nspec:\n  policyTypes:\n  - Egress\n  podSelector:\n    matchLabels:\n      app: source-pod\n  egress:\n  - to:\n    - podSelector:\n        matchLabels:\n          app: destination-pod\n  - ports:\n    - port: 53\n      protocol: TCP\n    - port: 53\n      protocol: UDP<\/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
Sie\u0165ov\u00fa politiku nasad\u00edme z vy\u0161\u0161ie vytvoren\u00e9ho konfigura\u010dn\u00e9ho s\u00faboru:<\/p>\n\n\n\n
kubectl create -f ~\/pod-egress.yaml<\/code><\/pre>\n\n\n\n
Teraz vytvor\u00edme pod s n\u00e1zvom test-3<\/code> a so \u0161t\u00edtkom app=source-pod<\/code> (prv\u00fd riadok), z ktor\u00e9ho sa pok\u00fasime spoji\u0165 s podom hello-web-2<\/code> (druh\u00fd riadok):<\/p>\n\n\n\n
kubectl run -l app=source-pod --image=alpine --restart=Never --rm -i -t test-3<\/code><\/pre>\n\n\n\n
wget -qO- --timeout=2 http:\/\/hello-web-2:8080<\/code><\/pre>\n\n\n\n
Komunik\u00e1cia v tomto pr\u00edpade prebehla ne\u00faspe\u0161ne, preto\u017ee pod hello-web-2<\/code> pod\u013ea sietovej politiky egress nem\u00f4\u017ee by\u0165 kontaktovan\u00fd nodom, ktor\u00fd nem\u00e1 \u0161t\u00edtok app=destination-pod<\/code>.<\/p>\n\n\n\n
M\u00f4\u017eeme ukon\u010di\u0165 pr\u00e1cu s pr\u00edkazov\u00fdm riadkom podu test-3<\/code>:<\/p>\n\n\n\n
exit<\/code><\/pre>\n\n\n\n
Dvakr\u00e1t stla\u010d\u00edme kl\u00e1vesov\u00fa skratku Ctrl + C<\/code> a vyma\u017eeme pod s n\u00e1zvom test-3<\/code>:<\/p>\n\n\n\n
kubectl delete pod test-3<\/code><\/pre>\n\n\n\n
Z\u00e1rove\u0148 vyma\u017eeme sie\u0165ov\u00fa politiku Ingress:<\/p>\n\n\n\n
kubectl delete networkpolicy source-pod-allow-to-destination-pod<\/code><\/pre>\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
V tomto diele sme nastavili pravidl\u00e1, pod\u013ea ktor\u00fdch bud\u00fa medzi sebou pody komunikova\u0165, a tie\u017e ako bud\u00fa komunikova\u0165 s in\u00fdmi sie\u0165ami. V\u0161etko za pomoci \u0161t\u00edtkov (labels) a mo\u017enosti druhu NetworkPolicy – konkr\u00e9tne sp\u00f4sob komunik\u00e1cie typu ingress (smerom do podu) a egress (smerom von z podu).<\/p>\n","protected":false},"excerpt":{"rendered":"
V predo\u0161lom diele sme uk\u00e1zali, ako nasaden\u00fd deployment aktualizova\u0165 bez ak\u00e9hoko\u013evek v\u00fdpadku. Tie\u017e sme demon\u0161trovali, ako sa v pr\u00edpade chyby vr\u00e1ti\u0165 do bodu, kedy v\u0161etko fungovalo spr\u00e1vne – a to bez potreby re\u0161tartovania \u010di vypnutia servera. V tomto diele nastav\u00edme pravidl\u00e1, pod\u013ea ktor\u00fdch bud\u00fa medzi sebou pody komunikova\u0165, a tie\u017e…<\/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-22750","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 - 8. Sie\u0165 - Ingress a Egress - 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-8-siet-ingress-a-egress\/\" \/>\n<meta property=\"og:locale\" content=\"sk_SK\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kubernetes - 8. Sie\u0165 - Ingress a Egress - Websupport centrum podpory\" \/>\n<meta property=\"og:description\" content=\"V predo\u0161lom diele sme uk\u00e1zali, ako nasaden\u00fd deployment aktualizova\u0165 bez ak\u00e9hoko\u013evek v\u00fdpadku. Tie\u017e sme demon\u0161trovali, ako sa v pr\u00edpade chyby vr\u00e1ti\u0165 do bodu, kedy v\u0161etko fungovalo spr\u00e1vne – a to bez potreby re\u0161tartovania \u010di vypnutia servera. V tomto diele nastav\u00edme pravidl\u00e1, pod\u013ea ktor\u00fdch bud\u00fa medzi sebou pody komunikova\u0165, a tie\u017e...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/\" \/>\n<meta property=\"og:site_name\" content=\"Websupport centrum podpory\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-14T12:29:02+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-8-siet-ingress-a-egress\\\/\",\"url\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-8-siet-ingress-a-egress\\\/\",\"name\":\"Kubernetes - 8. Sie\u0165 - Ingress a Egress - Websupport centrum podpory\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/#website\"},\"datePublished\":\"2022-06-14T11:02:00+00:00\",\"dateModified\":\"2022-06-14T12:29:02+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-8-siet-ingress-a-egress\\\/#breadcrumb\"},\"inLanguage\":\"sk-SK\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-8-siet-ingress-a-egress\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/kb\\\/kubernetes-8-siet-ingress-a-egress\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.websupport.sk\\\/podpora\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kubernetes – 8. Sie\u0165 – Ingress a Egress\"}]},{\"@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 - 8. Sie\u0165 - Ingress a Egress - 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-8-siet-ingress-a-egress\/","og_locale":"sk_SK","og_type":"article","og_title":"Kubernetes - 8. Sie\u0165 - Ingress a Egress - Websupport centrum podpory","og_description":"V predo\u0161lom diele sme uk\u00e1zali, ako nasaden\u00fd deployment aktualizova\u0165 bez ak\u00e9hoko\u013evek v\u00fdpadku. Tie\u017e sme demon\u0161trovali, ako sa v pr\u00edpade chyby vr\u00e1ti\u0165 do bodu, kedy v\u0161etko fungovalo spr\u00e1vne – a to bez potreby re\u0161tartovania \u010di vypnutia servera. V tomto diele nastav\u00edme pravidl\u00e1, pod\u013ea ktor\u00fdch bud\u00fa medzi sebou pody komunikova\u0165, a tie\u017e...","og_url":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/","og_site_name":"Websupport centrum podpory","article_modified_time":"2022-06-14T12:29:02+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-8-siet-ingress-a-egress\/","url":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/","name":"Kubernetes - 8. Sie\u0165 - Ingress a Egress - Websupport centrum podpory","isPartOf":{"@id":"https:\/\/www.websupport.sk\/podpora\/#website"},"datePublished":"2022-06-14T11:02:00+00:00","dateModified":"2022-06-14T12:29:02+00:00","breadcrumb":{"@id":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/#breadcrumb"},"inLanguage":"sk-SK","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.websupport.sk\/podpora\/kb\/kubernetes-8-siet-ingress-a-egress\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.websupport.sk\/podpora\/"},{"@type":"ListItem","position":2,"name":"Kubernetes – 8. Sie\u0165 – Ingress a Egress"}]},{"@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\/22750","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\/22750\/revisions"}],"predecessor-version":[{"id":22963,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb\/22750\/revisions\/22963"}],"wp:attachment":[{"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/media?parent=22750"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb-category?post=22750"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.websupport.sk\/podpora\/wp-json\/wp\/v2\/ht-kb-tag?post=22750"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}