{"id":82223,"date":"2020-05-20T13:42:34","date_gmt":"2020-05-20T11:42:34","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen"},"modified":"2020-05-20T13:42:34","modified_gmt":"2020-05-20T11:42:34","slug":"luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","title":{"rendered":"Cele mai bune practici Kubernetes. Organizarea Kubernetes cu spa\u021bii de nume","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Cele mai bune practici Kubernetes. Crearea de containere mici<\/a><\/noindex><\/p>\n

Pe m\u0103sur\u0103 ce \u00eencepe\u021bi s\u0103 crea\u021bi tot mai multe servicii Kubernetes, sarcinile ini\u021bial simple devin mai complexe. De exemplu, echipele de dezvoltare nu pot crea servicii sau desf\u0103\u0219ur\u0103ri cu acela\u0219i nume. Dac\u0103 ave\u021bi mii de poduri, enumerarea acestora va dura mult timp, f\u0103r\u0103 a men\u021biona gestionarea corect\u0103 a acestora. \u0218i aceasta este doar v\u00e2rful aisbergului.<\/p>\n

S\u0103 analiz\u0103m cum spa\u021biul de nume faciliteaz\u0103 gestionarea resurselor Kubernetes. A\u0219adar, ce este un spa\u021biu de nume? Un spa\u021biu de nume poate fi considerat un cluster virtual \u00een cadrul cluster-ului dvs. Kubernetes. Pute\u021bi avea mai multe spa\u021bii de nume izolate unul de cel\u0103lalt \u00eentr-un singur cluster Kubernetes. Acestea pot ajuta cu adev\u0103rat pe dvs. \u0219i echipele dvs. \u00een organizare, securitate \u0219i chiar performan\u021b\u0103 a sistemului.<\/p>\n

\"Cele
\n
\n\u00cen majoritatea distribu\u021biilor Kubernetes, cluster-ul vine \u201edin fabric\u0103\u201d cu un spa\u021biu de nume numit \u201edefault\u201d. De fapt, exist\u0103 trei spa\u021bii de nume cu care Kubernetes interac\u021bioneaz\u0103: default, kube-system \u0219i kube-public. \u00cen prezent, Kube-public nu este utilizat foarte des.<\/a><\/noindex><\/p>\n

\"Cele
\n
\nE bine s\u0103 nu modifica\u021bi spa\u021biul de nume kube, mai ales \u00eentr-un sistem gestionat, cum ar fi Google Kubernetes Engine. Acesta folose\u0219te spa\u021biul de nume \u201edefault\u201d ca loc pentru a crea serviciile \u0219i aplica\u021biile dvs. Nu are absolut nimic special, \u00een afar\u0103 de faptul c\u0103 Kubernetes este configurat \u201edin fabric\u0103\u201d s\u0103-l utilizeze, \u0219i nu pute\u021bi s\u0103-l \u0219terge\u021bi. Este ideal pentru a \u00eencepe \u0219i pentru sistemele cu performan\u021b\u0103 mic\u0103, dar nu a\u0219 recomanda utilizarea spa\u021biului de nume default \u00een sistemele mari de produc\u021bie. \u00cen acest ultim caz, o echip\u0103 de dezvoltatori ar putea scrie u\u0219or codul altcuiva \u0219i ar putea afecta munca altei echipe, f\u0103r\u0103 s\u0103 con\u0219tientizeze acest lucru.<\/p>\n

De aceea ar trebui s\u0103 crea\u021bi mai multe spa\u021bii de nume \u0219i s\u0103 le folosi\u021bi pentru a segmenta serviciile \u00een link-uri gestionate. Un spa\u021biu de nume poate fi creat cu o singur\u0103 comand\u0103. Dac\u0103 dori\u021bi s\u0103 crea\u021bi un spa\u021biu de nume numit test, folosi\u021bi comanda $ kubectl create namespace test sau crea\u021bi pur \u0219i simplu un fi\u0219ier YAML \u0219i folosi\u021bi-l ca pe orice alt resurs Kubernetes.<\/p>\n

\"Cele
\n
\nPute\u021bi vizualiza toate spa\u021biile de nume utiliz\u00e2nd comanda $ kubectl get namespace. <\/p>\n

\"Cele
\n
\nDup\u0103 finalizarea acesteia, ve\u021bi vedea trei spa\u021bii de nume integrate \u0219i un nou spa\u021biu de nume numit \u201etest\u201d. S\u0103 examin\u0103m un fi\u0219ier YAML simplu, destinat s\u0103 creeze un pod. Se poate observa c\u0103 nu exist\u0103 nicio men\u021biune a spa\u021biului de nume.<\/p>\n

\"Cele
\n
\nDac\u0103 utiliza\u021bi kubectl pentru a rula acest fi\u0219ier, va crea modulul mypod \u00een spa\u021biul de nume activ actual. Acesta va fi spa\u021biul de nume implicit, p\u00e2n\u0103 c\u00e2nd \u00eel schimba\u021bi. Exist\u0103 dou\u0103 moduri de a informa Kubernetes \u00een ce spa\u021biu de nume dori\u021bi s\u0103 crea\u021bi resursa dvs. Primul mod este de a folosi flag-ul de spa\u021biu de nume atunci c\u00e2nd crea\u021bi resursa. <\/p>\n

\"Cele
\n
\nAl doilea mod const\u0103 \u00een a specifica spa\u021biul de nume \u00een declara\u021bia YAML.<\/p>\n

\"Cele
\n
\nDac\u0103 specifica\u021bi spa\u021biul de nume \u00een YAML, atunci resursa va fi \u00eentotdeauna creat\u0103 \u00een acest spa\u021biu. Dac\u0103 \u00eencerca\u021bi s\u0103 folosi\u021bi un alt spa\u021biu de nume c\u00e2nd folosi\u021bi flag-ul de spa\u021biu de nume, comanda va e\u0219ua. Acum, dac\u0103 \u00eencerca\u021bi s\u0103 g\u0103si\u021bi podul dvs., nu ve\u021bi putea face acest lucru. <\/p>\n

\"Cele
\n
\nAcest lucru se \u00eent\u00e2mpl\u0103 deoarece toate comenzile sunt executate \u00een afara spa\u021biului de nume activ curent. Pentru a g\u0103si podul dvs., trebuie s\u0103 folosi\u021bi flag-ul de spa\u021biu de nume, \u00eens\u0103 acest lucru devine rapid plictisitor, mai ales dac\u0103 lucra\u021bi ca dezvoltator \u00eentr-un grup care folose\u0219te propriul spa\u021biu de nume \u0219i nu vrea s\u0103 foloseasc\u0103 un astfel de flag pentru fiecare comand\u0103. S\u0103 vedem cum putem rezolva aceast\u0103 problem\u0103.<\/p>\n

\"Cele
\n
\nDin fabrica\u021bie, spa\u021biul de nume activ se nume\u0219te default. Dac\u0103 nu espec\u00edfica\u021bi spa\u021biul de nume \u00een YAML-ul resursei, toate comenzile Kubernetes vor folosi acest spa\u021biu de nume activ default. Din p\u0103cate, \u00eencercarea de a gestiona spa\u021biul de nume activ cu kubectl poate e\u0219ua. Totu\u0219i, exist\u0103 un instrument excelent numit Kubens care simplific\u0103 mult acest proces. C\u00e2nd rula\u021bi comanda kubens, vede\u021bi toate spa\u021biile de nume cu spa\u021biul de nume activ eviden\u021biat. <\/p>\n

\"Cele
\n
\nPentru a schimba spa\u021biul de nume activ \u00een spa\u021biul de nume test, trebuie doar s\u0103 rula\u021bi comanda $ kubens test. Dac\u0103, dup\u0103 aceasta, introduce\u021bi din nou comanda $ kubens, pute\u021bi observa c\u0103 acum este eviden\u021biat un nou spa\u021biu de nume activ \u2013 test.<\/p>\n

\"Cele
\n
\nAceasta \u00eenseamn\u0103 c\u0103 nu ave\u021bi nevoie de un steag de spa\u021biu de nume pentru a vedea pod-ul \u00een spa\u021biul de nume test.<\/p>\n

\"Cele
\n
\nAstfel, spa\u021biile de nume sunt ascunse una de cealalt\u0103, dar nu sunt izolate. Un serviciu dintr-un spa\u021biu de nume poate comunica destul de u\u0219or cu un serviciu din alt spa\u021biu de nume, ceea ce este adesea foarte util. Posibilitatea de comunicare \u00eentre diferite spa\u021bii de nume \u00eenseamn\u0103 c\u0103 serviciul dezvoltatorilor dumneavoastr\u0103 poate interac\u021biona cu serviciul unei alte echipe de dezvoltare \u00eentr-un alt spa\u021biu de nume.<\/p>\n

De obicei, atunci c\u00e2nd aplica\u021bia dvs. dore\u0219te s\u0103 acceseze un serviciu Kubernetes, folosi\u021bi serviciul de descoperire DNS \u00eencorporat \u0219i pur \u0219i simplu indica\u021bi aplica\u021biei numele serviciului. Cu toate acestea, pute\u021bi crea un serviciu cu acela\u0219i nume \u00een mai multe spa\u021bii de nume, ceea ce este inacceptabil. <\/p>\n

\"Cele
\n
\nDin fericire, acest lucru este u\u0219or de ocolit, folosind forma extins\u0103 a adresei DNS. Serviciile din Kubernetes \u00ee\u0219i expun punctele finale folosind un \u0219ablon comun DNS. Acesta arat\u0103 cam a\u0219a:<\/p>\n

\"Cele
\n
\n\u00cen general, trebuie doar s\u0103 furniza\u021bi numele serviciului, iar DNS va determina automat adresa complet\u0103. <\/p>\n

\"Cele
\n
\nCu toate acestea, dac\u0103 trebuie s\u0103 accesa\u021bi un serviciu dintr-un alt spa\u021biu de nume, folosi\u021bi pur \u0219i simplu numele serviciului plus numele spa\u021biului de nume:<\/p>\n

\"Cele
\n
\nDe exemplu, dac\u0103 dori\u021bi s\u0103 v\u0103 conecta\u021bi la baza de date a serviciului din spa\u021biul de nume de testare, pute\u021bi folosi adresa database.test.<\/p>\n

\"Cele
\n
\nDac\u0103 dori\u021bi s\u0103 v\u0103 conecta\u021bi la baza de date a serviciului din spa\u021biul de nume prod, utiliza\u021bi database.prod.<\/p>\n

\"Cele
\n
\nDac\u0103 dori\u021bi cu adev\u0103rat s\u0103 izola\u021bi \u0219i s\u0103 restric\u021biona\u021bi accesul la un spa\u021biu de nume, Kubernetes v\u0103 permite s\u0103 face\u021bi acest lucru prin intermediul politicilor de re\u021bea Kubernetes Network Policies. Voi discuta despre asta \u00een urm\u0103toarea serie. <\/p>\n

Mi se pune adesea \u00eentrebarea c\u00e2te spa\u021bii de nume ar trebui s\u0103 crea\u021bi \u0219i \u00een ce scopuri? Ce reprezint\u0103 un fragment de date gestionat?<\/p>\n

Dac\u0103 crea\u021bi prea multe namespace-uri, acestea vor deveni o piedic\u0103. Dar dac\u0103 sunt prea pu\u021bine, ve\u021bi pierde toate avantajele unei astfel de solu\u021bii. Cred c\u0103 exist\u0103 patru etape principale prin care trece fiecare companie \u00een procesul de creare a structurii sale organiza\u021bionale. \u00cen func\u021bie de etapa de dezvoltare \u00een care se afl\u0103 proiectul sau compania dumneavoastr\u0103, pute\u021bi adopta strategia corespunz\u0103toare pentru crearea namespace-urilor.<\/p>\n

Imagina\u021bi-v\u0103 c\u0103 face\u021bi parte dintr-o echip\u0103 mic\u0103 care lucreaz\u0103 la dezvoltarea a 5-10 microservicii \u0219i c\u0103 pute\u021bi aduna u\u0219or to\u021bi dezvoltatorii \u00eentr-o camer\u0103. \u00cen aceast\u0103 situa\u021bie, are sens s\u0103 rula\u021bi toate serviciile prod \u00een namespace-ul default. Desigur, pentru mai mult\u0103 libertate de ac\u021biune, pute\u021bi utiliza 2 namespace-uri \u2013 c\u00e2te unul pentru prod \u0219i dev. Cel mai probabil, testa\u021bi dezvoltarea pe computerul local folosind ceva de genul Minikube. <\/p>\n

S\u0103 presupunem c\u0103 condi\u021biile s-au schimbat \u0219i acum ave\u021bi o echip\u0103 \u00een rapid\u0103 expansiune care lucreaz\u0103 simultan la mai mult de 10 microservicii. Vine un moment c\u00e2nd este necesar s\u0103 folosi\u021bi mai multe clustere sau namespace-uri, separate pentru prod \u0219i dev. Pute\u021bi \u00eemp\u0103r\u021bi echipa \u00een mai multe subgrupuri, astfel \u00eenc\u00e2t fiecare s\u0103 aib\u0103 propriile microservicii \u0219i fiecare dintre aceste echipe s\u0103 poat\u0103 alege propriul namespace pentru a facilita procesul de gestionare a dezvolt\u0103rii \u0219i lans\u0103rii software-ului.<\/p>\n

\"Cele
\n
\nPe m\u0103sur\u0103 ce fiecare membru al echipei ob\u021bine o \u00een\u021belegere a modului \u00een care func\u021bioneaz\u0103 sistemul \u00een ansamblu, coordonarea fiec\u0103rei modific\u0103ri cu to\u021bi ceilal\u021bi dezvoltatori devine din ce \u00een ce mai dificil\u0103. \u00cencercarea de a rula stack-ul complet pe computerul local devine mai complicat\u0103 cu fiecare zi. <\/p>\n

\u00cen companiile mari, dezvoltatorii nu \u0219tiu deloc cine lucreaz\u0103 la ce. Echipele comunic\u0103 prin intermediul contractelor de servicii sau folosesc tehnologia Service mesh, care adaug\u0103 un nivel de abstrac\u021bie deasupra re\u021belei, similar cu instrumentul de configurare Istio. \u00cencercarea de a rula \u00eentregul stiv\u0103 local este pur \u0219i simplu imposibil\u0103. Recomand cu t\u0103rie utilizarea unei platforme de livrare continu\u0103 (CD) \u00een Kubernetes, cum ar fi Spinnaker. Iat\u0103 c\u0103 vine momentul \u00een care fiecare echip\u0103 are nevoie de propriul spa\u021biu de nume. Fiecare echip\u0103 poate alege chiar \u0219i c\u00e2teva spa\u021bii de nume pentru mediu dev \u0219i mediu prod. <\/p>\n

\u00cen cele din urm\u0103, exist\u0103 mari companii antreprenoriale \u00een care un grup de dezvoltatori nu \u0219tie nici m\u0103car de existen\u021ba altor grupuri. O astfel de companie poate angaja chiar dezvoltatori externi care interac\u021bioneaz\u0103 prin intermediul unor API-uri bine documentate. \u00cen fiecare astfel de grup exist\u0103 c\u00e2teva echipe \u0219i c\u00e2teva microservicii. \u00cen acest caz, este necesar s\u0103 se foloseasc\u0103 toate instrumentele despre care am vorbit mai devreme.<\/p>\n

\"Cele
\n
\nProgramatorii nu ar trebui s\u0103 desf\u0103\u0219oare servicii manual \u0219i nu ar trebui s\u0103 aib\u0103 acces la spa\u021biile de nume care nu \u00eei privesc. \u00cen aceast\u0103 etap\u0103, este prudent s\u0103 se aib\u0103 mai multe clustere pentru a reduce \u201eraza de explozie\u201d a aplica\u021biilor prost configurate, pentru a simplifica procesele de facturare \u0219i gestionare a resurselor.<\/p>\n

Astfel, utilizarea corect\u0103 a spa\u021biilor de nume de c\u0103tre organiza\u021bia dumneavoastr\u0103 face Kubernetes mai gestionabil, controlabil, sigur \u0219i flexibil.<\/p>\n

Cele mai bune practici Kubernetes. Verificarea livrabilit\u0103\u021bii Kubernetes cu teste de Readiness \u0219i Liveness<\/a><\/noindex><\/p>\n

\r\n \"Reda\u021bi\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Pu\u021bin publicitate \ud83d\ude42<\/h3>\n

\nMul\u021bumim c\u0103 r\u0103m\u00e2ne\u021bi cu noi. V\u0103 plac articolele noastre? Dori\u021bi s\u0103 vede\u021bi mai multe materiale interesante? Sus\u021bine\u021bi-ne, efectu\u00e2nd o comand\u0103 sau recomand\u00e2ndu-ne prietenilor, VPS cloud pentru dezvoltatori de la 4,99 $<\/a><\/noindex>, un echivalent unic pentru serverele entry-level, care a fost creat de noi pentru voi:<\/b> Toat\u0103 adev\u0103rul despre VPS (KVM) E5-2697 v3 (6 nuclee) 10GB DDR4 480GB SSD 1Gbps de la 19 $ sau cum s\u0103 \u00eemp\u0103r\u021bi\u021bi corect un server?<\/a><\/noindex> (sunt disponibile op\u021biuni cu RAID1 \u0219i RAID10, p\u00e2n\u0103 la 24 nuclee \u0219i p\u00e2n\u0103 la 40GB DDR4).<\/p>\n

Dell R730xd la jum\u0103tate de pre\u021b \u00een centrul de date Equinix Tier IV din Amsterdam?<\/b> Numai la noi 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB de la 199 $<\/a><\/noindex> \u00een Olanda! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 de la 99 $!<\/b><\/b> Citi\u021bi despre Cum s\u0103 construi\u021bi o infrastructur\u0103 de clas\u0103 enterprise folosind servere Dell R730xd E5-2650 v4 la pre\u021buri foarte mici de 9000 \u20ac?<\/a><\/noindex>
\n
Sursa: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u0421\u043e\u0437\u0434\u0430\u043d\u0438\u0435 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u041f\u043e \u043c\u0435\u0440\u0435 \u0442\u043e\u0433\u043e \u043a\u0430\u043a \u0432\u044b \u043d\u0430\u0447\u0438\u043d\u0430\u0435\u0442\u0435 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0432\u0441\u0435 \u0431\u043e\u043b\u044c\u0448\u0435 \u0438 \u0431\u043e\u043b\u044c\u0448\u0435 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 Kubernetes, \u043f\u0440\u043e\u0441\u0442\u044b\u0435 \u043f\u043e \u043d\u0430\u0447\u0430\u043b\u0443 \u0437\u0430\u0434\u0430\u0447\u0438 \u043d\u0430\u0447\u0438\u043d\u0430\u044e\u0442 \u0443\u0441\u043b\u043e\u0436\u043d\u044f\u0442\u044c\u0441\u044f. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u043e\u0432 \u043d\u0435 \u043c\u043e\u0433\u0443\u0442 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0441\u043b\u0443\u0436\u0431\u044b \u0438\u043b\u0438 \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u043f\u043e\u0434 \u043e\u0434\u043d\u0438\u043c \u0438 \u0442\u0435\u043c \u0436\u0435 \u0438\u043c\u0435\u043d\u0435\u043c. \u0415\u0441\u043b\u0438 \u0443 \u0432\u0430\u0441 \u0442\u044b\u0441\u044f\u0447\u0438 \u043f\u043e\u0434\u043e\u0432, \u0438\u0445 \u043f\u0440\u043e\u0441\u0442\u043e\u0435 \u043f\u0435\u0440\u0435\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u0435 \u0437\u0430\u0439\u043c\u0435\u0442 \u043a\u0443\u0447\u0443 \u0432\u0440\u0435\u043c\u0435\u043d\u0438, \u043d\u0435 \u0433\u043e\u0432\u043e\u0440\u044f \u043e \u0442\u043e\u043c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":82224,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82223","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\udd47Cele mai bune practici Kubernetes. Organizarea Kubernetes cu spa\u021biu de nume | ProHoster","description":"Cele mai bune practici Kubernetes.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","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\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes. \u041e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f Kubernetes \u0441 \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u043e\u043c \u0438\u043c\u0435\u043d | ProHoster","og:description":"\u041b\u0443\u0447\u0448\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 Kubernetes.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/luchshie-praktiki-kubernetes-organizacziya-kubernetes-s-prostranstvom-imen","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-05-20T11:42:34+00:00","article:modified_time":"2020-05-20T11:42:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82223","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 15:41:29","updated":"2022-09-29 19:27:31","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\/82223","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=82223"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/82223\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/82224"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=82223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=82223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=82223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}