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

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

Det er lykkedes, at vores lille team, ikke direkte nyt, og bestemt ikke pludseligt, er vokset til at flytte nogle (og i perspektiv alle) produkter til Kubernetes. <\/p>\n

Der var mange grunde til dette, men vores historie handler ikke om debat.<\/p>\n

Vi havde et begr\u00e6nset valg i forhold til infrastrukturelle grundlag. vCloud Director og vCloud Director. Vi valgte den nyeste og besluttede at starte. <\/p>\n

N\u00e5r jeg endnu engang har bladret igennem \"The Hard Way\", kom jeg hurtigt frem til, at et v\u00e6rkt\u00f8j til automatisering af i det mindste grundl\u00e6ggende processer, s\u00e5som deployment og sizing, var n\u00f8dvendigt allerede i g\u00e5r. En dybdeg\u00e5ende s\u00f8gning i Google afsl\u00f8rede et produkt kaldet VMware Container Service Extension (CSE) \u2014 et open source-produkt, der muligg\u00f8r automatisering af oprettelsen og sizing af k8s-klynger for dem, der er i vCloud.
\n<\/a><\/noindex><\/p>\n

Disclaimer: CSE har sine begr\u00e6nsninger, men til vores form\u00e5l var det perfekt. L\u00f8sningen skal ogs\u00e5 st\u00f8tte af cloud-udbyderen, men eftersom serverdelen ogs\u00e5 er open source, skal du kr\u00e6ve, at den er tilg\u00e6ngelig hos den n\u00e6rmeste leder \ud83d\ude42<\/p><\/blockquote>\n

For at komme i gang kr\u00e6ves en administrator konto i vCloud-organisationen og et p\u00e5 forh\u00e5nd oprettet routed-netv\u00e6rk til klyngen (under deployment er der behov for internetadgang fra dette netv\u00e6rk, glem ikke at konfigurere Firewall\/NAT). Adresseringen er ikke vigtig. I dette eksempel tager vi 10.0.240.0\/24.<\/p>\n

\"CSE:<\/p>\n

Da klusteret efter oprettelsen skal kunne administreres, anbefales det at have en VPN med routing til det oprettede netv\u00e6rk. Vi bruger en standard SSL-VPN, der er konfigureret p\u00e5 Edge Gateway i vores organisation.<\/p><\/blockquote>\n

Dern\u00e6st skal CSE-klienten installeres p\u00e5 den enhed, der skal administrere k8s-klyngerne. I mit tilf\u00e6lde er det en arbejdscomputer og et par godt gemte containere, der styrer automatiseringen. <\/p>\n

Klienten kr\u00e6ver, at Python version 3.7.3 eller h\u00f8jere er installeret, samt modulet vcd-cli<\/a><\/noindex>, s\u00e5 vi installerer begge dele.<\/p>\n

pip3 install vcd-cli\n\npip3 install container-service-extension\n<\/code><\/pre>\n
\nEfter installationen tjekker vi CSE-versionen og f\u00e5r f\u00f8lgende:<\/p>\n
# vcd cse version\nError: No such command \"cse\".\n<\/code><\/pre>\n
\nOverraskende, men til at rette. Det viste sig, at CSE skal tilknyttes som et modul til vcd-cli.
\nFor at g\u00f8re dette skal vcd-cli f\u00f8rst logge ind i vores organisation:<\/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
\nHerefter vil vcd-cli oprette en konfigurationsfil ~\/.vcd-cli\/profiles.yaml<\/i>
\nI slutningen af denne fil skal f\u00f8lgende tilf\u00f8jes:<\/p>\n
extensions:\n  - container_service_extension.client.cse\n<\/code><\/pre>\n
\nHerefter tjekker vi igen:<\/p>\n
# vcd cse version\nCSE, Container Service Extension for VMware vCloud Director, version 2.5.0\n<\/code><\/pre>\n
\nKlientinstallationen er afsluttet. Lad os pr\u00f8ve at implementere den f\u00f8rste klynge.
\nCSE har flere s\u00e6t parametre, som alle kan ses her.<\/a><\/noindex><\/p>\n
For at starte skal vi oprette n\u00f8gler til adgang uden adgangskode til den kommende klynge. Dette punkt er vigtigt, da adgang med adgangskode til noderne som standard vil v\u00e6re deaktiveret, og hvis n\u00f8glerne ikke er angivet, kan man f\u00e5 meget arbejde gennem de virtuelle maskiners konsoller, hvilket ikke er s\u00e6rlig 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
\nLad os pr\u00f8ve at starte oprettelsen af 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 fejl Error: Session has expired or user not logged in. Please re-login.<\/i> \u2014 logger vi igen ind med vcd-cli i vCloud som beskrevet ovenfor og pr\u00f8ver igen.<\/p>\n
Denne gang er alt i orden, og opgaven med at oprette klyngen er startet.<\/p>\n
cluster operation: Creating cluster vApp 'MyCluster' (38959587-54f4-4a49-8f2e-61c3a3e879e0) from template 'photon-v2_k8-1.12_weave-2.3.0' (revision 1)\n<\/code><\/pre>\n
\nDet vil tage cirka 20 minutter at afslutte opgaven, imens ser vi n\u00e6rmere p\u00e5 de vigtigste startparametre.<\/p>\n
\u2014netv\u00e6rk \u2014 det netv\u00e6rk, vi tidligere har oprettet.
\n\u2014ssh-key \u2014 de n\u00f8gler, vi har oprettet, som vil blive gemt p\u00e5 klusterets noder.
\n\u2014nodes n \u2014 Antallet af Worker-noder i klustret. Der vil altid v\u00e6re \u00e9n Master, dette er en begr\u00e6nsning i CSE.
\n\u2014enable-nfs \u2014 opret en ekstra node til NFS-deling til persistent volumes. En lidt avanceret mulighed, vi vender tilbage til, n\u00e5r vi f\u00e5r lidt mere indsigt i, hvad den g\u00f8r.\n<\/p><\/blockquote>\n
 I mellemtiden kan man visuelt overv\u00e5ge oprettelsen af klyngen i vCloud.
