{"id":31173,"date":"2019-10-31T21:39:53","date_gmt":"2019-10-31T18:39:53","guid":{"rendered":"https:\/\/prohoster.info\/blog\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes\/"},"modified":"2019-10-31T21:39:53","modified_gmt":"2019-10-31T18:39:53","slug":"obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes","title":{"rendered":"Az Ingress vez\u00e9rl\u0151k \u00e1ttekint\u00e9se \u00e9s \u00f6sszehasonl\u00edt\u00e1sa a Kuberneteshez","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Az Ingress vez\u00e9rl\u0151k \u00e1ttekint\u00e9se \u00e9s \u00f6sszehasonl\u00edt\u00e1sa a Kuberneteshez\" src=\"\/wp-content\/uploads\/2019\/04\/3e6d3882a8f5a96a257fab4daaa230f2.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA Kubernetes cluster for a specific application should consider the requirements from the application, the business, and the developers. With this information, one can start making architectural decisions, particularly in choosing a specific Ingress controller, of which there are already many available today. To provide a basic overview of the available options without having to study numerous articles\/documentation, we have prepared this review, including the main (production ready) Ingress controllers.<\/p>\n<p>We hope this will assist colleagues in selecting an architectural solution \u2014 at the very least, it will serve as a starting point for obtaining more detailed information and practical experiments. We initially researched similar materials online and, strangely enough, found not a single reasonably complete, let alone structured, review. So let's fill this gap!<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Criteria<\/h2>\n<p>\nTo conduct a comparison and obtain any useful results, one must understand not only the subject area but also have a specific list of criteria that will guide the research focus. Without claiming to analyze all possible use cases for Ingress\/Kubernetes, we have attempted to highlight the most common requirements for controllers \u2014 be prepared that specific details will need to be studied separately.<\/p>\n<p>But I will start with characteristics that have become so common that they are implemented in all solutions and are not discussed:<\/p>\n<ul>\n<li> dynamic service discovery;<\/li>\n<li> SSL termination;<\/li>\n<li> websocket-okkal val\u00f3 munka.<\/li>\n<\/ul>\n<p>\nNow \u2014 on the comparison points:<\/p>\n<h3>Supported protocols<\/h3>\n<p>\nOne of the fundamental criteria for selection. Your software may not operate on standard HTTP or may require functioning with multiple protocols simultaneously. If your case is non-standard, be sure to consider this factor to avoid having to reconfigure the cluster later. The list of supported protocols varies among all controllers.<\/p>\n<h3>Software at its core<\/h3>\n<p>\nT\u00f6bbf\u00e9le alkalmaz\u00e1s l\u00e9tezik, amelyen a vez\u00e9rl\u0151 alapul. A legn\u00e9pszer\u0171bbek k\u00f6z\u00e9 tartozik a nginx, traefik, haproxy, envoy. \u00c1ltal\u00e1ban nem befoly\u00e1solja t\u00fals\u00e1gosan, hogy a forgalmat hogyan fogadj\u00e1k \u00e9s tov\u00e1bb\u00edtj\u00e1k, de mindig hasznos tudni a potenci\u00e1lis finoms\u00e1gokat \u00e9s jellemz\u0151ket, ami a \u201emotorh\u00e1ztet\u0151 alatt\u201d tal\u00e1lhat\u00f3.<\/p>\n<h3>Forgalomir\u00e1ny\u00edt\u00e1s<\/h3>\n<p>\nMilyen alapokon lehet d\u00f6nteni a forgalom ir\u00e1ny\u00edt\u00e1s\u00e1r\u00f3l egy adott szolg\u00e1ltat\u00e1s fel\u00e9? \u00c1ltal\u00e1ban ez a host \u00e9s a path, de vannak tov\u00e1bbi lehet\u0151s\u00e9gek is.<\/p>\n<h3>N\u00e9vt\u00e9r a klaszteren bel\u00fcl<\/h3>\n<p>\nA n\u00e9vt\u00e9r (namespace) a Kubernetes er\u0151forr\u00e1sok logikai feloszt\u00e1s\u00e1nak lehet\u0151s\u00e9ge (p\u00e9ld\u00e1ul stage, production stb.). Vannak Ingress-vez\u00e9rl\u0151k, amelyeket k\u00fcl\u00f6n kell telep\u00edteni minden n\u00e9vt\u00e9rbe (\u00e9s \u00edgy forgalmat ir\u00e1ny\u00edthatnak az adott t\u00e9rbe tartoz\u00f3 podokba). Vannak olyanok is (\u00e9s ezek a t\u00f6bbs\u00e9g), amelyek glob\u00e1lisan m\u0171k\u00f6dnek az eg\u00e9sz klaszterre \u2014 a forgalmat b\u00e1rmely podhoz ir\u00e1ny\u00edtj\u00e1k a klaszteren bel\u00fcl, f\u00fcggetlen\u00fcl a n\u00e9vt\u0151l. <i>a f\u0151 DB p\u00e9ld\u00e1nyhoz<\/i> e t\u00e9r t\u00e9rfogat\u00e1ban). Vannak (\u00e9s ezek nyilv\u00e1nval\u00f3 t\u00f6bbs\u00e9ge), amely glob\u00e1lisan m\u0171k\u00f6dik az eg\u00e9sz klaszterben \u2013 a forgalmat b\u00e1rmely klaszter podj\u00e1ba ir\u00e1ny\u00edtja, f\u00fcggetlen\u00fcl a n\u00e9vt\u00e9rben.<\/p>\n<h3>Pr\u00f3b\u00e1k az upstreamokhoz<\/h3>\n<p>\nHogyan biztos\u00edtj\u00e1k a forgalom ir\u00e1ny\u00edt\u00e1s\u00e1t az eg\u00e9szs\u00e9ges alkalmaz\u00e1s- \u00e9s szolg\u00e1ltat\u00e1smint\u00e1k fel\u00e9? Vannak lehet\u0151s\u00e9gek akt\u00edv \u00e9s passz\u00edv ellen\u0151rz\u00e9sekre, \u00fajrapr\u00f3b\u00e1lkoz\u00e1sokra (retries), \u00e1ramk\u00f6rmegszak\u00edt\u00f3kra. <i>(tov\u00e1bbi inform\u00e1ci\u00f3k\u00e9rt l\u00e1sd p\u00e9ld\u00e1ul a <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/438426\/\">cikket az Istio-r\u00f3l<\/a><\/noindex>)<\/i>, saj\u00e1t \u00e1llapotellen\u0151rz\u00e9si megold\u00e1saikkal (custom health checks) stb. Ez egy nagyon fontos param\u00e9ter, ha magas el\u00e9rhet\u0151s\u00e9gi \u00e9s id\u0151ben t\u00f6rt\u00e9n\u0151 kivezet\u00e9si k\u00f6vetelm\u00e9nyek vannak a hib\u00e1s szolg\u00e1ltat\u00e1sokb\u00f3l.<\/p>\n<h3>Kiegyens\u00falyoz\u00e1si algoritmusok<\/h3>\n<p>\nItt sz\u00e1mos lehet\u0151s\u00e9g van: a hagyom\u00e1nyos m\u00f3dszerekt\u0151l <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Round-robin_DNS\">k\u00f6rforg\u00e1sos<\/a><\/noindex> eg\u00e9szen egzotikusakig, mint p\u00e9ld\u00e1ul <noindex><a rel=\"nofollow\" href=\"http:\/\/www.loadbalancer.org\/blog\/load-balancing-windows-terminal-server-haproxy-and-rdp-cookies\/\">rdp-cookie<\/a><\/noindex>, valamint k\u00fcl\u00f6nb\u00f6z\u0151 lehet\u0151s\u00e9gek, mint p\u00e9ld\u00e1ul <noindex><a rel=\"nofollow\" href=\"https:\/\/access.redhat.com\/solutions\/900933\">sticky sessions<\/a><\/noindex>.<\/p>\n<h3>Hiteles\u00edt\u00e9s<\/h3>\n<p>\nMilyen hiteles\u00edt\u00e9si s\u00e9m\u00e1kat t\u00e1mogat a vez\u00e9rl\u0151? Basic, digest, oauth, external-auth \u2014 gondolom, hogy ezek az opci\u00f3k ismer\u0151sek. Ez egy fontos krit\u00e9rium, ha sok fejleszt\u0151i (\u00e9s\/vagy egyszer\u0171en z\u00e1rt) k\u00f6r m\u0171k\u00f6dik, amelyekhez az Ingress-en kereszt\u00fcl lehet hozz\u00e1f\u00e9rni. <\/p>\n<h3>Forgalomeloszt\u00e1s<\/h3>\n<p>\nT\u00e1mogatja-e a vez\u00e9rl\u0151 az olyan gyakran haszn\u00e1lt forgalomeloszt\u00e1si mechanizmusokat, mint a kan\u00e1riv\u00e1ltoztat\u00e1sok (canary), A\/B-tesztel\u00e9s, forgalom t\u00fck\u00f6rz\u00e9se (mirroring\/shadowing)? Ez val\u00f3ban f\u00e1jdalmas t\u00e9ma az alkalmaz\u00e1sok sz\u00e1m\u00e1ra, amelyek pontos \u00e9s prec\u00edz forgalomkezel\u00e9st ig\u00e9nyelnek a term\u00e9k tesztel\u00e9s\u00e9hez, term\u00e9khib\u00e1k debuggol\u00e1s\u00e1hoz (vagy minim\u00e1lis vesztes\u00e9gek mellett), a forgalom elemz\u00e9s\u00e9hez stb.<\/p>\n<h3>Fizet\u0151s el\u0151fizet\u00e9s<\/h3>\n<p>\nVan-e fizet\u0151s verzi\u00f3 a vez\u00e9rl\u0151b\u0151l, kiterjesztett funkci\u00f3kkal \u00e9s\/vagy technikai t\u00e1mogat\u00e1ssal?<\/p>\n<h3>Grafikus fel\u00fclet (Web UI)<\/h3>\n<p>\nVan-e valamilyen grafikus fel\u00fclet a vez\u00e9rl\u0151 konfigur\u00e1ci\u00f3j\u00e1nak kezel\u00e9s\u00e9re? F\u0151k\u00e9nt a \u201ek\u00f6nnyebb haszn\u00e1lat\u201d \u00e9rdek\u00e9ben \u00e9s\/vagy azok sz\u00e1m\u00e1ra, akik m\u00f3dos\u00edt\u00e1sokat k\u00edv\u00e1nnak v\u00e9grehajtani az Ingress konfigur\u00e1ci\u00f3ban, de k\u00e9nyelmetlen a \u201enyers\u201d sablonokkal dolgozni. Hasznos lehet, ha a fejleszt\u0151k k\u00eds\u00e9rleteket szeretn\u00e9nek v\u00e9gezni a forgalommal.<\/p>\n<h3>JWT-\u00e9rv\u00e9nyes\u00edt\u00e9s<\/h3>\n<p>\nBe\u00e9p\u00edtett JSON web-tokenek ellen\u0151rz\u00e9s\u00e9nek megl\u00e9te a felhaszn\u00e1l\u00f3i alkalmaz\u00e1s hiteles\u00edt\u00e9s\u00e9re \u00e9s \u00e9rv\u00e9nyes\u00edt\u00e9s\u00e9re.<\/p>\n<h3>Konfigur\u00e1ci\u00f3 testreszab\u00e1si lehet\u0151s\u00e9gek<\/h3>\n<p>\nA sablonok b\u0151v\u00edthet\u0151s\u00e9ge abban az \u00e9rtelemben, hogy mechanizmusokat tartalmaz, amelyek lehet\u0151v\u00e9 teszik saj\u00e1t direkt\u00edv\u00e1k, z\u00e1szl\u00f3k stb. hozz\u00e1ad\u00e1s\u00e1t a standard konfigur\u00e1ci\u00f3s sablonokhoz.<\/p>\n<h3>Alapvet\u0151 v\u00e9delmi mechanizmusok a DDoS ellen<\/h3>\n<p>\nEgyszer\u0171 sebess\u00e9gkorl\u00e1toz\u00f3 algoritmusok, vagy bonyolultabb megold\u00e1sok, amelyek a forgalom sz\u0171r\u00e9s\u00e9re szolg\u00e1lnak c\u00edmek, feh\u00e9rlist\u00e1k, orsz\u00e1gok stb. alapj\u00e1n.<\/p>\n<h3>K\u00e9r\u00e9snyomoz\u00e1s<\/h3>\n<p>\nAz Ingressekb\u0151l sz\u00e1rmaz\u00f3 k\u00e9r\u00e9sek megfigyel\u00e9si, nyomon k\u00f6vet\u00e9si \u00e9s hibakeres\u00e9si lehet\u0151s\u00e9gei a konkr\u00e9t szolg\u00e1ltat\u00e1sok\/podokhoz, ide\u00e1lis esetben pedig a szolg\u00e1ltat\u00e1sok\/podok k\u00f6z\u00f6tti kapcsolatokhoz is.<\/p>\n<h3>WAF<\/h3>\n<p>\nT\u00e1mogat\u00e1s <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Web_application_firewall\">alkalmaz\u00e1s t\u0171zfal<\/a><\/noindex>.<\/p>\n<h2>Ingress vez\u00e9rl\u0151k<\/h2>\n<p>\nA vez\u00e9rl\u0151k list\u00e1ja az al\u00e1bbiak alapj\u00e1n k\u00e9sz\u00fclt <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/services-networking\/ingress-controllers\/#additional-controllers\">a Kubernetes hivatalos dokument\u00e1ci\u00f3ja<\/a><\/noindex> \u00e9s <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/spreadsheets\/d\/16bxRgpO1H_Bn-5xVZ1WrR_I-0A-GOI6egmhvqqLMOmg\/edit\">e t\u00e1bl\u00e1zat<\/a><\/noindex>. N\u00e9h\u00e1nyat a specifikuss\u00e1ga vagy kis elterjedts\u00e9ge (korai fejleszt\u00e9si szakasz) miatt kiz\u00e1rtunk a betekint\u00e9sb\u0151l. A fennmarad\u00f3kat al\u00e1bb t\u00e1rgyaljuk. Kezdj\u00fck az \u00e1ltal\u00e1nos megold\u00e1sok le\u00edr\u00e1s\u00e1val, \u00e9s folytatjuk egy \u00f6sszefoglal\u00f3 t\u00e1bl\u00e1zattal.<\/p>\n<h3>Ingress a Kubernetes-t\u0151l<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/ingress-nginx\">github.com\/kubernetes\/ingress-nginx<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>Ez a Kubernetes hivatalos vez\u00e9rl\u0151je, amelyet a k\u00f6z\u00f6ss\u00e9g fejleszt. A nev\u00e9b\u0151l egy\u00e9rtelm\u0171en kider\u00fcl, hogy nginx alap\u00fa, \u00e9s kieg\u00e9sz\u00edtett\u00e9k k\u00fcl\u00f6nb\u00f6z\u0151 Lua b\u0151v\u00edtm\u00e9nyekkel, amelyeket tov\u00e1bbi lehet\u0151s\u00e9gek megval\u00f3s\u00edt\u00e1s\u00e1ra haszn\u00e1lnak. Az nginx n\u00e9pszer\u0171s\u00e9ge \u00e9s a n\u00e9h\u00e1ny minim\u00e1lis m\u00f3dos\u00edt\u00e1s miatt, amikor vez\u00e9rl\u0151k\u00e9nt haszn\u00e1lj\u00e1k, ez a verzi\u00f3 a legk\u00f6nnyebben \u00e9rthet\u0151 \u00e9s konfigur\u00e1lhat\u00f3 k\u00f6z\u00e9pkateg\u00f3ri\u00e1s m\u00e9rn\u00f6k sz\u00e1m\u00e1ra (webes tapasztalattal).<\/p>\n<h3>Ingress az NGINX Inc-t\u0151l<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/nginxinc\/kubernetes-ingress\">github.com\/nginxinc\/kubernetes-ingress<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>Az nginx fejleszt\u0151inek hivatalos term\u00e9ke. Fizet\u0151s verzi\u00f3val rendelkezik, amelyen alapul. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.nginx.com\/products\/nginx\/\">NGINX Plus<\/a><\/noindex>A f\u0151 elk\u00e9pzel\u00e9s a magas stabilit\u00e1s, a folyamatos visszafel\u00e9 kompatibilit\u00e1s, mindenf\u00e9le k\u00fcls\u0151 modul hi\u00e1nya \u00e9s a hivatalos vez\u00e9rl\u0151h\u00f6z k\u00e9pest el\u00e9rt fokozott sebess\u00e9g (amelyet a Lua elhagy\u00e1s\u00e1val \u00e9rtek el). <\/p>\n<p>A ingyenes v\u00e1ltozat jelent\u0151sen korl\u00e1tozott, m\u00e9g a hivatalos vez\u00e9rl\u0151h\u00f6z k\u00e9pest is (a Lua modulok hi\u00e1nya miatt). A fizet\u0151s v\u00e1ltozat ezzel szemben el\u00e9g sz\u00e9lesk\u00f6r\u0171 kieg\u00e9sz\u00edt\u0151 funkci\u00f3kkal rendelkezik: val\u00f3s idej\u0171 metrik\u00e1k, JWT-\u00e9rv\u00e9nyes\u00edt\u00e9s, akt\u00edv \u00e1llapotellen\u0151rz\u00e9sek \u00e9s m\u00e1sok. Fontos el\u0151nye az NGINX Ingress-szel szemben a TCP\/UDP forgalom teljes k\u00f6r\u0171 t\u00e1mogat\u00e1sa (\u00e9s a k\u00f6z\u00f6ss\u00e9gi verzi\u00f3ban is!). H\u00e1tr\u00e1ny \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/nginxinc\/kubernetes-ingress\/issues\/464\">hi\u00e1nya<\/a><\/noindex> a forgalom eloszt\u00e1s\u00e1nak funkci\u00f3inak, ami azonban \"maxim\u00e1lis priorit\u00e1st \u00e9lvez a fejleszt\u0151k sz\u00e1m\u00e1ra\", de id\u0151t ig\u00e9nyel a megval\u00f3s\u00edt\u00e1shoz.<\/p>\n<h3>Kong Ingress<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/Kong\/kubernetes-ingress-controller\">github.com\/Kong\/kubernetes-ingress-controller<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>A Kong Inc. \u00e1ltal kifejlesztett term\u00e9k, k\u00e9t v\u00e1ltozatban: kereskedelmi \u00e9s ingyenes. Az nginx alapjain k\u00e9sz\u00fclt, amelynek lehet\u0151s\u00e9geit sok Lua modul b\u0151v\u00edti.<\/p>\n<p>Eredetileg API-k\u00e9r\u00e9sek feldolgoz\u00e1s\u00e1ra \u00e9s ir\u00e1ny\u00edt\u00e1s\u00e1ra volt orient\u00e1lva, azaz API Gateway-k\u00e9nt m\u0171k\u00f6d\u00f6tt, azonban m\u00e1ra teljes \u00e9rt\u00e9k\u0171 Ingress-vez\u00e9rl\u0151v\u00e9 v\u00e1lt. F\u0151 el\u0151ny\u00f6k: sz\u00e1mos kieg\u00e9sz\u00edt\u0151 modul (t\u00f6bbek k\u00f6z\u00f6tt harmadik f\u00e9lt\u0151l sz\u00e1rmaz\u00f3 fejleszt\u0151k \u00e1ltal is) k\u00f6nnyen telep\u00edthet\u0151 \u00e9s konfigur\u00e1lhat\u00f3, amelyeken kereszt\u00fcl sz\u00e9les spektrum\u00fa kieg\u00e9sz\u00edt\u0151 lehet\u0151s\u00e9gek val\u00f3s\u00edthat\u00f3k meg. Azonban az alapfunkci\u00f3k m\u00e1r sz\u00e1mos lehet\u0151s\u00e9get k\u00edn\u00e1lnak. A munka konfigur\u00e1l\u00e1sa CRD-er\u0151forr\u00e1sok seg\u00edts\u00e9g\u00e9vel t\u00f6rt\u00e9nik.<\/p>\n<p>A term\u00e9k fontos jellemz\u0151je \u2014 egy kont\u00e9ner keretei k\u00f6z\u00f6tt val\u00f3 m\u0171k\u00f6d\u00e9s (a cross-namespaced helyett) vitatott t\u00e9ma: valakinek h\u00e1tr\u00e1nyk\u00e9nt t\u0171nhet (mivel entit\u00e1sok t\u00f6mkeleg\u00e9t kell l\u00e9trehozni minden kont\u00e9nerhez), m\u00edg m\u00e1snak el\u0151nyk\u00e9nt (b<i>\u00f3<\/i>iztos\u00edtva van a nagyobb szint\u0171 elszigetelts\u00e9g, mivel ha egy vez\u00e9rl\u0151 meghib\u00e1sodik, a probl\u00e9ma egyetlen kont\u00e9nerre korl\u00e1toz\u00f3dik).<\/p>\n<h3>Traefik<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/containous\/traefik\">github.com\/containous\/traefik<\/a><\/noindex><\/i><br \/>\n<i>Licenc: MIT<\/i><\/p>\n<p>Olyan proxy, amelyet eredetileg a mikroszolg\u00e1ltat\u00e1sok k\u00e9r\u00e9seinek ir\u00e1ny\u00edt\u00e1s\u00e1ra \u00e9s dinamikus k\u00f6rnyezet\u00fck kezel\u00e9s\u00e9re terveztek. Ennek k\u00f6vetkezt\u00e9ben sz\u00e1mos hasznos funkci\u00f3 \u00e1ll rendelkez\u00e9sre: a konfigur\u00e1ci\u00f3 \u00e1tl\u00e9p\u00e9se \u00fajraind\u00edt\u00e1sok n\u00e9lk\u00fcl, a k\u00fcl\u00f6nf\u00e9le terhel\u00e9seloszt\u00e1si m\u00f3dszerek t\u00e1mogat\u00e1sa, webes fel\u00fclet, metrik\u00e1k \u00e1tad\u00e1sa, k\u00fcl\u00f6nb\u00f6z\u0151 protokollok t\u00e1mogat\u00e1sa, REST API, kan\u00e1ris megjelen\u00e9sek \u00e9s m\u00e9g sok m\u00e1s. A kellemes jellemz\u0151 a dobozb\u00f3l val\u00f3 Let's Encrypt tan\u00fas\u00edtv\u00e1nyok t\u00e1mogat\u00e1sa is. H\u00e1tr\u00e1ny \u2013 a magas rendelkez\u00e9sre \u00e1ll\u00e1s (HA) megszervez\u00e9s\u00e9hez a vez\u00e9rl\u0151nek saj\u00e1t KV-t\u00e1rol\u00f3t kell telep\u00edtenie \u00e9s csatlakoztatnia.<\/p>\n<h3>HAProxy<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jcmoraisjr\/haproxy-ingress\">github.com\/jcmoraisjr\/haproxy-ingress<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>A HAProxy r\u00e9g\u00f3ta ismert proxy \u00e9s forgalomeloszt\u00f3. A Kubernetes klaszter keret\u00e9n bel\u00fcl \u201el\u00e1gy\u201d konfigur\u00e1ci\u00f3friss\u00edt\u00e9st (forgalomvesztes\u00e9g n\u00e9lk\u00fcl) k\u00edn\u00e1l, DNS alap\u00fa szolg\u00e1ltat\u00e1sok felfedez\u00e9s\u00e9t, dinamikus konfigur\u00e1ci\u00f3t API-n kereszt\u00fcl. Vonz\u00f3 lehet a konfigur\u00e1ci\u00f3s sablon teljes testreszabhat\u00f3s\u00e1ga a CM csere r\u00e9v\u00e9n, valamint a Sprig k\u00f6nyvt\u00e1r funkci\u00f3inak alkalmaz\u00e1s\u00e1nak lehet\u0151s\u00e9ge. A megold\u00e1s alapvet\u0151 hangs\u00falya az olyan magas sebess\u00e9g, optimaliz\u00e1lts\u00e1g \u00e9s er\u0151forr\u00e1s-hat\u00e9konys\u00e1g. A vez\u00e9rl\u0151 el\u0151nye \u2013 a rekord sz\u00e1m\u00fa k\u00fcl\u00f6nf\u00e9le terhel\u00e9seloszt\u00e1si m\u00f3d t\u00e1mogat\u00e1sa.<\/p>\n<h3>Voyager<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/appscode\/voyager\">github.com\/appscode\/voyager<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>A HAProxy alap\u00fa vez\u00e9rl\u0151, amelyet univerz\u00e1lis megold\u00e1sk\u00e9nt pozicion\u00e1lnak, sz\u00e9lesk\u00f6r\u0171 lehet\u0151s\u00e9geket t\u00e1mogat sz\u00e1mos szolg\u00e1ltat\u00f3n\u00e1l. Lehet\u0151v\u00e9 teszi a forgalom terhel\u00e9seloszt\u00e1s\u00e1t L7 \u00e9s L4 szinten, m\u00edg a TCP L4 forgalom terhel\u00e9seloszt\u00e1sa egy\u00e9rtelm\u0171en a megold\u00e1s egyik kulcsfontoss\u00e1g\u00fa funkci\u00f3ja.<\/p>\n<h3>Contour<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/heptio\/contour\">github.com\/heptio\/contour<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>Ennek a megold\u00e1snak az alapj\u00e1t nemcsak az Envoy k\u00e9pezi: k\u00f6z\u00f6sen <i>k\u00e9sz\u00edtett\u00e9k<\/i> a n\u00e9pszer\u0171 proxy szerz\u0151ivel. Fontos jellemz\u0151je a forgalom Ingress er\u0151forr\u00e1sainak CRD er\u0151forr\u00e1sokon kereszt\u00fcli kezel\u00e9se. Az olyan szervezetek sz\u00e1m\u00e1ra, ahol t\u00f6bb fejleszt\u0151csapat dolgozik egy klaszteren, ez seg\u00edt maximaliz\u00e1lni a forgalom kezel\u00e9s\u00e9nek biztons\u00e1g\u00e1t a szomsz\u00e9dos kont\u00farokban, \u00e9s megv\u00e9di \u0151ket az Ingress er\u0151forr\u00e1sok m\u00f3dos\u00edt\u00e1s\u00e1b\u00f3l ered\u0151 hib\u00e1kt\u00f3l.<\/p>\n<p>B\u0151v\u00edtett terhel\u00e9seloszt\u00e1si m\u00f3dszerek is el\u00e9rhet\u0151k (k\u00e9rjet\u00fck t\u00fckr\u00f6z\u00e9se, automatikus \u00fajrapr\u00f3b\u00e1lkoz\u00e1s, k\u00e9r\u00e9sek \u00fctemez\u00e9se \u00e9s m\u00e9g sok m\u00e1s), r\u00e9szletes forgalomfigyel\u00e9s \u00e9s hibakezel\u00e9s. Bizonyosok sz\u00e1m\u00e1ra jelent\u0151s h\u00e1tr\u00e1ny lehet a sticky session\u00f6k t\u00e1mogat\u00e1s\u00e1nak hi\u00e1nya (b\u00e1r a munka... <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/heptio\/contour\/issues\/361\">m\u00e1r folyamatban van<\/a><\/noindex>).<\/p>\n<h3>Istio Ingress<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/istio.io\/docs\/tasks\/traffic-management\/ingress\/\">istio.io\/docs\/tasks\/traffic-management\/ingress<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>Egy \u00e1tfog\u00f3 service mesh megold\u00e1s, amely nemcsak mint Ingress vez\u00e9rl\u0151 m\u0171k\u00f6dik a bej\u00f6v\u0151 forgalom ir\u00e1ny\u00edt\u00e1s\u00e1ban, hanem az eg\u00e9sz klaszter keretein bel\u00fcl is kezeli a forgalmat. A h\u00e1tt\u00e9rben, mint sidecar proxy minden szolg\u00e1ltat\u00e1s sz\u00e1m\u00e1ra, az Envoy alkalmaz\u00e1s tal\u00e1lhat\u00f3. Val\u00f3j\u00e1ban egy nagy komb\u00e1jn, amely \"mindent tud\", \u00e9s alapvet\u0151 \u00f6tlete a maxim\u00e1lis kezelhet\u0151s\u00e9g, sk\u00e1l\u00e1zhat\u00f3s\u00e1g, biztons\u00e1g \u00e9s \u00e1tl\u00e1that\u00f3s\u00e1g. Seg\u00edts\u00e9g\u00e9vel finomra tudja hangolni a forgalom ir\u00e1ny\u00edt\u00e1s\u00e1t, a szolg\u00e1ltat\u00e1sok k\u00f6z\u00f6tti hozz\u00e1f\u00e9r\u00e9s enged\u00e9lyez\u00e9s\u00e9t, terhel\u00e9seloszt\u00e1s\u00e1t, figyel\u00e9s\u00e9t, kan\u00e1ris kiad\u00e1sokat \u00e9s m\u00e9g sok m\u00e1st. T\u00f6bb inform\u00e1ci\u00f3t az Isti\u00f3r\u00f3l a \"<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/438426\/\">Vissza a mikroszolg\u00e1ltat\u00e1sokhoz Isti\u00f3val<\/a><\/noindex>\u00bb.<\/p>\n<h3>Ambassador<\/h3>\n<p>\n<i>Weboldal: <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/datawire\/ambassador\">github.com\/datawire\/ambassador<\/a><\/noindex><\/i><br \/>\n<i>Licenc: Apache 2.0<\/i><\/p>\n<p>Egy m\u00e1sik Envoy alap\u00fa megold\u00e1s. Ingyenes \u00e9s kereskedelmi verzi\u00f3k is rendelkez\u00e9sre \u00e1llnak. Olyan megold\u00e1sk\u00e9nt pozicion\u00e1lj\u00e1k, mint a \"teljesen nat\u00edv Kubernetes sz\u00e1m\u00e1ra\", ami megfelel\u0151 el\u0151ny\u00f6ket biztos\u00edt (szoros integr\u00e1ci\u00f3 a K8s klaszter m\u00f3dszereivel \u00e9s entit\u00e1saival).<\/p>\n<h2>\u00d6sszehasonl\u00edt\u00f3 t\u00e1bl\u00e1zat<\/h2>\n<p>\n\u00cdgy a cikk cs\u00facspontja ez az \u00f3ri\u00e1si t\u00e1bl\u00e1zat:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/ss\/wh\/lj\/sswhljo-rjkms7nadtyewqkxrdi.png\"><img decoding=\"async\" alt=\"Az Ingress vez\u00e9rl\u0151k \u00e1ttekint\u00e9se \u00e9s \u00f6sszehasonl\u00edt\u00e1sa a Kuberneteshez\" src=\"\/wp-content\/uploads\/2019\/04\/3a6c552df6b8b7b6a88517046fa7a275.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>Kattinthat\u00f3, hogy lehet\u0151v\u00e9 tegye a r\u00e9szletesebb n\u00e9zetet, \u00e9s el\u00e9rhet\u0151 <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/spreadsheets\/d\/1xjff2AMS6QXSdh8E8ay_uNMoUa2OLIanCallvkDvAy0\/edit#gid=0\">Google Sheets<\/a><\/noindex>.<\/p>\n<h2>\u00d6sszegz\u00e9s<\/h2>\n<p>\nA cikk c\u00e9lja, hogy \u00e1tfog\u00f3bb meg\u00e9rt\u00e9st ny\u00fajtson (b\u00e1r nem teljesk\u00f6r\u0171!) arr\u00f3l, hogy melyik v\u00e1laszt\u00e1st v\u00e1lassza az \u00d6n konkr\u00e9t eset\u00e9ben. Mint \u00e1ltal\u00e1ban, minden vez\u00e9rl\u0151nek megvannak a maga el\u0151nyei \u00e9s h\u00e1tr\u00e1nyai\u2026<\/p>\n<p>A klasszikus Ingress a Kubernetest\u0151l j\u00f3nak sz\u00e1m\u00edt el\u00e9rhet\u0151s\u00e9ge \u00e9s megb\u00edzhat\u00f3s\u00e1ga miatt, \u00e9s el\u00e9g gazdag funkci\u00f3kban \u2014 \u00e1ltal\u00e1ban v\u00e9ve, ez el\u00e9g is szokott lenni. Azonban, ha a stabilit\u00e1ssal, a funkci\u00f3k szintj\u00e9vel \u00e9s a fejleszt\u00e9ssel kapcsolatban magasabb k\u00f6vetelm\u00e9nyek vannak, \u00e9rdemes figyelmet ford\u00edtani az NGINX Plus-szal \u00e9s el\u0151fizet\u00e9ssel rendelkez\u0151 Ingress-re. A Kong sz\u00e1mos pluginnal rendelkezik (\u00e9s \u00edgy a biztos\u00edtott funkci\u00f3kkal), r\u00e1ad\u00e1sul a fizet\u0151s verzi\u00f3ban m\u00e9g t\u00f6bb van bel\u0151l\u00fck. Sz\u00e9lesk\u00f6r\u0171 lehet\u0151s\u00e9geket k\u00edn\u00e1l API Gateway-k\u00e9nt, dinamikus konfigur\u00e1l\u00e1sra CRD-er\u0151forr\u00e1sok alapj\u00e1n, valamint az alap Kubernetes szolg\u00e1ltat\u00e1sok sz\u00e1m\u00e1ra.<\/p>\n<p>Magasabb k\u00f6vetelm\u00e9nyek eset\u00e9n a terhel\u00e9seloszt\u00e1ssal \u00e9s az enged\u00e9lyez\u00e9si m\u00f3dszerekkel kapcsolatban \u00e9rdemes figyelni a Traefik-re \u00e9s a HAProxy-ra. Ezek ny\u00edlt forr\u00e1sk\u00f3d\u00fa projektek, amelyeket \u00e9veken \u00e1t teszteltek, nagyon stabilak \u00e9s akt\u00edvan fejl\u0151dnek. A Contour m\u00e1r p\u00e1r \u00e9ve jelen van, de m\u00e9g mindig fiatalnak t\u0171nik, \u00e9s csak az Envoy-ra \u00e9p\u00fcl\u0151 alapvet\u0151 funkci\u00f3kkal rendelkezik. Ha WAF haszn\u00e1lat\u00e1ra\/v\u00e9delm\u00e9re van sz\u00fcks\u00e9g az alkalmaz\u00e1s el\u0151tt, akkor \u00e9rdemes figyelni a Kubernetes Ingress-re vagy a HAProxy-ra is.<\/p>\n<p>A legfunkci\u00f3gazdagabb term\u00e9kek az Envoy alap\u00fa megold\u00e1sok, k\u00fcl\u00f6n\u00f6sen az Istio. Ez egy \u00e1tfog\u00f3 megold\u00e1sk\u00e9nt jelenik meg, ami \"mindent tud\", ami viszont magasabb bel\u00e9p\u00e9si k\u00fcsz\u00f6b\u00f6t jelent a konfigur\u00e1l\u00e1sra\/ind\u00edt\u00e1sra\/adminisztr\u00e1ci\u00f3ra, mint a t\u00f6bbi megold\u00e1s.<\/p>\n<p>Mi az Ingress-t v\u00e1lasztottuk standard vez\u00e9rl\u0151k\u00e9nt, \u00e9s ez m\u00e9g mindig haszn\u00e1latban van, amely 80-90% -os ig\u00e9nyt el\u00e9g\u00edt ki. El\u00e9g megb\u00edzhat\u00f3, k\u00f6nnyen konfigur\u00e1lhat\u00f3, b\u0151v\u00edthet\u0151. \u00c1ltal\u00e1ban, specifikus k\u00f6vetelm\u00e9nyek hi\u00e1ny\u00e1ban, ez megfelel\u0151 a legt\u00f6bb klaszterhez\/alkalmaz\u00e1shoz. Hasonl\u00f3 univerz\u00e1lis \u00e9s viszonylag egyszer\u0171 term\u00e9kekk\u00e9nt a Traefik-et \u00e9s a HAProxy-t lehet aj\u00e1nlani.<\/p>\n<h2>P.S.<\/h2>\n<p>\nOlvasson tov\u00e1bbi inform\u00e1ci\u00f3kat a blogunkban:<\/p>\n<ul>\n<li> \u201eVissza a mikroszolg\u00e1ltat\u00e1sokhoz az Isti\u00f3val\u201d: <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/438426\/\">1. r\u00e9sz (az alapvet\u0151 funkci\u00f3k bemutat\u00e1sa)<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/440378\/\">m\u00e1sodik r\u00e9sz (\u00fatvonalv\u00e1laszt\u00e1s, forgalomkezel\u00e9s)<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/443668\/\">3. r\u00e9sz (autentik\u00e1ci\u00f3 \u00e9s jogosults\u00e1gkezel\u00e9s)<\/a><\/noindex>;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445596\/\">Kubernetes tippek \u00e9s tr\u00fckk\u00f6k: szem\u00e9lyre szabott hibaoldalak az NGINX Ingress-n\u00e9l<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/427745\/\">Kubernetes tippek \u00e9s tr\u00fckk\u00f6k: hozz\u00e1f\u00e9r\u00e9s a dev k\u00f6rnyezetekhez<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Forr\u00e1s: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/447180\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438 \u0437\u0430\u043f\u0443\u0441\u043a\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u0434\u043b\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043f\u043e\u043d\u0438\u043c\u0430\u0442\u044c, \u043a\u0430\u043a\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u043a \u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u0441\u0443\u0440\u0441\u0443 \u0441\u0430\u043c\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435, \u0431\u0438\u0437\u043d\u0435\u0441 \u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438. \u041f\u0440\u0438 \u043d\u0430\u043b\u0438\u0447\u0438\u0438 \u044d\u0442\u043e\u0439 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0430\u0442\u044c \u043a \u043f\u0440\u0438\u043d\u044f\u0442\u0438\u044e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u043d\u043e\u0433\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0438, \u0432 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438, \u043a \u0432\u044b\u0431\u043e\u0440\u0443 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e Ingress-\u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440\u0430, \u043a\u043e\u0438\u0445 \u043d\u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0434\u0435\u043d\u044c \u0443\u0436\u0435 \u0431\u043e\u043b\u044c\u0448\u043e\u0435 \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e. \u0427\u0442\u043e\u0431\u044b \u0441\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0431\u0430\u0437\u043e\u0432\u043e\u0435 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0431 \u0438\u043c\u0435\u044e\u0449\u0438\u0445\u0441\u044f \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u0430\u0445 \u0431\u0435\u0437 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u0438 \u0438\u0437\u0443\u0447\u0430\u0442\u044c \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23140,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31173","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 \u0437\u0430\u043f\u0443\u0441\u043a\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u0434\u043b\u044f.\" \/>\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\/hu\/blog\/administrirovanie\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"hu_HU\" \/>\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\u041e\u0431\u0437\u043e\u0440 \u0438 \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440\u043e\u0432 Ingress \u0434\u043b\u044f Kubernetes | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438 \u0437\u0430\u043f\u0443\u0441\u043a\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u0434\u043b\u044f.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes\" \/>\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-31T18:39:53+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:39:53+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\udd47\u00c1ttekint\u00e9s \u00e9s \u00f6sszehasonl\u00edt\u00e1s a Kubernetes Ingress vez\u00e9rl\u0151kr\u0151l | ProHoster","description":"A Kubernetes klaszter ind\u00edt\u00e1sakor.","canonical_url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hu_HU","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\u041e\u0431\u0437\u043e\u0440 \u0438 \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u043b\u0435\u0440\u043e\u0432 Ingress \u0434\u043b\u044f Kubernetes | ProHoster","og:description":"\u041f\u0440\u0438 \u0437\u0430\u043f\u0443\u0441\u043a\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 Kubernetes \u0434\u043b\u044f.","og:url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/obzor-i-sravnenie-kontrollerov-ingress-dlya-kubernetes","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-31T18:39:53+00:00","article:modified_time":"2019-10-31T18:39:53+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31173","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-21 04:53:04","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:21:32","updated":"2026-01-21 04:53:04","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/31173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/comments?post=31173"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/31173\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media\/23140"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media?parent=31173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/categories?post=31173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/tags?post=31173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}