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

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

Det har blivit s\u00e5 att v\u00e5rt lilla team, inte s\u00e4rskilt nyligen och definitivt inte pl\u00f6tsligt, har vuxit till sig f\u00f6r att flytta vissa (och i framtiden alla) produkter till Kubernetes. <\/p>\n

Det fanns m\u00e5nga orsaker till detta, men v\u00e5r historia handlar inte om kontroverser.<\/p>\n

Som infrastruktur hade vi ett begr\u00e4nsat val. vCloud Director och vCloud Director. Vi valde den nyare versionen och best\u00e4mde oss f\u00f6r att b\u00f6rja. <\/p>\n

N\u00e4r jag \u00e5terigen bl\u00e4ddrade igenom \"The Hard Way\" kom jag snabbt fram till att ett verktyg f\u00f6r att automatisera \u00e5tminstone grundl\u00e4ggande processer, som deployment och sizing, beh\u00f6vdes ig\u00e5r. En djupdykning i Google visade ett produkt som VMware Container Service Extension (CSE) \u2013 en \u00f6ppen k\u00e4llkodsprodukt som m\u00f6jligg\u00f6r automatisering av skapandet och sizing av k8s-kluster f\u00f6r dem som \u00e4r i vCloud.
\n<\/a><\/noindex><\/p>\n

Disclaimer: CSE har sina begr\u00e4nsningar, men f\u00f6r v\u00e5ra \u00e4ndam\u00e5l passade den perfekt. L\u00f6sningen m\u00e5ste ocks\u00e5 st\u00f6djas av molnleverant\u00f6ren, men eftersom serverdelen ocks\u00e5 \u00e4r \u00f6ppen k\u00e4llkod, beg\u00e4r dess existens hos den n\u00e4rmaste managern \ud83d\ude42<\/p><\/blockquote>\n

F\u00f6r att b\u00f6rja anv\u00e4nda det kr\u00e4vs ett administrat\u00f6rskonto inom vCloud-organisationen och en f\u00f6rhandskonfigurerad routed-n\u00e4tverk f\u00f6r klustret (under deployment-processen kr\u00e4vs internet\u00e5tkomst fr\u00e5n detta n\u00e4tverk, gl\u00f6m inte att st\u00e4lla in brandv\u00e4gg\/NAT). Adresseringen \u00e4r inte viktig. I detta exempel tar vi 10.0.240.0\/24.<\/p>\n

\"CSE:<\/p>\n

Eftersom klustret m\u00e5ste hanteras efter skapandet rekommenderas en VPN med routing till det skapade n\u00e4tverket. Vi anv\u00e4nder en standard SSL-VPN, konfigurerad p\u00e5 Edge Gateway i v\u00e5r organisation.<\/p><\/blockquote>\n

D\u00e4refter m\u00e5ste CSE-klienten installeras d\u00e4rifr\u00e5n kluster k8s kommer att hanteras. I mitt fall \u00e4r detta en arbetslaptop och ett par v\u00e4l g\u00f6mda containrar som kontrollerar automatiseringen. <\/p>\n

Klienten kr\u00e4ver att Python version 3.7.3 eller h\u00f6gre och modulen vcd-cli<\/a><\/noindex>m\u00e5ste vara installerade, s\u00e5 vi installerar b\u00e5da.<\/p>\n

