{"id":39249,"date":"2019-10-31T22:28:41","date_gmt":"2019-10-31T19:28:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/cse-kubernetes-dlya-teh-kto-v-vcloud-e\/"},"modified":"2019-10-31T22:28:41","modified_gmt":"2019-10-31T19:28:41","slug":"cse-kubernetes-dlya-teh-kto-v-vcloud-e","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","title":{"rendered":"CSE: Kubernetes a vCloud-ban l\u00e9v\u0151knek","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"CSE:
\nMindenkinek szia!<\/b><\/p>\n

\u00dagy alakult, hogy a kis csapatunk, nem mondan\u00e1m, hogy nemr\u00e9g, \u00e9s biztosan nem hirtelen, eljutott od\u00e1ig, hogy n\u00e9h\u00e1ny (a j\u00f6v\u0151ben pedig minden) term\u00e9ket \u00e1tvigyen a Kubernetesbe. <\/p>\n

Ennek sok oka volt, de a mi t\u00f6rt\u00e9net\u00fcnk nem err\u0151l sz\u00f3l.<\/p>\n

Infrastrukt\u00fara szempontj\u00e1b\u00f3l a v\u00e1laszt\u00e9kunk kicsi volt. vCloud Director \u00e9s vCloud Director. Az \u00fajat v\u00e1lasztottuk, \u00e9s \u00fagy d\u00f6nt\u00f6tt\u00fcnk, hogy elkezdj\u00fck. <\/p>\n

Miut\u00e1n ism\u00e9t lapozgattam a \u201eThe Hard Way\u201d-t, nagyon gyorsan arra a k\u00f6vetkeztet\u00e9sre jutottam, hogy egy alapvet\u0151 folyamatok, mint a deploy \u00e9s a m\u00e9retez\u00e9s, automatiz\u00e1l\u00e1s\u00e1ra szolg\u00e1l\u00f3 eszk\u00f6zre sz\u00fcks\u00e9g volna m\u00e1r tegnap. A Google m\u00e9lyrehat\u00f3 kutat\u00e1sa olyan term\u00e9ket hozott felsz\u00ednre, mint a VMware Container Service Extension (CSE) \u2014 egy ny\u00edlt forr\u00e1sk\u00f3d\u00fa term\u00e9k, amely lehet\u0151v\u00e9 teszi a k8s klaszterek automatikus l\u00e9trehoz\u00e1s\u00e1t \u00e9s m\u00e9retez\u00e9s\u00e9t a vCloud felhaszn\u00e1l\u00f3k sz\u00e1m\u00e1ra.
\n<\/a><\/noindex><\/p>\n

Disclaimer: A CSE-nek megvannak a maga korl\u00e1tai, de a c\u00e9ljainknak t\u00f6k\u00e9letesen megfelelt. Emellett a megold\u00e1st a felh\u0151szolg\u00e1ltat\u00f3nak is t\u00e1mogatnia kell, de mivel a kiszolg\u00e1l\u00f3 oldala is ny\u00edlt forr\u00e1sk\u00f3d\u00fa, k\u00e9rje a legk\u00f6zelebbi menedzsert\u0151l \ud83d\ude42<\/p><\/blockquote>\n

A haszn\u00e1lat elkezd\u00e9s\u00e9hez sz\u00fcks\u00e9g van egy adminisztr\u00e1tori fi\u00f3kra a vCloud szervezetben \u00e9s egy el\u0151re l\u00e9trehozott routed h\u00e1l\u00f3zatra a klaszter sz\u00e1m\u00e1ra (a telep\u00edt\u00e9si folyamat sor\u00e1n internet-hozz\u00e1f\u00e9r\u00e9sre van sz\u00fcks\u00e9g ebb\u0151l a h\u00e1l\u00f3zatb\u00f3l, ne felejtse el be\u00e1ll\u00edtani a t\u0171zfalat\/NAT-ot). Az c\u00edmz\u00e9s nem sz\u00e1m\u00edt. A p\u00e9ld\u00e1hoz vegy\u00fcnk egy 10.0.240.0\/24-es c\u00edmet.<\/p>\n

\"CSE:<\/p>\n

Mivel a klaszter l\u00e9trehoz\u00e1sa ut\u00e1n valamilyen m\u00f3don kezelni kell, javasolt egy VPN be\u00e1ll\u00edt\u00e1sa, amely k\u00f6zvetlen\u00fcl a l\u00e9trehozott h\u00e1l\u00f3zatra ir\u00e1ny\u00edt. Mi egy standard SSL-VPN-t haszn\u00e1lunk, amely a szervezet\u00fcnk Edge Gateway-j\u00e9n van be\u00e1ll\u00edtva.<\/p><\/blockquote>\n

Ezut\u00e1n telep\u00edten\u00fcnk kell a CSE klienst arra a helyre, ahonnan a k8s klaszterek kezel\u00e9s\u00e9t v\u00e9gezz\u00fck. Az \u00e9n esetemben ez egy munkahelyi laptop \u00e9s n\u00e9h\u00e1ny j\u00f3l elrejtett kont\u00e9ner, amelyek az automatiz\u00e1l\u00e1st ir\u00e1ny\u00edtj\u00e1k. <\/p>\n

A kliens 3.7.3 vagy \u00fajabb verzi\u00f3j\u00fa Python telep\u00edt\u00e9s\u00e9t ig\u00e9nyli, valamint a k\u00f6vetkez\u0151 modul telep\u00edt\u00e9s\u00e9t: vcd-cli<\/a><\/noindex>, ez\u00e9rt telep\u00edts\u00fck mindkett\u0151t.<\/p>\n

pip3 install vcd-cli\n\npip3 install container-service-extension\n<\/code><\/pre>\n
\nA telep\u00edt\u00e9s ut\u00e1n ellen\u0151rizz\u00fck a CSE verzi\u00f3j\u00e1t, \u00e9s a k\u00f6vetkez\u0151t kapjuk:<\/p>\n
# vcd cse version\nError: No such command \"cse\".\n<\/code><\/pre>\n
\nMegh\u00f6kkent\u0151, de jav\u00edthat\u00f3. Kider\u00fclt, hogy a CSE-t mint modult kell csatolni a vcd-cli-hoz.
\nEhhez el\u0151sz\u00f6r be kell jelentkezn\u00fcnk a vcd-cli-ba a szervezet\u00fcnkh\u00f6z:<\/p>\n
# vcd login MyCloud.provider.com org-dev admin\nPassword: \nadmin logged in, org: 'org-dev', vdc: 'org-dev_vDC01'\n<\/code><\/pre>\n
\nEzt k\u00f6vet\u0151en a vcd-cli l\u00e9trehoz egy konfigur\u00e1ci\u00f3s f\u00e1jlt. ~\/.vcd-cli\/profiles.yaml<\/i>
\nA f\u00e1jl v\u00e9g\u00e9re a k\u00f6vetkez\u0151t kell hozz\u00e1adnunk:<\/p>\n
extensions:\n  - container_service_extension.client.cse\n<\/code><\/pre>\n
\nEzut\u00e1n \u00fajra ellen\u0151rizz\u00fck:<\/p>\n
# vcd cse version\nCSE, Container Service Extension for VMware vCloud Director, version 2.5.0\n<\/code><\/pre>\n
\nA kliens telep\u00edt\u00e9si l\u00e9p\u00e9se befejez\u0151d\u00f6tt. Pr\u00f3b\u00e1ljuk meg telep\u00edteni az els\u0151 klasztert.
\nA CSE-nek t\u00f6bbf\u00e9le haszn\u00e1lati param\u00e9tere van, amelyeket meg lehet tekinteni. itt.<\/a><\/noindex><\/p>\n
El\u0151sz\u00f6r hozzunk l\u00e9tre kulcsokat, hogy jelsz\u00f3 n\u00e9lk\u00fcli hozz\u00e1f\u00e9r\u00e9st biztos\u00edtsunk a j\u00f6v\u0151beli klaszterhez. Ez fontos, mert alap\u00e9rtelmez\u00e9s szerint a jelszavas bejelentkez\u00e9s a csom\u00f3pontokra ki lesz kapcsolva, \u00e9s ha nem \u00e1ll\u00edtunk be kulcsokat, sok munk\u00e1t val\u00f3s\u00edthatunk meg a virtu\u00e1lis g\u00e9pek konzolj\u00e1n, ami nem t\u00fal k\u00e9nyelmes.<\/p>\n
# ssh-keygen\nGenerating public\/private rsa key pair.\nEnter file in which to save the key (\/root\/.ssh\/id_rsa): \nCreated directory '\/root\/.ssh'.\nEnter passphrase (empty for no passphrase): \nEnter same passphrase again: \nYour identification has been saved in \/root\/.ssh\/id_rsa.\nYour public key has been saved in \/root\/.ssh\/id_rsa.pub.\n<\/code><\/pre>\n
\nPr\u00f3b\u00e1ljuk elind\u00edtani a klaszter l\u00e9trehoz\u00e1s\u00e1t:<\/p>\n
vcd cse cluster create MyCluster --network k8s_cluster_net --ssh-key ~\/ .ssh\/id_rsa.pub --nodes 3 --enable-nfs<\/code><\/pre>\n
\nHa hib\u00e1t kapunk, Error: A munkamenet lej\u00e1rt, vagy a felhaszn\u00e1l\u00f3 nincs bejelentkezve. K\u00e9rj\u00fck, jelentkezzen be \u00fajra.<\/i> \u2014 ism\u00e9t jelentkezz\u00fcnk be vcd-cli seg\u00edts\u00e9g\u00e9vel a vCloud-ba, ahogy fentebb le\u00edrtuk, \u00e9s pr\u00f3b\u00e1lkozzunk \u00fajra.<\/p>\n
Ez\u00fattal minden rendben van, \u00e9s a klaszter l\u00e9trehoz\u00e1sa elindult.<\/p>\n
cluster operation: Klaszter vApp 'MyCluster' (38959587-54f4-4a49-8f2e-61c3a3e879e0) l\u00e9trehoz\u00e1sa a 'photon-v2_k8-1.12_weave-2.3.0' sablonb\u00f3l (1. verzi\u00f3)\n<\/code><\/pre>\n
\nA feladat befejez\u00e9s\u00e9hez k\u00f6r\u00fclbel\u00fcl 20 percre lesz sz\u00fcks\u00e9g, addig n\u00e9zz\u00fck \u00e1t az ind\u00edt\u00e1s f\u0151 param\u00e9tereit.<\/p>\n
\u2014h\u00e1l\u00f3zat \u2014 a kor\u00e1bban \u00e1ltalunk l\u00e9trehozott h\u00e1l\u00f3zat.
\n\u2014ssh-kulcs \u2014 az \u00e1ltalunk l\u00e9trehozott kulcsok, amelyeket a klaszter csom\u00f3pontjain r\u00f6gz\u00edtenek.
\n\u2014csom\u00f3pontok n \u2014 A klaszter Worker csom\u00f3pontjainak sz\u00e1ma. A Mester mindig egy lesz, ez a CSE korl\u00e1toz\u00e1sa.
\n\u2014nfs-enged\u00e9lyez\u00e9s \u2014 egy tov\u00e1bbi csom\u00f3pont l\u00e9trehoz\u00e1sa az NFS megoszt\u00e1shoz a tart\u00f3s k\u00f6tetek sz\u00e1m\u00e1ra. Ez egy kicsit bonyolult opci\u00f3, amelynek be\u00e1ll\u00edt\u00e1s\u00e1ra k\u00e9s\u0151bb visszat\u00e9r\u00fcnk.\n<\/p><\/blockquote>\n
 Ez id\u0151 alatt a vCloud-ban vizu\u00e1lisan nyomon k\u00f6vethetj\u00fck a klaszter l\u00e9trehoz\u00e1s\u00e1t.
\n\"CSE:
\n
\nAmint a klaszter l\u00e9trehoz\u00e1sa befejez\u0151d\u00f6tt, k\u00e9szen \u00e1ll a haszn\u00e1latra.<\/p>\n
Ellen\u0151rizz\u00fck a telep\u00edt\u00e9s helyess\u00e9g\u00e9t a k\u00f6vetkez\u0151 parancs seg\u00edts\u00e9g\u00e9vel: vcd cse cluster info MyCluster<\/i><\/p>\n
\"CSE:
\n
\nEzut\u00e1n meg kell szerezn\u00fcnk a klaszter konfigur\u00e1ci\u00f3j\u00e1t a haszn\u00e1lathoz. kubectl<\/i><\/p>\n
# vcd cse cluster config MyCluster > .\/.kube\/config\n<\/code><\/pre>\n
\n\u00c9s ezt m\u00e1r ezzel az eszk\u00f6zzel ellen\u0151rizhetj\u00fck a klaszter \u00e1llapot\u00e1t:<\/p>\n
\"CSE:
\n
\nEzen a ponton a klaszter k\u00f6r\u00fclbel\u00fcl m\u0171k\u00f6d\u0151k\u00e9pes, ha nem lenne a tart\u00f3s t\u00e1rol\u00f3k t\u00f6rt\u00e9nete. Mivel a vCloud-ban vagyunk, nem haszn\u00e1lhatjuk a vSphere szolg\u00e1ltat\u00f3t. Az opci\u00f3 \u2014nfs-enged\u00e9lyez\u00e9s<\/i> kipr\u00f3b\u00e1lta ezt a kellemetlens\u00e9get, de nem teljesen siker\u00fclt. K\u00e9zi finomhangol\u00e1sra van sz\u00fcks\u00e9g.<\/p>\n
El\u0151sz\u00f6r a csom\u00f3pontunknak l\u00e9tre kell hoznia egy k\u00fcl\u00f6n Independent lemezt a vCloud-ban. Ez garant\u00e1lja, hogy az adataink nem t\u0171nnek el a klaszterrel egy\u00fctt, ha az t\u00f6rl\u00e9sre ker\u00fcl. Tov\u00e1bb\u00e1 csatlakoztassuk a lemezt az NFS-hez. <\/p>\n
# vcd disk create nfs-shares-1 100g --description 'Kubernetes NFS shares'\n# vcd vapp attach mycluster nfsd-9604 nfs-shares-1\n<\/code><\/pre>\n
\nEzut\u00e1n SSH-n kereszt\u00fcl (val\u00f3ban, l\u00e9trehoztad a kulcsokat?) csatlakozunk az NFS csom\u00f3pontunkhoz, \u00e9s v\u00e9glegesen csatlakoztatjuk a lemezt:<\/p>\n
root@nfsd-9604:~# parted \/dev\/sdb\n(parted) mklabel gpt\nFigyelem: A megl\u00e9v\u0151 lemezc\u00edmke az \/dev\/sdb-n el fog veszni, \u00e9s az ezen a lemezen tal\u00e1lhat\u00f3 \u00f6sszes adat t\u00f6rl\u0151dik. Folytatni akarja?\nIgen\/Nem? igen\n(parted) unit GB\n(parted) mkpart primary 0 100\n(parted) print\nModell: VMware Virtual disk (scsi)\nLemez \/dev\/sdb: 100GB\nSektor m\u00e9ret (logikai\/fizikai): 512B\/512B\nPart\u00edci\u00f3s t\u00e1bla: gpt\nLemez z\u00e1szl\u00f3k:\n\nSz\u00e1m  Kezd  V\u00e9g  M\u00e9ret  F\u00e1jlrendszer  N\u00e9v  Z\u00e1szl\u00f3k\n 1      0.00GB  100GB  100GB               primary\n\n(parted) quit\nroot@nfsd-9604:~# mkfs -t ext4 \/dev\/sdb1\nF\u00e1jlrendszer l\u00e9trehoz\u00e1sa 24413696 4k blokkal \u00e9s 6111232 inode-dal\nF\u00e1jlrendszer UUID: 8622c0f5-4044-4ebf-95a5-0372256b34f0\nSuperblock ment\u00e9sek a k\u00f6vetkez\u0151 blokkokon:\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\n\t4096000, 7962624, 11239424, 20480000, 23887872\n\nCsoport t\u00e1bl\u00e1k allok\u00e1l\u00e1sa: k\u00e9sz\nInode t\u00e1bl\u00e1k \u00edr\u00e1sa: k\u00e9sz\nNapl\u00f3 l\u00e9trehoz\u00e1sa (32768 blokk): k\u00e9sz\nSuperblock \u00e9s f\u00e1jlrendszer k\u00f6nyvel\u00e9si inform\u00e1ci\u00f3k \u00edr\u00e1sa: k\u00e9sz\n<\/code><\/pre>\n
\nHozzunk l\u00e9tre egy k\u00f6nyvt\u00e1rat az adatok sz\u00e1m\u00e1ra, \u00e9s csatoljuk oda az \u00faj part\u00edci\u00f3t:<\/p>\n
mkdir \/export\necho '\/dev\/sdb1  \/export   ext4  defaults   0 0' >> \/etc\/fstab\nmount -a\n<\/code><\/pre>\n
\nHozzunk l\u00e9tre \u00f6t tesztpart\u00edci\u00f3t, \u00e9s osszuk meg \u0151ket a klaszter sz\u00e1m\u00e1ra:<\/p>\n
>cd \/export\n>mkdir vol1 vol2 vol3 vol4 vol5\n>vi \/etc\/exports\n#Ezt adjuk hozz\u00e1 a f\u00e1jl v\u00e9g\u00e9hez\n\/export\/vol1 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol2 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol3 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol4 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol5 *(rw,sync,no_root_squash,no_subtree_check)\n#:wq! ;)\n#Ezut\u00e1n export\u00e1ljuk a part\u00edci\u00f3kat\n>exportfs -r\n<\/code><\/pre>\n
\nMindezek ut\u00e1n l\u00e9trehozhatjuk a PV-t \u00e9s a PVC-t a klaszter\u00fcnkben k\u00f6r\u00fclbel\u00fcl \u00edgy:
\nPV:<\/p>\n
cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: PersistentVolume\nmetadata:\n  name: nfs-vol1\nspec:\n  capacity:\n    storage: 10Gi\n  accessModes:\n    - ReadWriteMany\n  nfs:\n    # Az NFS hoszt IP-c\u00edme, amelyhez kor\u00e1bban ssh-val csatlakoztunk.\n    server: 10.150.200.22\n    path: "\/export\/vol1"\nEOF\n<\/code><\/pre>\n
\nPVC:<\/p>\n
cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: nfs-pvc\nspec:\n  accessModes:\n    - ReadWriteMany\n  storageClassName: ""\n  resources:\n    requests:\n      storage: 10Gi\nEOF\n<\/code><\/pre>\n
\nEzzel a egy klaszter l\u00e9trehoz\u00e1s\u00e1nak t\u00f6rt\u00e9nete v\u00e9get \u00e9r, \u00e9s elkezd\u0151dik a l\u00e9trehozott klaszter \u00e9letciklusa. B\u00f3nuszk\u00e9nt \u2014 itt van m\u00e9g k\u00e9t hasznos CSE parancs, amelyek id\u0151nk\u00e9nt jelent\u0151s energi\u00e1t takar\u00edthatnak meg:<\/p>\n
#\u0423\u0432\u0435\u043b\u0438\u0447\u0438\u0432\u0430\u0435\u043c \u0440\u0430\u0437\u043c\u0435\u0440 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0434\u043e 8 \u0432\u043e\u0440\u043a\u0435\u0440 \u043d\u043e\u0434\n>cse cluster resize MyCluster --network k8s_cluster_net --nodes 8\n\n#\u0412\u044b\u0432\u043e\u0434\u0438\u043c \u043d\u0435\u043d\u0443\u0436\u043d\u044b\u0435 \u043d\u043e\u0434\u044b \u0438\u0437 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0441 \u0438\u0445 \u043f\u043e\u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c\n>vcd cse node delete MyCluster node-1a2v node-6685 --yes\n<\/code><\/pre>\n
\nMindenkinek k\u00f6sz\u00f6nj\u00fck az id\u0151t, ha k\u00e9rd\u00e9sei vannak \u2014 k\u00e9rdezzen a megjegyz\u00e9sekben.
\n
Forr\u00e1s: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0422\u0430\u043a \u0441\u043b\u043e\u0436\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430\u0448\u0430 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043a\u043e\u043c\u0430\u043d\u0434\u0430, \u043d\u0435 \u0441\u043a\u0430\u0437\u0430\u0442\u044c, \u0447\u0442\u043e\u0431\u044b \u043d\u0435\u0434\u0430\u0432\u043d\u043e, \u0438 \u0443\u0436 \u0442\u043e\u0447\u043d\u043e \u043d\u0435 \u0432\u043d\u0435\u0437\u0430\u043f\u043d\u043e, \u0434\u043e\u0440\u043e\u0441\u043b\u0430 \u0434\u043e \u043f\u0435\u0440\u0435\u043d\u043e\u0441\u0430 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 (\u0430 \u0432 \u043f\u0435\u0440\u0441\u043f\u0435\u043a\u0442\u0438\u0432\u0435 \u0438 \u0432\u0441\u0435\u0445) \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432 \u0432 Kubernetes. \u041f\u0440\u0438\u0447\u0438\u043d \u0442\u043e\u043c\u0443 \u0431\u044b\u043b\u043e \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e, \u043d\u043e \u043d\u0430\u0448\u0430 \u0438\u0441\u0442\u043e\u0440\u0438\u044f \u043d\u0435 \u043f\u0440\u043e \u0445\u043e\u043b\u0438\u0432\u0430\u0440. \u0418\u0437 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043d\u043e\u0439 \u043e\u0441\u043d\u043e\u0432\u044b \u0432\u044b\u0431\u043e\u0440 \u0443 \u043d\u0430\u0441 \u0431\u044b\u043b \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439. vCloud Director \u0438 vCloud Director. \u0412\u044b\u0431\u0440\u0430\u043b\u0438 \u0442\u043e\u0442, \u0447\u0442\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29455,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39249","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\udd47CSE: Kubernetes a vCloud-ban l\u00e9v\u0151knek | ProHoster","description":"\u00dcdv\u00f6zl\u00f6k mindenkit! \u00cdgy alakult, hogy a mi.","canonical_url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","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\udd47CSE: Kubernetes \u0434\u043b\u044f \u0442\u0435\u0445 \u043a\u0442\u043e \u0432 vCloud-\u0435 | ProHoster","og:description":"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0422\u0430\u043a \u0441\u043b\u043e\u0436\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430\u0448\u0430.","og:url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","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:28:41+00:00","article:modified_time":"2019-10-31T19:28:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39249","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-24 01:28:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:53:37","updated":"2026-01-24 01:28:19","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\/39249","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=39249"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/39249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media\/29455"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media?parent=39249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/categories?post=39249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/tags?post=39249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}