{"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\/no\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","title":{"rendered":"CSE: Kubernetes for de som er i vCloud","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"CSE:
\nHei alle sammen!<\/b><\/p>\n

Det har utviklet seg slik at v\u00e5rt lille team, ikke akkurat nylig, men absolutt ikke plutselig, har n\u00e5dd et punkt hvor vi vurderer \u00e5 migrere noen (og p\u00e5 sikt alle) produkter til Kubernetes. <\/p>\n

Det var mange grunner til dette, men v\u00e5r historie handler ikke om debatten.<\/p>\n

Valgene vi hadde for infrastrukturbasen var ikke mange. vCloud Director og vCloud Director. Vi valgte den nyeste og bestemte oss for \u00e5 begynne. <\/p>\n

Ved \u00e5 bla gjennom 'The Hard Way' kom jeg raskt til konklusjonen om at et verkt\u00f8y for \u00e5 automatisere minst grunnleggende prosesser, som distribusjon og sizing, var n\u00f8dvendig for lenge siden. En dypere utforskning p\u00e5 Google avsl\u00f8rte et produkt som VMware Container Service Extension (CSE) \u2013 et opensourceprodukt som gj\u00f8r det mulig \u00e5 automatisere opprettelsen og sizing av k8s-klynger for de som er i vCloud.
\n<\/a><\/noindex><\/p>\n

Ansvarsfraskrivelse: CSE har sine begrensninger, men for v\u00e5re form\u00e5l passet det perfekt. L\u00f8sningen m\u00e5 ogs\u00e5 st\u00f8ttes av skyl\u00f8sningen, men siden serverdelen ogs\u00e5 er open-source, b\u00f8r du kreve at det er tilgjengelig fra n\u00e6rmeste leder \ud83d\ude42<\/p><\/blockquote>\n

For \u00e5 begynne \u00e5 bruke det, er en administrator-konto i vCloud-organisasjonen n\u00f8dvendig og et p\u00e5 forh\u00e5nd opprettet routed-nettverk for klyngen (under distribusjonen er tilgang til internett fra dette nettverket n\u00f8dvendig, s\u00e5 husk \u00e5 konfigurere brannmur\/NAT). Adresseringen spiller ingen rolle. I dette eksempelet bruker vi 10.0.240.0\/24.<\/p>\n

\"CSE:<\/p>\n

Siden klyngen m\u00e5 kunne h\u00e5ndteres etter opprettelsen, anbefales det \u00e5 ha en VPN med ruting til det opprettede nettverket. Vi bruker en standard SSL-VPN konfigurert p\u00e5 Edge Gateway av v\u00e5r organisasjon.<\/p><\/blockquote>\n

Deretter m\u00e5 CSE-klienten installeres derfra hvor k8s-klyngene skal h\u00e5ndteres. I mitt tilfelle er dette min arbeidslaptop og et par godt skjulte containere som h\u00e5ndterer automatiseringen. <\/p>\n

Klienten krever installert Python versjon 3.7.3 eller h\u00f8yere, samt den installerte modulet vcd-cli<\/a><\/noindex>, s\u00e5 vi instiller begge deler.<\/p>\n

pip3 install vcd-cli\n\npip3 install container-service-extension\n<\/code><\/pre>\n
\nEtter installasjonen sjekker vi versjonen av CSE og f\u00e5r f\u00f8lgende:<\/p>\n
# vcd cse version\nError: No such command \"cse\".\n<\/code><\/pre>\n
\nOverraskende, men fikserbart. Det viste seg at CSE m\u00e5 kobles som et modul til vcd-cli.
\nFor dette m\u00e5 vi f\u00f8rst logge inn i vcd-cli i v\u00e5r organisasjon:<\/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
\nEtter dette vil vcd-cli opprette en konfigurasjonsfil ~\/.vcd-cli\/profiles.yaml<\/i>
\nP\u00e5 slutten m\u00e5 f\u00f8lgende legges til:<\/p>\n
extensions:\n  - container_service_extension.client.cse\n<\/code><\/pre>\n
\nDeretter sjekker vi igjen:<\/p>\n
# vcd cse version\nCSE, Container Service Extension for VMware vCloud Director, version 2.5.0\n<\/code><\/pre>\n
\nKlientinstallasjonssteget er fullf\u00f8rt. La oss pr\u00f8ve \u00e5 sette opp den f\u00f8rste klyngen.
\nCSE har flere sett med parametre for bruk, som alle kan sees. her.<\/a><\/noindex><\/p>\n
F\u00f8r vi begynner, m\u00e5 vi lage n\u00f8kler for passordfri tilgang til den fremtidige klyngen. Dette er viktig, da passordinnlogging til nodene som standard vil v\u00e6re deaktivert, og hvis vi ikke setter opp n\u00f8klene, kan vi f\u00e5 mye arbeid fra konsollen til de virtuelle maskinene, noe som ikke er spesielt praktisk.<\/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
\nVi pr\u00f8ver \u00e5 starte opprettingen av klyngen:<\/p>\n
vcd cse cluster create MyCluster --network k8s_cluster_net --ssh-key ~\/.ssh\/id_rsa.pub --nodes 3 --enable-nfs<\/code><\/pre>\n
\nHvis vi f\u00e5r en feil, Error: Session has expired or user not logged in. Please re-login.<\/i> \u2013 logger vi inn p\u00e5 vcd-cli i vCloud som beskrevet ovenfor og gjentar fors\u00f8ket.<\/p>\n
Denne gangen gikk alt bra, og opprettelsen av klyngen ble startet.<\/p>\n
cluster operation: Oppretter klynge vApp 'MyCluster' (38959587-54f4-4a49-8f2e-61c3a3e879e0) fra malen 'photon-v2_k8-1.12_weave-2.3.0' (revisjon 1)\n<\/code><\/pre>\n
\nDet vil ta omtrent 20 minutter \u00e5 fullf\u00f8re oppgaven, i mellomtiden skal vi g\u00e5 gjennom de viktigste startparameterne.<\/p>\n
\u2014network \u2014 det opprettede nettverket v\u00e5rt.
\n\u2014ssh-key \u2014 de opprettede n\u00f8klene som vil bli lagret p\u00e5 klusterets noder.
\n\u2014nodes n \u2014 Antall Worker-noder i klusteret. Det vil alltid v\u00e6re \u00e9n Master, dette er en begrensning i CSE.
\n\u2014enable-nfs \u2014 opprett en ekstra node for NFS-delingen til vedvarende volumer. En litt pedantisk opsjon, som vi vil g\u00e5 dypere inn i senere.\n<\/p><\/blockquote>\n
 I mellomtiden kan vi visuelt overv\u00e5ke opprettingen av klyngen i vCloud.
\n\"CSE:
\n
\nS\u00e5 snart opprettelsen av klyngen er fullf\u00f8rt, er den klar til bruk.<\/p>\n
La oss sjekke riktigheten av distribusjonen med kommandoen vcd cse cluster info MyCluster<\/i><\/p>\n
\"CSE:
\n
\nDeretter m\u00e5 vi f\u00e5 klyngekonfigurasjonen for bruk. kubectl<\/i><\/p>\n
# vcd cse cluster config MyCluster > .\/.kube\/config\n<\/code><\/pre>\n
\nOg vi kan allerede sjekke tilstanden til klyngen ved hjelp av den:<\/p>\n
\"CSE:
\n
\nI dette \u00f8yeblikket kan vi anse klyngen som betinget operativ, dersom det ikke hadde v\u00e6rt for problemet med vedvarende volumer. Siden vi er i vCloud, kan vi ikke bruke vSphere-leverand\u00f8ren. Alternativet \u2014enable-nfs<\/i> er ment \u00e5 glatte over denne ulempen, men det ble ikke helt vellykket. Manuell fininnstilling er n\u00f8dvendig.<\/p>\n
For \u00e5 begynne, m\u00e5 vi opprette en egen uavhengig disk i vCloud for noden v\u00e5r. Dette garanterer at dataene v\u00e5re ikke forsvinner sammen med klyngen, hvis den blir slettet. Vi skal ogs\u00e5 koble disken til NFS. <\/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
\nEtter dette, g\u00e5r vi via ssh (dere opprettet vel n\u00f8kler?) til NFS-noden v\u00e5r og kobler disken til:<\/p>\n
root@nfsd-9604:~# parted \/dev\/sdb\n(parted) mklabel gpt\nWarning: The existing disk label on \/dev\/sdb will be destroyed and all data on\nthis disk will be lost. Do you want to continue?\nYes\/No? yes\n(parted) unit GB\n(parted) mkpart primary 0 100\n(parted) print\nModel: VMware Virtual disk (scsi)\nDisk \/dev\/sdb: 100GB\nSector size (logical\/physical): 512B\/512B\nPartition Table: gpt\nDisk Flags:\n\nNumber  Start   End    Size   File system  Name     Flags\n 1      0.00GB  100GB  100GB               primary\n\n(parted) quit\nroot@nfsd-9604:~# mkfs -t ext4 \/dev\/sdb1\nCreating filesystem with 24413696 4k blocks and 6111232 inodes\nFilesystem UUID: 8622c0f5-4044-4ebf-95a5-0372256b34f0\nSuperblock backups stored on blocks:\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\n\t4096000, 7962624, 11239424, 20480000, 23887872\n\nAllocating group tables: done\nWriting inode tables: done\nCreating journal (32768 blocks): done\nWriting superblocks and filesystem accounting information: done\n<\/code><\/pre>\n
\nOpprett en katalog for dataene og mount den nye partisjonen:<\/p>\n
mkdir \/export\necho '\/dev\/sdb1  \/export   ext4  defaults   0 0' >> \/etc\/fstab\nmount -a\n<\/code><\/pre>\n
\nLa oss opprette fem testpartisjoner og dele dem for klyngen:<\/p>\n
>cd \/export\n>mkdir vol1 vol2 vol3 vol4 vol5\n>vi \/etc\/exports\n#Legg dette til slutten av filen\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#Deretter eksporterer vi partisjonene\n>exportfs -r\n<\/code><\/pre>\n
\nEtter all denne magien, kan vi opprette PV og PVC i klyngen v\u00e5r p\u00e5 denne m\u00e5ten:
\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    # Samme IP som NFS-verten vi ssh'et til tidligere.\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
\nSlik avsluttes historien om opprettelsen av en klynge og historien om dens livssyklus begynner. Som en bonus \u2014 her er to nyttige CSE-kommandoer som noen ganger kan spare ressurser:<\/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
\nTakk for at dere tok dere tid, hvis dere har sp\u00f8rsm\u00e5l \u2014 still dem i kommentarfeltet.
\n
Kilde: 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 for dem som er i vCloud | ProHoster","description":"Hei alle sammen! S\u00e5nn har det blitt at v\u00e5r.","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","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\/no\/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\/no\/wp-json\/wp\/v2\/posts\/39249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=39249"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/39249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/29455"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=39249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=39249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=39249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}