pip3 install vcd-cli\n\npip3 install container-service-extension\n<\/code><\/pre>\n
\nEfter installationen kontrollerar vi versionen av CSE och f\u00e5r f\u00f6ljande:<\/p>\n
# vcd cse version\nError: No such command \"cse\".\n<\/code><\/pre>\n
\n\u00d6verraskande, men fixbart. Det visade sig att CSE m\u00e5ste kopplas som en modul till vcd-cli.
\nF\u00f6r detta m\u00e5ste vi f\u00f6rst logga in p\u00e5 vcd-cli i v\u00e5r 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
\nEfter detta kommer vcd-cli att skapa en konfigurationsfil ~\/ .vcd-cli \/ profiles.yaml<\/i>
\nI slutet av denna fil m\u00e5ste f\u00f6ljande l\u00e4ggas till:<\/p>\n
extensions:\n  - container_service_extension.client.cse\n<\/code><\/pre>\n
\nD\u00e4refter kontrollerar vi igen:<\/p>\n
# vcd cse version\nCSE, Container Service Extension for VMware vCloud Director, version 2.5.0\n<\/code><\/pre>\n
\nKlientinstallationen \u00e4r avslutad. L\u00e5t oss f\u00f6rs\u00f6ka implementera den f\u00f6rsta klustret.
\nCSE har flera upps\u00e4ttningar av anv\u00e4ndarinst\u00e4llningar, som alla kan ses. h\u00e4r.<\/a><\/noindex><\/p>\n
F\u00f6rst skapar vi nycklar f\u00f6r l\u00f6senordsfri \u00e5tkomst till det framtida klustret. Det h\u00e4r \u00e4r viktigt eftersom l\u00f6senordsinloggning till noderna \u00e4r inaktiverad som standard, och om nycklarna inte anges kan man beh\u00f6va g\u00f6ra mycket arbete via konsolen f\u00f6r de virtuella maskinerna, vilket inte \u00e4r s\u00e4rskilt bekv\u00e4mt.<\/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 f\u00f6rs\u00f6ker starta skapandet av klustret:<\/p>\n
vcd cse cluster create MyCluster --network k8s_cluster_net --ssh-key ~\/ssh\/id_rsa.pub --nodes 3 --enable-nfs<\/code><\/pre>\n
\nOm vi f\u00e5r ett fel: Fel: Sessionen har l\u00f6pt ut eller anv\u00e4ndaren \u00e4r inte inloggad. V\u00e4nligen logga in igen.<\/i> \u2014 logga in vcd-cli i vCloud igen som beskrivs ovan och f\u00f6rs\u00f6k p\u00e5 nytt.<\/p>\n
Den h\u00e4r g\u00e5ngen gick allt bra och skapandet av klustret startade.<\/p>\n
klusteroperation: Skapar kluster vApp 'MyCluster' (38959587-54f4-4a49-8f2e-61c3a3e879e0) fr\u00e5n mall 'photon-v2_k8-1.12_weave-2.3.0' (revision 1)\n<\/code><\/pre>\n
\nDet tar cirka 20 minuter att slutf\u00f6ra uppgiften, under tiden g\u00e5r vi igenom de grundl\u00e4ggande startparametrarna.<\/p>\n
\u2014n\u00e4tverk \u2014 det n\u00e4tverk vi skapade tidigare.
\n\u2014ssh-key \u2014 de nycklar vi skapade som kommer att skrivas in p\u00e5 klustrets noder.
\n\u2014noder n \u2014 Antalet Worker-noder i klustret. Det kommer alltid att finnas en Master, detta \u00e4r en begr\u00e4nsning av CSE.
\n\u2014enable-nfs \u2014 skapa en extra nod f\u00f6r NFS-delning under persistent volumes. Det \u00e4r en lite mer komplicerad funktion, vi kommer att \u00e5terkomma till vad den g\u00f6r senare.\n<\/p><\/blockquote>\n
 Under tiden kan vi visuellt observera skapandet av klustret i vCloud.
