{"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\/sk\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","title":{"rendered":"Najlep\u0161\u00edch 10 trikov a tipov pre Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Najlep\u0161\u00edch
\n
\nNa internete je mnoho referen\u010dnej literat\u00fary, ale niekedy sa ukazuj\u00fa ako najcennej\u0161ie najjednoduch\u0161ie rady. T\u00edm Kubernetes aaS od Mail.ru<\/a><\/noindex> prelo\u017eil v\u00fdber desiatich trikov a tipov<\/a><\/noindex>, ktor\u00e9 autor \u010dl\u00e1nku zhroma\u017edil po roku pr\u00e1ce s Kubernetes. Tipy nie s\u00fa zoraden\u00e9 pod\u013ea d\u00f4le\u017eitosti, ale mysl\u00edme si, \u017ee si ka\u017ed\u00fd n\u00e1jde nie\u010do u\u017eito\u010dn\u00e9 pre seba.
\n<\/a><\/noindex><\/p>\n

Najjednoduch\u0161\u00ed pr\u00edkaz pri pr\u00e1ci s Kubernetes<\/h2>\n

\nNa za\u010diatok, sn\u00e1\u010f najjednoduch\u0161ia a naju\u017eito\u010dnej\u0161ia akcia pri pr\u00e1ci s Kubernetes. Nasleduj\u00faci pr\u00edkaz aktivuje automatick\u00e9 dopl\u0148ovanie pr\u00edkazov kubectl<\/code> v shelli bash:<\/p>\n

echo \"source > ~\/.ashrc\n<\/code><\/pre>\n
\nAutomatick\u00e9 dopl\u0148ovanie kubectl<\/code> sa zap\u00ed\u0161e do s\u00faboru .bashrc a automaticky sa aktivuje pri ka\u017edom spusten\u00ed shellu. To ur\u00fdch\u013euje zad\u00e1vanie dlh\u00fdch pr\u00edkazov a parametrov, ako je all-namespaces<\/code>. Viac inform\u00e1ci\u00ed n\u00e1jdete v pr\u00edru\u010dke Kubernetes pre bash<\/a><\/noindex>.<\/p>\n
Predvolen\u00e9 obmedzenia pam\u00e4te a CPU v mennom priestore<\/h2>\n
\nAk je aplik\u00e1cia nap\u00edsan\u00e1 nespr\u00e1vne, napr\u00edklad ka\u017ed\u00fa sekundu otv\u00e1ra nov\u00e9 spojenie s datab\u00e1zou, ale nikdy ho nezatv\u00e1ra, v klastre doch\u00e1dza k \u00faniku pam\u00e4te. A ak pre aplik\u00e1ciu nie s\u00fa pri nasaden\u00ed nastaven\u00e9 obmedzenia pam\u00e4te, m\u00f4\u017ee to vies\u0165 k zlyhaniu uzla.<\/p>\n
Aby sa tomu predi\u0161lo, Kubernetes umo\u017e\u0148uje nastavi\u0165 predvolen\u00e9 obmedzenia pre ka\u017ed\u00fd menn\u00fd priestor. Tieto obmedzenia s\u00fa zap\u00edsan\u00e9 v yaml s\u00fabore pre konkr\u00e9tny menn\u00fd priestor. Tu je pr\u00edklad tak\u00e9ho s\u00faboru:<\/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
\nVytvorte tak\u00fdto yaml a aplikujte ho na ak\u00fdko\u013evek menn\u00fd priestor. Napr\u00edklad na menn\u00fd priestor limit-example<\/code>. Teraz bude pre ka\u017ed\u00fd kontajner nasaden\u00fd v tomto mennom priestore plati\u0165 limit 512Mi, ak pre dan\u00fd kontajner nie je navy\u0161e nastaven\u00fd in\u00fd individu\u00e1lny limit.<\/p>\n
Odstra\u0148ovanie odpadu v star\u0161\u00edch verzi\u00e1ch Kubernetes<\/h2>\n
\nKubelet predvolene za\u010d\u00edna odstra\u0148ovanie odpadu, ke\u010f var\/lib\/docker<\/i> zaber\u00e1 90 % dostupn\u00e9ho diskov\u00e9ho priestoru. To je skvel\u00e9, av\u0161ak pred verziou Kubernetes 1.7 neexistoval \u017eiadny predvolen\u00fd limit na po\u010det pou\u017e\u00edvan\u00fdch indexov\u00fdch deskriptorov inode (inodov), ktor\u00e9 zodpovedaj\u00fa po\u010dtu s\u00faborov v s\u00faborovom syst\u00e9me.<\/p>\n
Potenci\u00e1lne v\u00e1\u0161 kontajner var\/lib\/docker<\/i> m\u00f4\u017ee vyu\u017e\u00edva\u0165 len 50 % diskov\u00e9ho priestoru, ale inody m\u00f4\u017eu by\u0165 vy\u010derpan\u00e9, \u010do vyvol\u00e1 probl\u00e9my v pr\u00e1ci pracovn\u00edkov.<\/p>\n
Vo star\u0161\u00edch verzi\u00e1ch kubelet od 1.4 do 1.6 je potrebn\u00e9 prida\u0165 t\u00fato vlajku:<\/p>\n
--eviction-hard\n=memory.available<100Mi,nodefs.available<10%,nodefs.inodesFree<5%\n<\/code><\/pre>\n
\nVo verzii 1.7 a nov\u0161\u00edch je t\u00e1to vlajka nastaven\u00e1 predvolene. Star\u0161ie verzie v\u0161ak nesleduj\u00fa limit in\u00f3d.<\/p>\n
Minikube\u2026 mal\u00fd, ale v\u00fdkonn\u00fd lok\u00e1lny Kubernetes<\/h2>\n
\nMinikube je najjednoduch\u0161\u00ed sp\u00f4sob, ako spusti\u0165 lok\u00e1lny klaster Kubernetes. Sp\u00fa\u0161\u0165a sa jednoduch\u00fdm pr\u00edkazom:<\/p>\n
minikube start\n<\/code><\/pre>\n
\nPo vykonan\u00ed tohto pr\u00edkazu m\u00e1te na po\u010d\u00edta\u010di skuto\u010dn\u00fd klaster Kubernetes.<\/p>\n
\"Najlep\u0161\u00edch
\nZdroj ilustr\u00e1cie<\/i><\/a><\/noindex><\/p>\n
Trik spo\u010d\u00edva v tom, ako zostavi\u0165 aplik\u00e1ciu a spusti\u0165 ju lok\u00e1lne v tomto klasteri. Ak nevyd\u00e1te osobitn\u00e9 pokyny, Docker obraz sa bude zostavova\u0165 na va\u0161om po\u010d\u00edta\u010di, nie v klasteri.<\/p>\n
Aby Docker poslalo obraz do lok\u00e1lneho klastera Kubernetes, d\u00e1me docker-machine nasleduj\u00faci pr\u00edkaz:<\/p>\n
eval $(minikube docker-env)\n<\/code><\/pre>\n
\nTeraz m\u00f4\u017eeme zostavova\u0165 aplik\u00e1cie na lok\u00e1lnom klasteri Kubernetes.<\/p>\n
Ned\u00e1vajte pr\u00edstup kubectl v\u0161etk\u00fdm okolo<\/h2>\n
\nToto sa zd\u00e1 by\u0165 samozrejm\u00e9, ale ak viac t\u00edmov pou\u017e\u00edva jeden klaster pre svoje aplik\u00e1cie (na \u010do Kubernetes vznikol), nemali by ste jednoducho rozd\u00e1va\u0165 pr\u00edstupy. kubectl<\/code>Rad\u0161ej rozdelte t\u00edmy, pri\u010dom ka\u017edej pridel\u00edte vlastn\u00fd n\u00e1zov priestoru a obmedz\u00edte pr\u00edstup pomocou polit\u00edk RBAC.<\/p>\n
M\u00f4\u017eete sa zaobera\u0165 podrobn\u00fdm nastaven\u00edm pr\u00edstupov\u00fdch pr\u00e1v pre ka\u017ed\u00fd pod, vr\u00e1tane \u010d\u00edtania, vytv\u00e1rania, mazan\u00ed a in\u00fdch oper\u00e1ci\u00ed. Ale hlavn\u00e9 je obmedzi\u0165 pr\u00edstup k tajomstv\u00e1m, povoli\u0165 ho len administr\u00e1torom. Takto oddel\u00edme t\u00fdch, ktor\u00ed m\u00f4\u017eu spravova\u0165 klaster, od t\u00fdch, ktor\u00ed v \u0148om m\u00f4\u017eu len nasadi\u0165 aplik\u00e1cie.<\/p>\n
Spravujte rozpo\u010dty podov<\/h2>\n
\nAko zabezpe\u010di\u0165, aby aplik\u00e1cia v klasteri Kubernetes nemala \u017eiadne prestoje? PodDisruptionBudget a e\u0161te raz PodDisruptionBudget.<\/p>\n
Klastre sa pravidelne aktualizuj\u00fa a uzly sa vypr\u00e1zd\u0148uj\u00fa. Ni\u010d nestoj\u00ed na mieste, tak\u00e1 je realita. Do ka\u017ed\u00e9ho nasadenia s viac ako jedn\u00fdm in\u0161tancom by mal by\u0165 ur\u010dite zahrnut\u00fd PDB (PodDisruptionBudget). Vytv\u00e1ra sa v jednoduchom yaml s\u00fabore, ktor\u00fd sa aplikuje na klaster. Rozsah konkr\u00e9tneho PDB sa ur\u010duje pomocou selektorov \u0161t\u00edtkov.<\/p>\n
Pozn\u00e1mka:<\/strong> Rozpo\u010det PDB sa zoh\u013ead\u0148uje len pri reverzibilnom poru\u0161en\u00ed rozpo\u010dtu (voluntary disruption<\/a><\/noindex>). V situ\u00e1ci\u00e1ch ako s\u00fa hardv\u00e9rov\u00e9 zlyhania PDB nefunguje.<\/p>\n
Pr\u00edklad 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
\nDva z\u00e1kladn\u00e9 parametre s\u00fa matchLabels<\/code> a minAvailable<\/code>. V prvom parametri sa uv\u00e1dza, pre ktor\u00e9 aplik\u00e1cie plat\u00ed rozpo\u010det. Napr\u00edklad, ak m\u00e1m nasadenia s etiketami app: app-a<\/code> a app: app-b<\/code>, tento PDB sa bude uplat\u0148ova\u0165 len na prv\u00e9.<\/p>\n
Parameter minAvailable<\/code> sa zoh\u013ead\u0148uje pri vypr\u00e1zdnen\u00ed uzla. Napr\u00edklad v na\u0161om pr\u00edklade sa pri vypr\u00e1zd\u0148ovan\u00ed vyra\u010fuj\u00fa v\u0161etky in\u0161tancie app: app-a<\/code>, okrem dvoch.<\/p>\n
To umo\u017e\u0148uje kontrolova\u0165, ko\u013eko in\u0161tanci\u00ed aplik\u00e1cie m\u00e1 by\u0165 spusten\u00fdch v danom \u010dase.<\/p>\n
Monitoring stavu aplik\u00e1cie<\/h2>\n
\nTak\u00fdto monitoring je mo\u017en\u00e9 realizova\u0165 dvoma sp\u00f4sobmi: pomocou kontroly Readiness alebo Liveness.<\/p>\n
Prv\u00e1 kontrola (readiness) ur\u010duje pripravenos\u0165 kontajnera na pr\u00edjem prev\u00e1dzky.<\/p>\n
Druh\u00e1 (liveness) ukazuje, \u010di je kontajner funk\u010dn\u00fd, alebo ho treba re\u0161tartova\u0165.<\/p>\n
Prisl\u00fachaj\u00face konfigur\u00e1cie sa jednoducho pridaj\u00fa do yaml pre nasadenie. Tam m\u00f4\u017eete uvies\u0165 \u010dasov\u00e9 v\u00fdpadky, dobu oneskorenia a po\u010det opakovan\u00fdch pokusov. Podrobnej\u0161ie inform\u00e1cie o nich n\u00e1jdete v dokument\u00e1cii Kubernetes<\/a><\/noindex>.<\/p>\n
\u0160t\u00edtky v\u0161ade<\/h2>\n
\n\u0160t\u00edtky s\u00fa jedn\u00fdm z fundament\u00e1lnych pojmov v Kubernetes. Umo\u017e\u0148uj\u00fa objektom slobodne sa spoji\u0165 navz\u00e1jom a vytv\u00e1ra\u0165 po\u017eiadavky na z\u00e1klade \u0161t\u00edtkov. V Kubernetes je mo\u017en\u00e9 dokonca prejs\u0165 k klientovi a sledova\u0165 udalosti pod\u013ea konkr\u00e9tnych \u0161t\u00edtkov.<\/p>\n
Pomocou \u0161t\u00edtkov je mo\u017en\u00e9 spravi\u0165 takmer v\u0161etko, ale dobr\u00fdm pr\u00edkladom bude vytvorenie viacer\u00fdch prostred\u00ed na vykon\u00e1vanie programov v jednom klastri.<\/p>\n
Predpokladajme, \u017ee pou\u017e\u00edvate rovnak\u00fd klaster pre dev<\/code> a qa<\/code>. To znamen\u00e1, \u017ee m\u00f4\u017eete ma\u0165 aplik\u00e1ciu app-a<\/code>, ktor\u00e1 z\u00e1rove\u0148 funguje v oboch prostrediach qa<\/code> a dev<\/code>. V takom pr\u00edpade m\u00f4\u017eeme samostatne pristupova\u0165 k in\u0161tancii aplik\u00e1cie v konkr\u00e9tnom prostred\u00ed, zadan\u00edm pr\u00edslu\u0161n\u00e9ho parametra environment<\/code>. Napr\u00edklad, app: app-a<\/code> a environment: dev<\/code> pre jedno prostredie, a app: app-a<\/code> a environment: qa<\/code> pre druh\u00e9.<\/p>\n
To umo\u017e\u0148uje pristupova\u0165 k obom in\u0161tanci\u00e1m aplik\u00e1cie, napr\u00edklad s\u00fa\u010dasne vykon\u00e1va\u0165 testovanie.<\/p>\n
Urobte poriadok<\/h2>\n
\nKubernetes je ve\u013emi mocn\u00fd syst\u00e9m, ale ak\u00fdko\u013evek syst\u00e9m sa nakoniec m\u00f4\u017ee uviaznu\u0165 v ve\u013ekom mno\u017estve procesov. Kubelet sp\u00fa\u0161\u0165a v\u0161etky procesy a kontroly, ktor\u00e9 ste uviedli, ako aj svoje vlastn\u00e9.<\/p>\n
Samozrejme, jedna neudr\u017eiavan\u00e1 slu\u017eba nezastav\u00ed syst\u00e9m, a Kubernetes je p\u00f4vodne navrhnut\u00fd na \u0161k\u00e1lovanie. Ale ak namiesto jednej slu\u017eby vznikne mili\u00f3n, kubelet za\u010dne zlyh\u00e1va\u0165.<\/p>\n
Ak ste z nejak\u00e9ho d\u00f4vodu odstr\u00e1nili nasadenie (kontajner, obraz, \u010doko\u013evek), uistite sa, \u017ee je \u00faplne vy\u010disten\u00e9.<\/p>\n
Poznajte Go<\/h2>\n
\nNajd\u00f4le\u017eitej\u0161iu radu sme si nechali na koniec. Nau\u010dte sa programovac\u00ed jazyk Go.<\/p>\n
Kubernetes je vyvinut\u00fd v Go, v\u0161etky roz\u0161\u00edrenia s\u00fa nap\u00edsan\u00e9 v Go, a ofici\u00e1lne je podporovan\u00e1 klientsk\u00e1 kni\u017enica client-go.<\/p>\n
M\u00f4\u017ee sa pou\u017ei\u0165 na r\u00f4zne zauj\u00edmav\u00e9 veci. Napr\u00edklad na prisp\u00f4sobenie syst\u00e9mu Kubernetes pod\u013ea va\u0161ich predst\u00e1v. M\u00f4\u017eete pou\u017ei\u0165 vlastn\u00e9 programy na zhroma\u017e\u010fovanie \u00fadajov, nasadzovanie aplik\u00e1ci\u00ed alebo jednoduch\u00e9 \u010distenie kontajnerov.<\/p>\n
Nau\u010di\u0165 sa programovac\u00ed jazyk Go a ovl\u00e1dnu\u0165 client-go je sn\u00e1\u010f najd\u00f4le\u017eitej\u0161ia rada, ktor\u00fa m\u00f4\u017eeme da\u0165 za\u010d\u00ednaj\u00facim pou\u017e\u00edvate\u013eom Kubernetes.<\/p>\n
Prelo\u017eil Mail.ru Cloud Solutions<\/i><\/a><\/noindex><\/p>\n
\u010co \u010fal\u0161ie \u010d\u00edta\u0165<\/strong>:<\/p>\n
    \n
  1. Tri \u00farovne automatick\u00e9ho \u0161k\u00e1lovania v Kubernetes a ako ich efekt\u00edvne vyu\u017ei\u0165<\/a><\/noindex>.<\/li>\n
  2. Pracovn\u00e9 uzly Kubernetes: ve\u013ea mal\u00fdch alebo m\u00e1lo ve\u013ek\u00fdch<\/a><\/noindex>?<\/li>\n
  3. 25 u\u017eito\u010dn\u00fdch n\u00e1strojov na nasadenie a spr\u00e1vu Kubernetes<\/a><\/noindex>.<\/li>\n<\/ol>\n
    Zdroj: 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\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\udd47Najlep\u0161\u00edch 10 trikov a r\u00e1d pre Kubernetes | ProHoster","description":"Na internete je ve\u013ea referen\u010dnej literat\u00fary, ale.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/luchshie-10-hitrostej-i-sovetov-po-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\/sk\/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\/sk\/wp-json\/wp\/v2\/posts\/75425","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=75425"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/75425\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/75426"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=75425"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=75425"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=75425"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}