{"id":38112,"date":"2019-10-31T22:21:44","date_gmt":"2019-10-31T19:21:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah\/"},"modified":"2019-10-31T22:21:44","modified_gmt":"2019-10-31T19:21:44","slug":"obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah","title":{"rendered":"Recenzia Kubecost pentru economisirea de fonduri pe Kubernetes \u00een cloud-uri","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Recenzia Kubecost pentru economisirea de fonduri pe Kubernetes \u00een cloud-uri\" src=\"\/wp-content\/uploads\/2019\/09\/410170787ccdee028c1b918561f15ee0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen prezent, tot mai multe companii \u00ee\u0219i mut\u0103 infrastructura de pe servere fizice \u0219i virtuale proprii \u00een clouduri. Aceast\u0103 decizie poate fi explicat\u0103 u\u0219or: nu este necesar s\u0103 te \u00eengrijorezi de hardware, iar clusterul poate fi configurat \u00een numeroase moduri... iar cel mai important \u2014 tehnologia disponibil\u0103 (cum ar fi Kubernetes) permite scalarea u\u0219oar\u0103 a resurselor de calcul \u00een func\u021bie de sarcin\u0103.<\/p>\n<p>Aspectul financiar este \u00eentotdeauna important. Instrumentul despre care vom vorbi \u00een acest articol este destinat s\u0103 ajute la reducerea bugetelor prin utilizarea infrastructurii cloud cu Kubernetes.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Introducere<\/h2>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kubecost.com\/\">Kubecost<\/a><\/noindex> \u2014 o startup din California fondat\u0103 de fo\u0219ti angaja\u021bi Google, care creeaz\u0103 o solu\u021bie pentru calcularea costurilor infrastructurii \u00een servicii cloud (\u00een interiorul clusterului Kubernetes + resurse comune), identificarea punctelor slabe \u00een set\u0103rile clusterului \u0219i trimiterea notific\u0103rilor corespunz\u0103toare \u00een Slack.<\/p>\n<p>Avem clien\u021bi cu Kubernetes \u00een at\u00e2t de obi\u0219nuitele clouduri AWS \u0219i GCP, c\u00e2t \u0219i \u00een Azure, care este mai rar \u00eent\u00e2lnit \u00een comunitatea Linux \u2014 \u00een general, pe toate platformele acceptate de Kubecost. Pentru unii dintre ace\u0219tia, evalu\u0103m costurile pentru serviciile interne ale clusterului autonom (printr-o metod\u0103 similar\u0103 celei folosite de Kubecost) \u0219i, de asemenea, monitoriz\u0103m cheltuielile pentru infrastructur\u0103 \u0219i \u00eencerc\u0103m s\u0103 le optimiz\u0103m. Prin urmare, este logic c\u0103 ne-a interesat posibilitatea de a automatiza aceste sarcini.<\/p>\n<p>Codul surs\u0103 al modulului principal Kubecost este deschis sub licen\u021b\u0103 Open Source (Licen\u021ba Apache 2.0). Poate fi utilizat liber, iar func\u021biile disponibile ar trebui s\u0103 fie suficiente pentru proiecte mici. Totu\u0219i, afacerea este afacere: restul produsului este \u00eenchis \u0219i poate fi accesat prin <noindex><a rel=\"nofollow\" href=\"https:\/\/kubecost.com\/pricing\">abonamente pl\u0103tite<\/a><\/noindex>, care implic\u0103, de asemenea, suport comercial. \u00cen plus, autorii ofer\u0103 o licen\u021b\u0103 gratuit\u0103 pentru clustere mici (1 cluster cu 10 noduri \u2014 la momentul redact\u0103rii acestui articol, acest limit a fost extins la 20 de noduri) sau un period de prob\u0103 cu acces complet timp de 1 lun\u0103.<\/p>\n<h2>Cum este organizat totul<\/h2>\n<p>\nA\u0219adar, partea principal\u0103 a Kubecost este o aplica\u021bie <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubecost\/cost-model\"><b>cost-model<\/b><\/a><\/noindex>, scris\u0103 \u00een Go. Helm chart-ul care descrie \u00eentregul sistem se nume\u0219te <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubecost\/cost-analyzer\"><b>cost-analyzer<\/b><\/a><\/noindex> \u0219i, \u00een esen\u021b\u0103, este o combina\u021bie \u00eentre cost-model, Prometheus, Grafana \u0219i c\u00e2teva tablouri de bord.<\/p>\n<p>\u00cen general, cost-model are o interfa\u021b\u0103 web care afi\u0219eaz\u0103 grafice \u0219i statistici detaliate despre cheltuieli \u00een format tabelar, precum \u0219i, desigur, sfaturi pentru optimizarea costurilor. Dashboard-urile prezentate \u00een Grafana sunt un stadiu mai timpuriu al dezvolt\u0103rii Kubecost \u0219i con\u021bin \u00een mare parte acelea\u0219i date ca \u0219i cost-model, complet\u00e2ndu-le cu statistici obi\u0219nuite despre consumul de CPU\/memorie\/re\u021bea\/spa\u021biu pe disc \u00een cluster \u0219i componentele acestuia.<\/p>\n<p>Cum func\u021bioneaz\u0103 Kubecost?<\/p>\n<ul>\n<li> Cost-model ob\u021bine pre\u021burile de \u00eentre\u021binere prin API-ul providerilor de cloud.<\/li>\n<li> Ulterior, \u00een func\u021bie de tipul de hardware al nodului \u0219i regiune, se calculeaz\u0103 costul pe noduri.<\/li>\n<li> Pe baza costului de func\u021bionare al nodurilor, fiecare pod final prime\u0219te un cost pe or\u0103 pentru utilizarea procesorului, pentru un gigabyte de memorie consumat \u0219i pentru ora de stocare a unui gigabyte de date, \u00een func\u021bie de nodul pe care a func\u021bionat sau de clasa de stocare.<\/li>\n<li> Pe baza costului de func\u021bionare al podurilor individuale, se calculeaz\u0103 plata pe spa\u021biile de nume, servicii, Deployment-uri, StatefulSet-uri.<\/li>\n<li> Pentru a calcula statisticile sunt utilizate metrici furnizate de kube-state-metrics \u0219i node-exporter.<\/li>\n<\/ul>\n<p>\nEste important de men\u021bionat c\u0103 Kubecost <b>prin default consider\u0103 doar resursele disponibile \u00een Kubernetes<\/b>. Baze de date externe, servere GitLab, stoc\u0103ri S3 \u0219i alte servicii care nu sunt prezente \u00een cluster (chiar \u0219i cele din acela\u0219i cloud) nu sunt vizibile pentru el. Cu toate acestea, pentru GCP \u0219i AWS se pot ad\u0103uga cheile conturilor de serviciu \u0219i se poate calcula totul \u00eempreun\u0103.<\/p>\n<h2>Instalare<\/h2>\n<p>\nPentru a func\u021biona Kubecost sunt necesare:<\/p>\n<ul>\n<li> Kubernetes versiunea 1.8 \u0219i mai recent\u0103;<\/li>\n<li> kube-state-metrics;<\/li>\n<li> Prometheus;<\/li>\n<li> node-exporter.<\/li>\n<\/ul>\n<p>\nA\u0219a s-a \u00eent\u00e2mplat c\u0103 \u00een clusterele noastre toate aceste condi\u021bii au fost respectate anterior, a\u0219a c\u0103 s-a dovedit a fi suficient doar s\u0103 specific\u0103m endpoint-ul corect pentru accesul \u00een Prometheus. Cu toate acestea, chart-ul Helm oficial al kubecost con\u021bine tot ceea ce este necesar pentru a porni chiar \u0219i \u00eentr-un cluster 'gol'.<\/p>\n<p>Kubecost poate fi instalat \u00een mai multe moduri: <\/p>\n<ol>\n<li> Calea standard de instalare, descris\u0103 \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/kubecost.com\/install?ref=home\">instruc\u021biuni<\/a><\/noindex> pe site-ul dezvoltatorului. Este necesar <b>s\u0103 ad\u0103uga\u021bi \u00een Helm repository-ul cost-analyzer, dup\u0103 care s\u0103 instala\u021bi chart-ul<\/b>. Nu va r\u0103m\u00e2ne dec\u00e2t s\u0103 redirec\u021biona\u021bi portul \u0219i s\u0103 finaliza\u021bi set\u0103rile manual (prin kubectl) \u0219i\/sau cu ajutorul interfe\u021bei web a cost-model.\n<p>Aceast\u0103 metod\u0103 nu am \u00eencercat-o, deoarece nu folosim configura\u021bii gata f\u0103cute din exterior, dar pare o op\u021biune bun\u0103 \u201edoar pentru a \u00eencerca\u201d. Dac\u0103 deja ave\u021bi instalate unele componente ale sistemului sau dori\u021bi o configurare mai detaliat\u0103, ar fi mai bine s\u0103 lua\u021bi \u00een considerare a doua op\u021biune.\n<\/li>\n<li> A folosi, de fapt <b><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubecost\/cost-analyzer-helm-chart\">acela\u0219i chart<\/a><\/noindex>, dar s\u0103-l configura\u021bi \u0219i s\u0103-l instala\u021bi singuri<\/b> \u00een orice mod convenabil.\n<p>A\u0219a cum s-a men\u021bionat, pe l\u00e2ng\u0103 kubecost-ul propriu-zis, acest chart con\u021bine chart-uri pentru Grafana \u0219i Prometheus, care pot fi, de asemenea, configurate dup\u0103 dorin\u021ba dumneavoastr\u0103.<\/p>\n<p>Include \u00een chart <code>values.yaml<\/code> pentru cost-analyzer permite configurarea:<\/p>\n<ul>\n<li> lista componentelor cost-analyzer care trebuie desf\u0103\u0219urate;<\/li>\n<li> endpointul dumneavoastr\u0103 pentru Prometheus (dac\u0103 deja ave\u021bi unul);<\/li>\n<li> domeniile \u0219i alte set\u0103ri pentru ingress-uri pentru cost-model \u0219i Grafana;<\/li>\n<li> anota\u021bii pentru pod-uri;<\/li>\n<li> necesitatea de a folosi stoc\u0103ri permanente \u0219i dimensiunea acestora.<\/li>\n<\/ul>\n<p>\nLista complet\u0103 a op\u021biunilor disponibile pentru configurare este \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubecost\/cost-analyzer-helm-chart\">documentation<\/a><\/noindex>.<\/p>\n<p>Deoarece kubecost, \u00een varianta sa de baz\u0103, nu limiteaz\u0103 accesul, va trebui s\u0103 configura\u021bi mai \u00eent\u00e2i basic-auth pentru panoul web.\n<\/li>\n<li> Instaleaz\u0103 <b>doar nucleul sistemului<\/b> \u2014 cost-model. Pentru aceasta, trebuie s\u0103 ave\u021bi Prometheus instalat \u00een cluster \u0219i s\u0103 specifica\u021bi adresa sa \u00een variabila <code>prometheusEndpoint<\/code> pentru Helm. Dup\u0103 aceea \u2014 aplica\u021bi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubecost\/cost-model\/tree\/master\/kubernetes\">setul de configura\u021bii YAML<\/a><\/noindex> \u00een cluster.\n<p>Din nou, va trebui s\u0103 ad\u0103uga\u021bi manual Ingress cu basic-auth. \u0218i, \u00een final, va trebui s\u0103 ad\u0103uga\u021bi o sec\u021biune pentru colectarea metricilor cost-model \u00een <code>extraScrapeConfigs<\/code> din configura\u021bia Prometheus:<\/p>\n<pre><code class=\"plaintext\">- job_name: kubecost\n  honor_labels: true\n  scrape_interval: 1m\n  scrape_timeout: 10s\n  metrics_path: \/metrics\n  scheme: http\n  dns_sd_configs:\n  - names:\n    - \n    type: 'A'\n    port: 9003<\/code><\/pre>\n<\/li>\n<\/ol>\n<p><\/p>\n<h2>Ce ob\u021binem?<\/h2>\n<p>\n\u00cen cazul unei instal\u0103ri complete, vom avea la dispozi\u021bie panoul web kubecost \u0219i Grafana cu un set de dashboard-uri.<\/p>\n<p><b>Cost total<\/b>, afi\u0219at pe ecranul principal, arat\u0103 practic costul estimat al resurselor pe lun\u0103. Acesta este <i>un pre\u021b prognozat<\/i> care reflect\u0103 costul utiliz\u0103rii clusterului (pe lun\u0103) la nivelul curent de consum al resurselor.<\/p>\n<p>Aceast\u0103 metric\u0103 este mai mult pentru analiza cheltuielilor \u0219i optimizarea acestora. Cheltuielile totale pentru luna abstract\u0103 iulie \u00een kubecost nu sunt foarte u\u0219or de urm\u0103rit: va trebui s\u0103 <b>merge\u021bi la facturare<\/b>. Totu\u0219i, pute\u021bi vedea cheltuielile defalcate pe spa\u021bii de nume, etichete, pod-uri pe 1\/2\/7\/30\/90 zile, ceea ce facturarea nu v\u0103 va ar\u0103ta niciodat\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Recenzia Kubecost pentru economisirea de fonduri pe Kubernetes \u00een cloud-uri\" src=\"\/wp-content\/uploads\/2019\/09\/45db0df267d17e2814003580d87b4048.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nC\u00e2t despre <b>etichete<\/b>. Este bine s\u0103 accesa\u021bi imediat set\u0103rile \u0219i s\u0103 specifica\u021bi denumirile etichetelor care vor fi utilizate ca categorii suplimentare pentru gruparea cheltuielilor:<\/p>\n<p><img decoding=\"async\" alt=\"Recenzia Kubecost pentru economisirea de fonduri pe Kubernetes \u00een cloud-uri\" src=\"\/wp-content\/uploads\/2019\/09\/d953f8c6205495e43343e97977431ba6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPe acestea se pot ata\u0219a orice etichete \u2014 convenabil dac\u0103 ave\u021bi deja propriul sistem de etichetare.<\/p>\n<p>De asemenea, acolo pute\u021bi schimba adresa endpoint-ului API la care se conecteaz\u0103 cost-model, s\u0103 seta\u021bi discount-ul \u00een GCP \u0219i s\u0103 specifica\u021bi pre\u021burile proprii pentru resurse \u0219i moneda pentru m\u0103surarea acestora (func\u021bionalitatea nu afecteaz\u0103 Total cost din motive inexplicabile).<\/p>\n<p>Kubecost poate ar\u0103ta diferite <b>probleme \u00een cluster<\/b> (\u0219i chiar s\u0103 alerteze \u00een caz de pericol). Din p\u0103cate, op\u021biunea nu este configurabil\u0103, a\u0219a c\u0103, dac\u0103 ave\u021bi medii pentru dezvoltatori \u0219i acestea sunt utilizate, ve\u021bi putea observa constant ceva de genul:<\/p>\n<p><img decoding=\"async\" alt=\"Recenzia Kubecost pentru economisirea de fonduri pe Kubernetes \u00een cloud-uri\" src=\"\/wp-content\/uploads\/2019\/09\/729af727faeb10d1ad0384fb4de121f7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nUn instrument important \u2014 <b>Cluster Savings<\/b>. Acesta m\u0103soar\u0103 activitatea pod-urilor (consumul de resurse, inclusiv cel de re\u021bea) \u0219i calculeaz\u0103 c\u00e2t de mul\u021bi bani se pot economisi \u0219i pe ce.<\/p>\n<p>Poate p\u0103rea c\u0103 sfaturile pentru optimizare sunt destul de evidente, totu\u0219i experien\u021ba sugereaz\u0103 c\u0103 tot exist\u0103 lucruri de observat. \u00cen special, se monitorizeaz\u0103 activitatea de re\u021bea a pod-urilor (Kubecost sugereaz\u0103 s\u0103 se acorde aten\u021bie celor inactive), se compar\u0103 consumul solicitat \u0219i cel real de memorie \u0219i CPU, precum \u0219i CPU-ul utilizat de nodurile clusterului (sugereaz\u0103 comprimarea mai multor noduri \u00eentr-unul), sarcina pe discuri \u0219i \u00eenc\u0103 c\u00e2teva zeci de parametri.<\/p>\n<p>Ca \u00een orice problem\u0103 legat\u0103 de optimizare, optimizarea resurselor bazat\u0103 pe datele Kubecost trebuie <b>manipulat\u0103 cu precau\u021bie<\/b>. De exemplu, Cluster Savings sugereaz\u0103 s\u0103 se elimine noduri, afirm\u00e2nd c\u0103 este sigur, \u00eens\u0103 nu ia \u00een considerare existen\u021ba selec\u021biilor de noduri \u0219i a taint-urilor la pod-urile desf\u0103\u0219urate pe acestea, care nu exist\u0103 pe celelalte noduri. \u00cen plus, chiar \u0219i autorii produsului \u00een propria lor <noindex><a rel=\"nofollow\" href=\"http:\/\/blog.kubecost.com\/blog\/cost-monitoring\/\">un articol recent<\/a><\/noindex> (de altfel, aceasta poate fi foarte util\u0103 celor interesa\u021bi de subiectul proiectului) recomand\u0103 s\u0103 nu se arunce cu capul \u00eenainte \u00een optimizarea cheltuielilor, ci s\u0103 se abordeze aceast\u0103 problem\u0103 cu aten\u021bie.<\/p>\n<h2>Concluzii<\/h2>\n<p>\nDup\u0103 utilizarea kubecost timp de o lun\u0103 pe c\u00e2teva proiecte, putem concluziona c\u0103 acesta este un instrument interesant (\u0219i de asemenea u\u0219or de \u00eenv\u0103\u021bat \u0219i instalat) pentru analiza \u0219i optimizarea cheltuielilor pentru serviciile furnizorilor de cloud utilizate pentru clusterele Kubernetes. Calculul este destul de precis: \u00een experimentele noastre s-a potrivit cu ceea ce cer furnizorii \u00een realitate.<\/p>\n<p>Nu au lipsit nici minusurile: exist\u0103 erori necritice, func\u021bionalit\u0103\u021bile nu acoper\u0103 uneori nevoile specifice ale anumitor proiecte. Totu\u0219i, dac\u0103 trebuie s\u0103 \u00een\u021belegi rapid unde se duc banii \u0219i ce po\u021bi 't\u0103ia' pentru a reduce constant factura pentru serviciile cloud cu 5-30% (a\u0219a s-a \u00eent\u00e2mplat \u00een cazul nostru), este o op\u021biune excelent\u0103.<\/p>\n<h2>P.S.<\/h2>\n<p>\nCiti\u021bi \u0219i \u00een blogul nostru:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/459326\/\">Autoscalarea \u0219i gestionarea resurselor \u00een Kubernetes (prezentare general\u0103 \u0219i videoclip prezentare)<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/460877\/\">Tranzi\u021bia Tinder la Kubernetes<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/432748\/\">Tips &amp; tricks pentru Kubernetes: despre alocarea nodurilor \u0219i despre sarcinile pe aplica\u021bia web<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/466659\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0432\u0441\u0451 \u0431\u043e\u043b\u044c\u0448\u0435 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0439 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u044f\u0442 \u0441\u0432\u043e\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u0441 \u0436\u0435\u043b\u0435\u0437\u043d\u044b\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0438 \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0445 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u043e\u043a \u0432 \u043e\u0431\u043b\u0430\u043a\u0430. \u0422\u0430\u043a\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u043b\u0435\u0433\u043a\u043e \u043e\u0431\u044a\u044f\u0441\u043d\u0438\u0442\u044c: \u043d\u0435\u0442 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u0438 \u0437\u0430\u0431\u043e\u0442\u0438\u0442\u044c\u0441\u044f \u043e \u0436\u0435\u043b\u0435\u0437\u0435, \u043a\u043b\u0430\u0441\u0442\u0435\u0440 \u043b\u0435\u0433\u043a\u043e \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e\u043c \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u0441\u043f\u043e\u0441\u043e\u0431\u043e\u0432\u2026 \u0430 \u0441\u0430\u043c\u043e\u0435 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u2014 \u0438\u043c\u0435\u044e\u0449\u0438\u0435\u0441\u044f \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438 (\u0432\u0440\u043e\u0434\u0435 Kubernetes) \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u0440\u043e\u0441\u0442\u043e \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0432\u044b\u0447\u0438\u0441\u043b\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u0438 \u0432 \u0437\u0430\u0432\u0438\u0441\u0438\u043c\u043e\u0441\u0442\u0438 \u043e\u0442 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438. \u0412\u0441\u0435\u0433\u0434\u0430 \u0432\u0430\u0436\u0435\u043d \u0438 \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0439 \u0430\u0441\u043f\u0435\u043a\u0442. \u0418\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28612,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38112","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.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0432\u0441\u0451 \u0431\u043e\u043b\u044c\u0448\u0435.\" \/>\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\/ro\/blog\/administrirovanie\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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 Kubecost \u0434\u043b\u044f \u044d\u043a\u043e\u043d\u043e\u043c\u0438\u0438 \u0441\u0440\u0435\u0434\u0441\u0442\u0432 \u043d\u0430 Kubernetes \u0432 \u043e\u0431\u043b\u0430\u043a\u0430\u0445 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0432\u0441\u0451 \u0431\u043e\u043b\u044c\u0448\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:21:44+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:21:44+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\udd47Recenzia Kubecost pentru economisirea fondurilor pe Kubernetes \u00een cloud | ProHoster","description":"\u00cen prezent, din ce \u00een ce mai multe.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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 Kubecost \u0434\u043b\u044f \u044d\u043a\u043e\u043d\u043e\u043c\u0438\u0438 \u0441\u0440\u0435\u0434\u0441\u0442\u0432 \u043d\u0430 Kubernetes \u0432 \u043e\u0431\u043b\u0430\u043a\u0430\u0445 | ProHoster","og:description":"\u0412 \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0432\u0441\u0451 \u0431\u043e\u043b\u044c\u0448\u0435.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/obzor-kubecost-dlya-ekonomii-sredstv-na-kubernetes-v-oblakah","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:21:44+00:00","article:modified_time":"2019-10-31T19:21:44+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38112","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 20:30:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:15:22","updated":"2026-01-23 20:30:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/38112","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=38112"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/38112\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/28612"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=38112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=38112"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=38112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}