\n\"CSE:
\n
\nS\u00e5 snart klustrets skapande \u00e4r klart \u00e4r det redo f\u00f6r anv\u00e4ndning.<\/p>\n
L\u00e5t oss kontrollera korrektheten i distributionen med kommandot: vcd cse cluster info MyCluster<\/i><\/p>\n
\"CSE:
\n
\nD\u00e4refter m\u00e5ste vi f\u00e5 klusterkonfigurationen f\u00f6r anv\u00e4ndning. kubectl<\/i><\/p>\n
# vcd cse cluster config MyCluster > .\/.kube\/config\n<\/code><\/pre>\n
\nOch vi kan kontrollera klustrets tillst\u00e5nd med hj\u00e4lp av den:<\/p>\n
\"CSE:
\n
\nVid detta tillf\u00e4lle kan klustret anses vara villkorligt aktivt, om det inte vore f\u00f6r historien om best\u00e4ndiga volymer. Eftersom vi \u00e4r i vCloud g\u00e5r det inte att anv\u00e4nda vSphere-leverant\u00f6ren. Alternativet \u2014enable-nfs<\/i> \u00e4r avsedd att mildra detta problem, men det har inte helt lyckats. Manuell efterkonfiguration kr\u00e4vs.<\/p>\n
F\u00f6rst m\u00e5ste v\u00e5r nod skapa en separat oberoende disk i vCloud. Detta garanterar att v\u00e5ra data inte f\u00f6rsvinner tillsammans med klustret om det raderas. Vi kopplar ocks\u00e5 disken till 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
\nEfter detta g\u00e5r vi via ssh (du har v\u00e4l skapat nycklar?) till v\u00e5r NFS-nod och kopplar slutgiltigt disken:<\/p>\n
root@nfsd-9604:~# parted \/dev\/sdb\n(parted) mklabel gpt\nVarning: Den befintliga disklabeln p\u00e5 \/dev\/sdb kommer att raderas och all data p\u00e5 denna disk kommer att g\u00e5 f\u00f6rlorad. Vill du forts\u00e4tta?\nJa\/Nej? ja\n(parted) unit GB\n(parted) mkpart primary 0 100\n(parted) print\nModell: VMware Virtual disk (scsi)\nDisk \/dev\/sdb: 100GB\nSektorstorlek (logisk\/fysisk): 512B\/512B\nPartitionstabell: gpt\nDiskflaggor:\n\nNummer  Start   Slut    Storlek   Filtyp  Namn     Flaggor\n 1      0.00GB  100GB  100GB               primary\n\n(parted) quit\nroot@nfsd-9604:~# mkfs -t ext4 \/dev\/sdb1\nSkapar filsystem med 24413696 4k block och 6111232 inoder\nFilsystem UUID: 8622c0f5-4044-4ebf-95a5-0372256b34f0\nSuperblock backups lagrade p\u00e5 block:\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\n\t4096000, 7962624, 11239424, 20480000, 23887872\n\nAllokerar grupptabeller: klart\nSkriver inodetabeller: klart\nSkapar journal (32768 block): klart\nSkriver superblock och filsystemredovisningsinformation: klart\n<\/code><\/pre>\n
\nSkapar en katalog f\u00f6r data och monterar den nya partitionen d\u00e4r:<\/p>\n
mkdir \/export\necho '\/dev\/sdb1  \/export   ext4  defaults   0 0' >> \/etc\/fstab\nmount -a\n<\/code><\/pre>\n
\nL\u00e5t oss skapa fem testpartitioner och dela dem f\u00f6r klustret:<\/p>\n
>cd \/export\n>mkdir vol1 vol2 vol3 vol4 vol5\n>vi \/etc\/exports\n#L\u00e4gg till detta i slutet 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#D\u00e4refter - exportera partitionerna\n>exportfs -r\n<\/code><\/pre>\n
\nEfter all denna magi kan vi skapa PV och PVC i v\u00e5rt kluster p\u00e5 ungef\u00e4r detta s\u00e4tt:
\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    # Samma IP som NFS-v\u00e4rden vi ssh:ade till tidigare.\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
\nP\u00e5 detta s\u00e4tt avslutas historien om skapandet av ett kluster och historien om dess livscykel b\u00f6rjar. Som en bonus - ytterligare tv\u00e5 anv\u00e4ndbara CSE-kommandon som ibland kan spara resurser ganska bra eller inte:<\/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
\nTack f\u00f6r er tid, om ni har fr\u00e5gor - st\u00e4ll dem i kommentarerna.
\n
K\u00e4lla: 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 f\u00f6r dem som \u00e4r i vCloud | ProHoster","description":"Hej alla! Det har blivit s\u00e5 att v\u00e5r.","canonical_url":"https:\/\/prohoster.info\/sv\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sv_SE","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\/sv\/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\/sv\/wp-json\/wp\/v2\/posts\/39249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/comments?post=39249"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/posts\/39249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/media\/29455"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/media?parent=39249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/categories?post=39249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/tags?post=39249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}