{"id":75425,"date":"2020-03-26T07:42:30","date_gmt":"2020-03-26T05:42:30","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes"},"modified":"2020-03-26T07:42:30","modified_gmt":"2020-03-26T05:42:30","slug":"luchshie-10-hitrostej-i-sovetov-po-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","title":{"rendered":"10 truke dhe k\u00ebshilla m\u00eb t\u00eb mira p\u00ebr Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"10
\n
\nN\u00eb internet ka shum\u00eb literatur\u00eb referuese, por ndonj\u00ebher\u00eb k\u00ebshillat m\u00eb t\u00eb vlefshme jan\u00eb ato m\u00eb t\u00eb thjeshta. Ekipi Kubernetes aaS nga Mail.ru<\/a><\/noindex> p\u00ebrktheu nj\u00eb p\u00ebrmbledhje prej dhjet\u00eb trukesh dhe k\u00ebshillash<\/a><\/noindex>, t\u00eb cilat autori i artikullit i grumbulloi pas nj\u00eb viti pune me Kubernetes. K\u00ebshillat nuk jan\u00eb renditur sipas r\u00ebnd\u00ebsis\u00eb, por mendojm\u00eb se \u00e7do kush do t\u00eb gjej\u00eb di\u00e7ka t\u00eb dobishme p\u00ebr vete.
\n<\/a><\/noindex><\/p>\n

Komanda m\u00eb e thjesht\u00eb n\u00eb pun\u00ebn me Kubernetes<\/h2>\n

\nP\u00ebr t\u00eb filluar, ndoshta veprimi m\u00eb i thjesht\u00eb dhe m\u00eb i dobish\u00ebm n\u00eb pun\u00ebn me Kubernetes. Komanda n\u00eb vijim aktivizon autoshkall\u00ebzimin e komandave kubectl<\/code> n\u00eb shell-in bash:<\/p>\n

echo "source <(kubectl completion bash)" >> ~\/.bashrc\n<\/code><\/pre>\n
\nAutoshkall\u00ebzimi kubectl<\/code> do t\u00eb regjistrohet n\u00eb skedarin .bashrc dhe do t\u00eb aktivizohet automatikisht \u00e7do her\u00eb q\u00eb hapet shell-i. Kjo p\u00ebrshpejton hyrjen e komandave dhe parametrave t\u00eb gjat\u00eb, si\u00e7 \u00ebsht\u00eb all-namespaces<\/code>. M\u00eb shum\u00eb n\u00eb ndihm\u00ebs n\u00eb Kubernetes p\u00ebr bash<\/a><\/noindex>.<\/p>\n
Kufizimet e paracaktuara p\u00ebr RAM dhe CPU n\u00eb hap\u00ebsir\u00ebn em\u00ebrore<\/h2>\n
\nN\u00ebse aplikacioni \u00ebsht\u00eb shkruar gabimisht, p\u00ebr shembull, hap nj\u00eb lidhje t\u00eb re me baz\u00ebn e t\u00eb dh\u00ebnave \u00e7do sekond\u00eb, por kurr\u00eb nuk e mbyll at\u00eb, at\u00ebher\u00eb ndodh nj\u00eb rrjedhje kujtese n\u00eb klaster. Dhe n\u00ebse nuk \u00ebsht\u00eb vendosur nj\u00eb kufi p\u00ebr kujtes\u00ebn p\u00ebr aplikacionin gjat\u00eb deploy-it, kjo mund t\u00eb \u00e7oj\u00eb n\u00eb d\u00ebshtimin e nod\u00ebs.<\/p>\n
P\u00ebr t\u00eb parandaluar nj\u00eb gj\u00eb t\u00eb till\u00eb, Kubernetes lejon vendosjen e kufizimeve t\u00eb paracaktuara p\u00ebr \u00e7do hap\u00ebsir\u00eb em\u00ebrore. K\u00ebto shkruhen n\u00eb skedarin yaml p\u00ebr hap\u00ebsir\u00ebn em\u00ebrore specifike. K\u00ebtu \u00ebsht\u00eb nj\u00eb shembull i nj\u00eb skedari t\u00eb till\u00eb:<\/p>\n
apiVersion: v1\nkind: LimitRange\nmetadata:\n  name: mem-limit-range\nspec:\n  limits:\n  - default:\n      memory: 512Mi\n    defaultRequest:\n      memory: 256Mi\n    type: Container\n<\/code><\/pre>\n
\nKrijoni nj\u00eb t\u00eb till\u00eb yaml dhe aplikoni n\u00eb \u00e7do hap\u00ebsir\u00eb em\u00ebrore. P\u00ebr shembull, n\u00eb hap\u00ebsir\u00ebn em\u00ebrore limit-example<\/code>. Tani, p\u00ebr \u00e7do konteiner q\u00eb do t\u00eb shp\u00ebrndahet n\u00eb k\u00ebt\u00eb hap\u00ebsir\u00eb em\u00ebrore, do t\u00eb zbatohet kufiri 512Mi, n\u00ebse p\u00ebr k\u00ebt\u00eb konteiner nuk \u00ebsht\u00eb vendosur nj\u00eb kufi tjet\u00ebr individual.<\/p>\n
Pastrimi i mbeturinave n\u00eb versionet e vjetra t\u00eb Kubernetes<\/h2>\n
\nKubelet p\u00ebrit\u00eb fillon pastrimin e mbeturinave kur var\/lib\/docker<\/i> z\u00eb 90% t\u00eb hap\u00ebsir\u00ebs diskore t\u00eb disponueshme. Kjo \u00ebsht\u00eb e shk\u00eblqyer, megjithat\u00eb, deri n\u00eb versionin 1.7 t\u00eb Kubernetes nuk kishte kufi t\u00eb paracaktuar p\u00ebr numrin e descriptor\u00ebve t\u00eb indekseve inode t\u00eb p\u00ebrdorur (inodet), t\u00eb cilat korrespondonin me numrin e skedareve n\u00eb sistemin e skedar\u00ebve.<\/p>\n
Potencialisht konteneri juaj var\/lib\/docker<\/i> mund t\u00eb p\u00ebrdor\u00eb vet\u00ebm 50% t\u00eb hap\u00ebsir\u00ebs diskore, por n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb inodet mund t\u00eb p\u00ebrfundojn\u00eb, \u00e7ka do t\u00eb shkaktonte probleme n\u00eb funksionimin e pun\u00ebtor\u00ebve.<\/p>\n
N\u00eb versionet e vjetra t\u00eb kubelet midis 1.4 dhe 1.6 do t\u00eb duhet t\u00eb shtoni nj\u00eb flamur t\u00eb till\u00eb:<\/p>\n
--eviction-hard\n=memory.available<100Mi,nodefs.available<10%,nodefs.inodesFree<5%\n<\/code><\/pre>\n
\nN\u00eb versionet 1.7 dhe m\u00eb t\u00eb reja, ky flamur \u00ebsht\u00eb i vendosur si stopim t\u00eb paracaktuar. Megjithat\u00eb, versionet e m\u00ebparshme nuk monitorojn\u00eb kufirin e inod\u00ebve.<\/p>\n
Minikube\u2026 i vog\u00ebl, por i fuqish\u00ebm Kubernetes lokal<\/h2>\n
\nMinikube \u00ebsht\u00eb m\u00ebnyra m\u00eb e thjesht\u00eb p\u00ebr t\u00eb nisur nj\u00eb klaster lokal Kubernetes. Ai niset me nj\u00eb komand\u00eb t\u00eb thjesht\u00eb:<\/p>\n
minikube start\n<\/code><\/pre>\n
\nSi rezultat i ekzekutimit t\u00eb k\u00ebsaj komande, ju keni nj\u00eb klaster t\u00eb v\u00ebrtet\u00eb Kubernetes n\u00eb kompjuterin tuaj.<\/p>\n
\"10
\nBurimi i ilustrimit<\/i><\/a><\/noindex><\/p>\n
Truku \u00ebsht\u00eb se si t\u00eb nd\u00ebrtoni nj\u00eb aplikacion dhe ta nisni at\u00eb lokal n\u00eb k\u00ebt\u00eb klaster. N\u00ebse nuk jepen udh\u00ebzime t\u00eb ve\u00e7anta, imazhi Docker do t\u00eb nd\u00ebrtohet n\u00eb kompjuterin tuaj dhe jo n\u00eb klaster.<\/p>\n
P\u00ebr t\u00eb b\u00ebr\u00eb q\u00eb Docker t\u00eb d\u00ebrgoj\u00eb imazhin n\u00eb klasterin lokal Kubernetes, i jepet komand\u00ebs docker-machine:<\/p>\n
eval $(minikube docker-env)\n<\/code><\/pre>\n
\nTani mund t\u00eb nd\u00ebrtojm\u00eb aplikacione n\u00eb klasterin lokal Kubernetes.<\/p>\n
Mos e ndani aksesin kubectl me \u00e7do kush<\/h2>\n
\nKjo duket e qart\u00eb, por n\u00ebse disa ekipe p\u00ebrdorin nj\u00eb klaster p\u00ebr aplikacionet e tyre (p\u00ebr at\u00eb q\u00eb u krijua Kubernetes), nuk \u00ebsht\u00eb e men\u00e7ur ta jepni aksesin pa zgjidhje. kubectl<\/code>M\u00eb mir\u00eb \u00ebsht\u00eb t\u00eb ndahen ekipet, duke i dh\u00ebn\u00eb secil\u00ebs hap\u00ebsir\u00ebn e saj emri dhe duke kufizuar aksesin me politika RBAC.<\/p>\n
Mund t\u00eb merret me t\u00eb, duke specifikuar p\u00ebr \u00e7do pod t\u00eb drejtat e aksesit, leximit, krijimit, fshirjes dhe operacioneve t\u00eb tjera. Por m\u00eb e r\u00ebnd\u00ebsishmja \u00ebsht\u00eb t\u00eb kufizoni aksesin n\u00eb sekretet, duke e lejuar at\u00eb vet\u00ebm administratoreve. K\u00ebshtu ne do t\u00eb ndajm\u00eb ata q\u00eb mund t\u00eb administrojn\u00eb klasterin dhe ata q\u00eb mund t\u00eb vendosen aty.<\/p>\n
Menaxhoni buxhetet e pod\u00ebve<\/h2>\n
\nSi t\u00eb garanteoni munges\u00ebn e nd\u00ebrprerjeve p\u00ebr aplikacionin n\u00eb klasterin Kubernetes? PodDisruptionBudget dhe p\u00ebrs\u00ebri PodDisruptionBudget.<\/p>\n
Klasteret p\u00ebrdit\u00ebsohen her\u00eb pas here, dhe nyjat zbrazin. Asgj\u00eb nuk q\u00ebndron n\u00eb vend, k\u00ebshtu q\u00eb \u00ebsht\u00eb realiteti. \u00c7do dispersim me m\u00eb shum\u00eb se nj\u00eb instanc\u00eb duhet t\u00eb p\u00ebrfshij\u00eb patjet\u00ebr PDB (PodDisruptionBudget). Ai krijohet n\u00eb nj\u00eb sked\u00eb t\u00eb thjesht\u00eb yaml, e cila aplikohet n\u00eb klaster. Rrethi i mbulimit t\u00eb PDB t\u00eb caktuar p\u00ebrcaktohet nga selektor\u00ebt e etiketave.<\/p>\n
V\u00ebrejtje:<\/strong> Buxheti PDB merr parasysh vet\u00ebm n\u00eb rastin e nj\u00eb shkeljeje t\u00eb rikthyeshme t\u00eb buxhetit (shkelje vullnetar<\/a><\/noindex>). N\u00eb situata si problemet harduerike, PDB nuk do t\u00eb funksionoj\u00eb.<\/p>\n
Shembulli i PDB:<\/strong><\/p>\n
apiVersion: policy\/v1beta1\nkind: PodDisruptionBudget\nmetadata:\n  name: app-a-pdb\nspec:\n  minAvailable: 2\n  selector:\n      matchLabels:\n        app: app-a\n<\/code><\/pre>\n
\nDy parametrat kryesor\u00eb jan\u00eb matchLabels<\/code> dhe minAvailable<\/code>. N\u00eb parametrin e par\u00eb tregohet p\u00ebr cilat aplikacione zbatohet buxheti. P\u00ebr shembull, n\u00ebse kam disa shp\u00ebrndarje me etiketat app: app-a<\/code> dhe app: app-b<\/code>, at\u00ebher\u00eb ky PDB do t\u00eb zbatohet vet\u00ebm p\u00ebr t\u00eb parin.<\/p>\n
Parametri minAvailable<\/code> merr parasysh gjat\u00eb pastrimit t\u00eb nyj\u00ebs. P\u00ebr shembull, n\u00eb shembullin ton\u00eb gjat\u00eb pastrimit eliminohen t\u00eb gjitha instancat app: app-a<\/code>, p\u00ebrve\u00e7 dy.<\/p>\n
Kjo lejon kontrollin e numrit t\u00eb instancave t\u00eb aplikacionit q\u00eb duhet t\u00eb jen\u00eb aktive n\u00eb \u00e7do moment.<\/p>\n
Monitorimi i sh\u00ebndet\u00ebsis\u00eb s\u00eb aplikacionit<\/h2>\n
\nKy monitorim \u00ebsht\u00eb i mundur n\u00eb dy m\u00ebnyra: p\u00ebrmes probe-ve Readiness ose Liveness.<\/p>\n
Prova e par\u00eb (readiness) p\u00ebrcakton gatishm\u00ebrin\u00eb e kontejnerit p\u00ebr t\u00eb pranuar trafik.<\/p>\n
E dyta (liveness) tregon n\u00ebse kontejneri \u00ebsht\u00eb n\u00eb gjendje funksionimi apo duhet t\u00eb riniset.<\/p>\n
Konfigurimet p\u00ebrkat\u00ebse thjesht shtohen n\u00eb yaml p\u00ebr shp\u00ebrndarje. Aty mund t\u00eb specifikoni koh\u00ebt e skadenc\u00ebs, vonesat dhe numrin e provave. M\u00eb shum\u00eb detaje p\u00ebr to mund t\u00eb gjeni n\u00eb dokumentacionin e Kubernetes<\/a><\/noindex>.<\/p>\n
Etiketat kudo<\/h2>\n
\nEtiketat jan\u00eb nj\u00eb nga konceptet themelore n\u00eb Kubernetes. Ato lejojn\u00eb objektet t\u00eb lidhen lirisht me nj\u00ebra-tjetr\u00ebn dhe gjithashtu t\u00eb krijojn\u00eb k\u00ebrkesa n\u00eb baz\u00eb t\u00eb etiketeve. N\u00eb Kubernetes, madje mund t\u00eb kaloni te klienti dhe t\u00eb shihni ngjarjet sipas etiketeve t\u00eb caktuara.<\/p>\n
Me etiketat mund t\u00eb b\u00ebni gati gjith\u00e7ka, por nj\u00eb shembull i mir\u00eb do t\u00eb ishte krijimi i disa ambienteve p\u00ebr t\u00eb ekzekutuar programe n\u00eb nj\u00eb klaster t\u00eb vet\u00ebm.<\/p>\n
Supozoni se po p\u00ebrdorni t\u00eb nj\u00ebjtin klaster p\u00ebr dev<\/code> dhe qa<\/code>. Kjo do t\u00eb thot\u00eb se mund t\u00eb keni nj\u00eb aplikacion app-a<\/code>, duke funksionuar n\u00eb t\u00eb dyja mjediset qa<\/code> dhe dev<\/code>. N\u00eb k\u00ebt\u00eb rast, mund t\u00eb drejtohemi ve\u00e7mas p\u00ebr instanc\u00ebn e aplikacionit n\u00eb mjedisin p\u00ebrkat\u00ebs duke specifikuar parametrin p\u00ebrkat\u00ebs mjedis<\/code>. P\u00ebr shembull, app: app-a<\/code> dhe environment: dev<\/code> p\u00ebr nj\u00eb ambient, dhe app: app-a<\/code> dhe environment: qa<\/code> p\u00ebr ambientin e dyt\u00eb.<\/p>\n
Kjo lejon qasjen n\u00eb t\u00eb dyja instancat e aplikacionit, p\u00ebr shembull, p\u00ebr t\u00eb kryer testime nj\u00ebkoh\u00ebsisht.<\/p>\n
Rregulloni gj\u00ebrat<\/h2>\n
\nKubernetes \u00ebsht\u00eb nj\u00eb sistem shum\u00eb i fuqish\u00ebm, por \u00e7do sistem n\u00eb fund t\u00eb fundit \u00ebsht\u00eb n\u00eb gjendje t\u00eb ngec\u00eb n\u00eb nj\u00eb num\u00ebr t\u00eb madh procesesh. Kubelet nxit t\u00eb gjith\u00eb proceset dhe kontrollet e specifikuara nga ju, si dhe t\u00eb tijat.<\/p>\n
Sigurisht, nj\u00eb sh\u00ebrbim n\u00eb l\u00ebnie t\u00eb lir\u00eb nuk e ngadal\u00ebson sistemin, dhe Kubernetes \u00ebsht\u00eb fillimisht i nd\u00ebrtuar p\u00ebr t\u00eb shkall\u00ebzuar. Por n\u00ebse n\u00eb vend t\u00eb nj\u00eb sh\u00ebrbimi shfaqen nj\u00eb milion, kubelet fillon t\u00eb ngjitet.<\/p>\n
N\u00ebse p\u00ebr nj\u00eb arsye e hiqni zhvendosjen (kontejner, imazh, \u00e7far\u00ebdo), thjesht sigurohuni q\u00eb t\u00eb jet\u00eb b\u00ebr\u00eb pastrimi i plot\u00eb.<\/p>\n
Njoftohuni me Go<\/h2>\n
\nK\u00ebshill\u00ebn m\u00eb t\u00eb r\u00ebnd\u00ebsishme e kemi l\u00ebn\u00eb p\u00ebr n\u00eb fund. M\u00ebsoni gjuh\u00ebn e programimit Go.<\/p>\n
Kubernetes \u00ebsht\u00eb zhvilluar n\u00eb Go, t\u00eb gjitha zgjerimet jan\u00eb shkruar n\u00eb Go, dhe p\u00ebr m\u00eb tep\u00ebr, biblioteka zyrtare e klientit client-go mb\u00ebshtetet.<\/p>\n
Ajo mund t\u00eb p\u00ebrdoret p\u00ebr gj\u00ebra t\u00eb ndryshme dhe interesante. P\u00ebr shembull, p\u00ebr t\u00eb zgjeruar sistemin Kubernetes sipas d\u00ebshir\u00ebs suaj. K\u00ebshtu, mund t\u00eb p\u00ebrdorni programe t\u00eb veta p\u00ebr mbledhjen e t\u00eb dh\u00ebnave, zhvendosjen e aplikacioneve ose thjesht pastrimin e kontejner\u00ebve.<\/p>\n
T\u00eb m\u00ebsosh gjuh\u00ebn e programimit Go dhe t\u00eb zot\u00ebrosh client-go mund t\u00eb jet\u00eb k\u00ebshilla m\u00eb e r\u00ebnd\u00ebsishme q\u00eb mund t'u jepet p\u00ebrdoruesve fillestar\u00eb t\u00eb Kubernetes.<\/p>\n
P\u00ebrkthyer me mb\u00ebshtetje nga Mail.ru Cloud Solutions<\/i><\/a><\/noindex><\/p>\n
\u00c7far\u00eb tjet\u00ebr t\u00eb lexoni<\/strong>:<\/p>\n
    \n
  1. Tre nivele auto-skalimi n\u00eb Kubernetes dhe si t'i p\u00ebrdorni ato n\u00eb m\u00ebnyr\u00eb efektive<\/a><\/noindex>.<\/li>\n
  2. Nyjet e pun\u00ebs Kubernetes: shum\u00eb t\u00eb vogla ose pak t\u00eb m\u00ebdha<\/a><\/noindex>?<\/li>\n
  3. 25 mjete t\u00eb dobishme p\u00ebr zhvendosjen dhe menaxhimin e Kubernetes<\/a><\/noindex>.<\/li>\n<\/ol>\n
    Burimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
    \u0412 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435 \u043c\u043d\u043e\u0433\u043e \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u043e\u0439 \u043b\u0438\u0442\u0435\u0440\u0430\u0442\u0443\u0440\u044b, \u043d\u043e \u0438\u043d\u043e\u0433\u0434\u0430 \u0441\u0430\u043c\u044b\u043c\u0438 \u0446\u0435\u043d\u043d\u044b\u043c\u0438 \u0441\u0442\u0430\u043d\u043e\u0432\u044f\u0442\u0441\u044f \u0441\u0430\u043c\u044b\u0435 \u043f\u0440\u043e\u0441\u0442\u044b\u0435 \u0441\u043e\u0432\u0435\u0442\u044b. \u041a\u043e\u043c\u0430\u043d\u0434\u0430 Kubernetes aaS \u043e\u0442 Mail.ru \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u0430 \u043f\u043e\u0434\u0431\u043e\u0440\u043a\u0443 \u0438\u0437 \u0434\u0435\u0441\u044f\u0442\u0438 \u0445\u0438\u0442\u0440\u043e\u0441\u0442\u0435\u0439 \u0438 \u0441\u043e\u0432\u0435\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0432\u0442\u043e\u0440 \u0441\u0442\u0430\u0442\u044c\u0438 \u0441\u043e\u0431\u0440\u0430\u043b\u0430 \u043f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0431\u043e\u0442\u044b \u0441 Kubernetes. \u0421\u043e\u0432\u0435\u0442\u044b \u043d\u0435 \u043e\u0442\u0441\u043e\u0440\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u044b \u043f\u043e \u0432\u0430\u0436\u043d\u043e\u0441\u0442\u0438, \u043d\u043e \u0434\u0443\u043c\u0430\u0435\u043c, \u0447\u0442\u043e \u043a\u0430\u0436\u0434\u044b\u0439 \u043d\u0430\u0439\u0434\u0435\u0442 \u0447\u0442\u043e-\u0442\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u043e\u0435 \u0434\u043b\u044f \u0441\u0435\u0431\u044f. \u0421\u0430\u043c\u0430\u044f \u043f\u0440\u043e\u0441\u0442\u0430\u044f \u043a\u043e\u043c\u0430\u043d\u0434\u0430 \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 Kubernetes […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":75426,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-75425","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd4710 hile dhe k\u00ebshilla m\u00eb t\u00eb mira p\u00ebr Kubernetes | ProHoster","description":"N\u00eb internet ka shum\u00eb literatur\u00eb referuese, por.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\u041b\u0443\u0447\u0448\u0438\u0435 10 \u0445\u0438\u0442\u0440\u043e\u0441\u0442\u0435\u0439 \u0438 \u0441\u043e\u0432\u0435\u0442\u043e\u0432 \u043f\u043e Kubernetes | ProHoster","og:description":"\u0412 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435 \u043c\u043d\u043e\u0433\u043e \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u043e\u0439 \u043b\u0438\u0442\u0435\u0440\u0430\u0442\u0443\u0440\u044b, \u043d\u043e.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-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":"2020-03-26T05:42:30+00:00","article:modified_time":"2020-03-26T05:42:30+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"75425","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:56:30","updated":"2022-10-01 20:34:03","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/75425","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=75425"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/75425\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/75426"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=75425"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=75425"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=75425"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}