\n\"CSE:
\n
\nN\u00e5r opgaven med at oprette klyngen er afsluttet, er den klar til brug.<\/p>\n
Lad os kontrollere korrektheden af deployment med kommandoen vcd cse cluster info MyCluster<\/i><\/p>\n
\"CSE:
\n
\nDerefter skal vi have konfigurationen af klyngen til brug kubectl<\/i><\/p>\n
# vcd cse cluster config MyCluster > .\/.kube\/config\n<\/code><\/pre>\n
\nOg vi kan kontrollere tilstanden af klyngen allerede ved hj\u00e6lp af den:<\/p>\n
\"CSE:
\n
\nI dette \u00f8jeblik kan klyngen betragtes som betinget funktionsdygtig, hvis det ikke havde v\u00e6ret for historien med persistent volumes. Da vi er i vCloud, kan vi ikke bruge vSphere Provider. Indstillingen \u2014enable-nfs<\/i> er designet til at afb\u00f8de denne ulempe, men det lykkedes ikke helt. Der kr\u00e6ves manuel finjustering.<\/p>\n
For at starte skal vores node oprette en separat Independent disk i vCloud. Dette garanterer, at vores data ikke forsvinder sammen med klyngen, skulle den blive slettet. Derudover tilslutter vi 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
\nDerefter g\u00e5r vi via ssh (du har virkelig oprettet n\u00f8glerne?) til vores NFS-node og tilslutter disken endeligt:<\/p>\n
root@nfsd-9604:~# parted \/dev\/sdb\n(parted) mklabel gpt\nAdvarsel: Den eksisterende disklabel p\u00e5 \/dev\/sdb vil blive \u00f8delagt, og alle data p\u00e5\ndenne disk vil g\u00e5 tabt. Vil du forts\u00e6tte?\nJa\/Nej? ja\n(parted) unit GB\n(parted) mkpart primary 0 100\n(parted) print\nModel: VMware Virtual disk (scsi)\nDisk \/dev\/sdb: 100GB\nSektorst\u00f8rrelse (logisk\/fysisk): 512B\/512B\nPartitionsskema: gpt\nDiskflags:\n\nNummer  Start   Slut    St\u00f8rrelse  Filsystem  Navn     Flags\n 1      0.00GB  100GB  100GB               primary\n\n(parted) quit\nroot@nfsd-9604:~# mkfs -t ext4 \/dev\/sdb1\nOpretter filsystem med 24413696 4k blokke og 6111232 inode\nFilsystem UUID: 8622c0f5-4044-4ebf-95a5-0372256b34f0\nSuperblok backups gemt p\u00e5 blokke:\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\n\t4096000, 7962624, 11239424, 20480000, 23887872\n\nAllokerer gruppetabeller: f\u00e6rdig\nSkriver inode-tabeller: f\u00e6rdig\nOpretter journal (32768 blokke): f\u00e6rdig\nSkriver superblokke og filsystemregnskabsinformation: f\u00e6rdig\n<\/code><\/pre>\n
\nVi opretter en mappe til data og monterer den nye partition der:<\/p>\n
mkdir \/export\necho '\/dev\/sdb1  \/export   ext4  defaults   0 0' >> \/etc\/fstab\nmount -a\n<\/code><\/pre>\n
\nLad os oprette fem testpartitioner og dele dem ud til klyngen:<\/p>\n
>cd \/export\n>mkdir vol1 vol2 vol3 vol4 vol5\n>vi \/etc\/exports\n#Tilf\u00f8j dette til slutningen af 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#Herefter - eksporterer vi partitionerne\n>exportfs -r\n<\/code><\/pre>\n
\nEfter al denne magi kan vi oprette PV og PVC i vores klynge cirka s\u00e5dan her:
\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-v\u00e6rten, vi ssh'ede 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
\nHer slutter historien om oprettelsen af en klynge, og historien om dens livscyklus begynder. Som bonus kommer der to nyttige CSE-kommandoer, der nogle gange kan spare ressourcer:<\/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
\nTak for jeres tid, hvis der er sp\u00f8rgsm\u00e5l, s\u00e5 sp\u00f8rg endelig i kommentarerne.
\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 der er i vCloud | ProHoster","description":"Hej alle! Det er s\u00e5dan, at vores.","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","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\/da\/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\/da\/wp-json\/wp\/v2\/posts\/39249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=39249"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/39249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/29455"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=39249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=39249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=39249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}