{"id":94739,"date":"2020-09-20T19:42:27","date_gmt":"2020-09-20T17:42:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes"},"modified":"2021-01-02T13:05:08","modified_gmt":"2021-01-02T11:05:08","slug":"prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","title":{"rendered":"Praktick\u00fd pr\u00edklad pripojenia \u00falo\u017eiska na b\u00e1ze Ceph do klastrov\u00e9ho Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Kontejnerov\u00e9 \u00falo\u017eisko interface (CSI) je jednotn\u00fd rozhran\u00ed pre interakciu Kubernetes a syst\u00e9mov \u00falo\u017eiska. Kr\u00e1tko o \u0148om sme u\u017e rozpr\u00e1vali<\/a><\/noindex>, a dnes podrobne presk\u00famame spojenie CSI a Ceph: uk\u00e1\u017eeme, ako pripoji\u0165 \u00falo\u017eisko Ceph<\/a><\/noindex> k klastru Kubernetes.
\nV \u010dl\u00e1nku s\u00fa prezentovan\u00e9 skuto\u010dn\u00e9, aj ke\u010f trochu zjednodu\u0161en\u00e9 pr\u00edklady na lep\u0161ie pochopenie. In\u0161tal\u00e1ciu a nastavenie klastra Ceph a Kubernetes neberieme do \u00favahy.<\/p>\n

Zauj\u00edma v\u00e1s, ako to funguje?<\/p>\n

\"Praktick\u00fd<\/p>\n

<\/a><\/noindex><\/p>\n

Tak\u017ee m\u00e1te po ruke klaster Kubernetes, nasaden\u00fd napr\u00edklad kubespray<\/a><\/noindex>. Ved\u013ea pracuje klaster Ceph \u2013 ten m\u00f4\u017eete tie\u017e nain\u0161talova\u0165, napr\u00edklad touto s\u00fapravou playbookov<\/a><\/noindex>. D\u00fafam, \u017ee netreba spom\u00edna\u0165, \u017ee pre produkciu by medzi nimi mala by\u0165 sie\u0165 s priepustnos\u0165ou najmenej 10 Gbit\/s.<\/p>\n

Ak m\u00e1te toto v\u0161etko, po\u010fme na to!<\/p>\n

Najprv sa prihl\u00e1sime na jednu z n\u00f3d klastra Ceph a over\u00edme, \u017ee je v\u0161etko v poriadku:<\/p>\n

ceph health\nceph -s<\/code><\/pre>\n
\u010ealej tu ihne\u010f vytvor\u00edme baz\u00e9n pre RBD disky:<\/p>\n
ceph osd pool create kube 32\nceph osd pool application enable kube rbd<\/code><\/pre>\n
Prejdeme do klastra Kubernetes. Tam najprv nain\u0161talujeme Ceph CSI ovl\u00e1da\u010d pre RBD. In\u0161tal\u00e1cia sa bude robi\u0165, ako sa patr\u00ed, prostredn\u00edctvom Helm.
\nPrid\u00e1me repozit\u00e1r s chartom, dostaneme s\u00fabor premenn\u00fdch chartu ceph-csi-rbd:<\/p>\n
helm repo add ceph-csi https:\/\/ceph.github.io\/csi-charts\nhelm inspect values ceph-csi\/ceph-csi-rbd > cephrbd.yml<\/code><\/pre>\n
Teraz je potrebn\u00e9 vyplni\u0165 s\u00fabor cephrbd.yml. Na to zist\u00edme ID klastra a IP adresy monitorov v Ceph:<\/p>\n
ceph fsid  # tak zist\u00edme clusterID\nceph mon dump  # a tak uvid\u00edme IP adresy monitorov<\/code><\/pre>\n
Z\u00edskan\u00e9 hodnoty vlo\u017e\u00edme do s\u00faboru cephrbd.yml. Z\u00e1rove\u0148 povol\u00edme vytv\u00e1ranie polit\u00edk PSP (Pod Security Policies). Mo\u017enosti v sekci\u00e1ch nodeplugin<\/strong> a provisioner<\/strong> u\u017e s\u00fa v s\u00fabore, daj\u00fa sa upravi\u0165 tak, ako je uveden\u00e9 ni\u017e\u0161ie:<\/p>\n
csiConfig:\n  - clusterID: \"bcd0d202-fba8-4352-b25d-75c89258d5ab\"\n    monitors:\n      - \"v2:172.18.8.5:3300\/0,v1:172.18.8.5:6789\/0\"\n      - \"v2:172.18.8.6:3300\/0,v1:172.18.8.6:6789\/0\"\n      - \"v2:172.18.8.7:3300\/0,v1:172.18.8.7:6789\/0\"\n\nnodeplugin:\n  podSecurityPolicy:\n    enabled: true\n\nprovisioner:\n  podSecurityPolicy:\n    enabled: true<\/code><\/pre>\n
\u010ealej, \u010do n\u00e1m ost\u00e1va, je nain\u0161talova\u0165 chart do klastra Kubernetes.<\/p>\n
helm upgrade -i ceph-csi-rbd ceph-csi\/ceph-csi-rbd -f cephrbd.yml -n ceph-csi-rbd --create-namespace<\/code><\/pre>\n
Skvele, RBD ovl\u00e1da\u010d funguje!
\nVytvorme v Kubernetes nov\u00fa StorageClass. Na to op\u00e4\u0165 bude potrebn\u00e9 trochu pracova\u0165 s Ceph.<\/p>\n
Vytvor\u00edme nov\u00e9ho pou\u017e\u00edvate\u013ea v Ceph a poskytneme mu pr\u00e1va na z\u00e1pis do baz\u00e9na kube<\/strong>:<\/p>\n
ceph auth get-or-create client.rbdkube mon 'profile rbd' osd 'profile rbd pool=kube'<\/code><\/pre>\n
A teraz sa pozrime na pr\u00edstupov\u00fd k\u013e\u00fa\u010d, v\u0161etko tam ist\u00e9:<\/p>\n
ceph auth get-key client.rbdkube<\/code><\/pre>\n
Pr\u00edkaz vyprodukuje nie\u010do podobn\u00e9:<\/p>\n
AQCO9NJbhYipKRAAMqZsnqqS\/T8OYQX20xIa9A==<\/code><\/pre>\n
Zaznamen\u00e1me t\u00fato hodnotu do Secret v klastri Kubernetes \u2013 tam, kde je potrebn\u00e1 userKey<\/strong>:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-rbd-secret\n  namespace: ceph-csi-rbd\nstringData:\n  # Hodnoty k\u013e\u00fa\u010dov zodpovedaj\u00fa pou\u017e\u00edvate\u013esk\u00e9mu menu a jeho k\u013e\u00fa\u010du, ako je uveden\u00e9 v\n  # klastre Ceph. ID u\u017e\u00edvate\u013ea by malo ma\u0165 pr\u00edstup k baz\u00e9nu,\n  # uveden\u00e9mu v storage class\n  userID: rbdkube\n  userKey:<\/code><\/pre>\n
A vytvor\u00edme n\u00e1\u0161 tajn\u00fd k\u00f3d:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
\u010ealej potrebujeme pribli\u017ene tak\u00fdto manifest StorageClass:<\/p>\n
---\napiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n   name: csi-rbd-sc\nprovisioner: rbd.csi.ceph.com\nparameters:\n   clusterID: \n   pool: kube\n\n   imageFeatures: layering\n\n   # Tieto tajn\u00e9 k\u00f3dy by mali obsahova\u0165 \u00fadaje na autoriz\u00e1ciu\n   # do v\u00e1\u0161ho baz\u00e9nu.\n   csi.storage.k8s.io\/provisioner-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/provisioner-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/controller-expand-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/controller-expand-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/node-stage-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/node-stage-secret-namespace: ceph-csi-rbd\n\n   csi.storage.k8s.io\/fstype: ext4\n\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - discard<\/code><\/pre>\n
Je potrebn\u00e9 vyplni\u0165 clusterID<\/strong>, ktor\u00fd sme u\u017e zistili pr\u00edkazom ceph fsid<\/em>, a aplikova\u0165 tento manifest v klastri Kubernetes:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Aby sme skontrolovali pr\u00e1cu klastrov v s\u00falade, vytvor\u00edme tak\u00fdto PVC (Persistent Volume Claim):<\/p>\n
apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: rbd-pvc\nspec:\n  accessModes:\n  - ReadWriteOnce\n  resources:\n    requests:\n      storage: 1Gi\n  storageClassName: csi-rbd-sc<\/code><\/pre>\n
Ihne\u010f sa pozrieme, ako Kubernetes vytvoril v Ceph po\u017eadovan\u00fd objem:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Vyzer\u00e1 to skvele! A ako to vyzer\u00e1 na strane Ceph?
\nZ\u00edskame zoznam objemov v baz\u00e9ne a prezerieme si inform\u00e1cie o na\u0161om objeme:<\/p>\n
rbd ls -p kube\nrbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653  # tu, samozrejme, bude in\u00e9 ID objemu, ktor\u00e9 vydala predch\u00e1dzaj\u00faca \u043a\u043e\u043c\u0430\u043d\u0434\u0430<\/code><\/pre>\n
Teraz sa po\u010fme pozrie\u0165, ako funguje zmena ve\u013ekosti objemu RBD.
\nZmen\u00edme ve\u013ekos\u0165 objemu v manifeste pvc.yaml na 2Gi a aplikujeme ho:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Po\u010dkajme, k\u00fdm sa zmeny prejavia, a pozrime sa znova na ve\u013ekos\u0165 objemu.<\/p>\n
rbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653\n\nkubectl get pv\nkubectl get pvc<\/code><\/pre>\n
Vid\u00edme, \u017ee ve\u013ekos\u0165 PVC sa nezmenila. Aby sme zistili, pre\u010do, m\u00f4\u017eeme po\u017eiada\u0165 Kubernetes o popis PVC vo form\u00e1te YAML:<\/p>\n
kubectl get pvc rbd-pvc -o yaml<\/code><\/pre>\n
A tu je probl\u00e9m:<\/p>\n
message: Waiting for user to (re-)start a pod to finish file system resize of volume on node. type: FileSystemResizePending<\/em><\/p>\n
To znamen\u00e1, \u017ee disk sa zv\u00e4\u010d\u0161il, ale s\u00faborov\u00fd syst\u00e9m na \u0148om nie.
\nAby sme zv\u00e4\u010d\u0161ili s\u00faborov\u00fd syst\u00e9m, mus\u00edme pripoji\u0165 objem. N\u00e1\u0161 vytvoren\u00fd PVC\/PV sa teraz nikam nepou\u017e\u00edva.<\/p>\n
M\u00f4\u017eeme vytvori\u0165 testovac\u00ed Pod, napr\u00edklad takto:<\/p>\n
---\napiVersion: v1\nkind: Pod\nmetadata:\n  name: csi-rbd-demo-pod\nspec:\n  containers:\n    - name: web-server\n      image: nginx:1.17.6\n      volumeMounts:\n        - name: mypvc\n          mountPath: \/data\n  volumes:\n    - name: mypvc\n      persistentVolumeClaim:\n        claimName: rbd-pvc\n        readOnly: false<\/code><\/pre>\n
A teraz sa pozrime na PVC:<\/p>\n
kubectl get pvc<\/code><\/pre>\n
Ve\u013ekos\u0165 sa zmenila, v\u0161etko je v poriadku.<\/p>\n
V prvej \u010dasti sme pracovali s blokov\u00fdm zariaden\u00edm RBD (\u010do je skratka pre Rados Block Device), ale to takto nem\u00f4\u017eeme robi\u0165, ak potrebujeme, aby r\u00f4zne mikroslu\u017eby s\u00fa\u010dasne pracovali s t\u00fdmto diskom. Pre pr\u00e1cu s s\u00fabormi, a nie s obrazom disku, je ove\u013ea lep\u0161ie pou\u017ei\u0165 CephFS.
\nNa pr\u00edklade klastra Ceph a Kubernetes nastav\u00edme CSI a ostatn\u00e9 potrebn\u00e9 entity pre pr\u00e1cu s CephFS.<\/p>\n
Z\u00edskame hodnoty z po\u017eadovan\u00e9ho nov\u00e9ho Helm grafu:<\/p>\n
helm inspect values ceph-csi\/ceph-csi-cephfs > cephfs.yml<\/code><\/pre>\n
Znova je potrebn\u00e9 vyplni\u0165 s\u00fabor cephfs.yml. Ako predt\u00fdm, pom\u00f4\u017eu pr\u00edkazy Ceph:<\/p>\n
ceph fsid\nceph mon dump<\/code><\/pre>\n
Vypl\u0148ujeme s\u00fabor s hodnotami pribli\u017ene takto:<\/p>\n
csiConfig:\n  - clusterID: \"bcd0d202-fba8-4352-b25d-75c89258d5ab\"\n    monitors:\n      - \"172.18.8.5:6789\"\n      - \"172.18.8.6:6789\"\n      - \"172.18.8.7:6789\"\n\nnodeplugin:\n  httpMetrics:\n    enabled: true\n    containerPort: 8091\n  podSecurityPolicy:\n    enabled: true\n\nprovisioner:\n  replicaCount: 1\n  podSecurityPolicy:\n    enabled: true<\/code><\/pre>\n
V\u0161imnite si, \u017ee adresy monitorov s\u00fa uveden\u00e9 v jednoduchom form\u00e1te adresa:port. Pre montovanie cephfs na uzle s\u00fa tieto adresy pred\u00e1van\u00e9 do jadrov\u00e9ho modulu, ktor\u00fd e\u0161te nevie pracova\u0165 s protokolom monitorov v2.
\nPort pre httpMetrics (kam sa bude Prometheus chodi\u0165 po metriky na monitorovanie) men\u00edme, aby nekolidoval s nginx-proxy, ktor\u00fd sa in\u0161taluje pomocou Kubespray. Mo\u017eno to nebudete potrebova\u0165.<\/p>\n
In\u0161talujeme Helm graf do klastra Kubernetes:<\/p>\n
helm upgrade -i ceph-csi-cephfs ceph-csi\/ceph-csi-cephfs -f cephfs.yml -n ceph-csi-cephfs --create-namespace<\/code><\/pre>\n
Prejdeme do \u00falo\u017eiska Ceph, aby sme tam vytvorili osobitn\u00e9ho pou\u017e\u00edvate\u013ea. V dokument\u00e1cii je uveden\u00e9, \u017ee provisioner pre CephFS potrebuje administr\u00e1torsk\u00e9 pr\u00edstupov\u00e9 pr\u00e1va k clustru. Ale vytvor\u00edme samostatn\u00e9ho pou\u017e\u00edvate\u013ea fs<\/em> s obmedzen\u00fdmi pr\u00e1vami:<\/p>\n
ceph auth get-or-create client.fs mon 'allow r' mgr 'allow rw' mds 'allow rws' osd 'allow rw pool=cephfs_data, allow rw pool=cephfs_metadata'<\/code><\/pre>\n
A hne\u010f sa pozrieme na jeho pr\u00edstupov\u00fd k\u013e\u00fa\u010d, ktor\u00fd vyu\u017eijeme nesk\u00f4r:<\/p>\n
ceph auth get-key client.fs<\/code><\/pre>\n
Vytvor\u00edme samostatn\u00e9 Secret a StorageClass.
\nNi\u010d nov\u00e9, u\u017e sme to videli na pr\u00edklade RBD:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-cephfs-secret\n  namespace: ceph-csi-cephfs\nstringData:\n  # Potrebn\u00e9 pre dynamicky vytvoren\u00e9 objemy\n  adminID: fs\n  adminKey:<\/code><\/pre>\n
Pou\u017e\u00edvame manifest:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
A teraz \u2013 samostatn\u00fd StorageClass:<\/p>\n
---\napiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n  name: csi-cephfs-sc\nprovisioner: cephfs.csi.ceph.com\nparameters:\n  clusterID: \n\n  # N\u00e1zov CephFS s\u00faborov\u00e9ho syst\u00e9mu, v ktorom bude vytvoren\u00fd objem\n  fsName: cephfs\n\n  # (volite\u013en\u00e9) Pool Ceph, v ktorom bud\u00fa ulo\u017een\u00e9 d\u00e1ta objemu\n  # pool: cephfs_data\n\n  # (volite\u013en\u00e9) Mo\u017enosti pripojenia oddelen\u00e9 \u010diarkou pre Ceph-fuse\n  # napr\u00edklad:\n  # fuseMountOptions: debug\n\n  # (volite\u013en\u00e9) Mo\u017enosti pripojenia CephFS pre jadro oddelen\u00e9 \u010diarkou\n  # Pozri man mount.ceph pre zoznam t\u00fdchto mo\u017enost\u00ed. Napr\u00edklad:\n  # kernelMountOptions: readdir_max_bytes=1048576,norbytes\n\n  # Tajomstv\u00e1 musia obsahova\u0165 pr\u00edstupov\u00e9 \u00fadaje pre administr\u00e1tora a\/alebo pou\u017e\u00edvate\u013ea Ceph.\n  csi.storage.k8s.io\/provisioner-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/provisioner-secret-namespace: ceph-csi-cephfs\n  csi.storage.k8s.io\/controller-expand-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/controller-expand-secret-namespace: ceph-csi-cephfs\n  csi.storage.k8s.io\/node-stage-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/node-stage-secret-namespace: ceph-csi-cephfs\n\n  # (volite\u013en\u00e9) Ovl\u00e1da\u010d m\u00f4\u017ee pou\u017e\u00edva\u0165 bu\u010f ceph-fuse (fuse), \n  # alebo ceph kernelclient (kernel).\n  # Ak nie je zadan\u00e9, bude sa pou\u017e\u00edva\u0165 predvolen\u00e9 pripojenie objemov,\n  # ktor\u00e9 sa ur\u010duje h\u013eadan\u00edm ceph-fuse a mount.ceph\n  # mounter: kernel\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - debug<\/code><\/pre>\n
Vypln\u00edme tu clusterID<\/strong> a aplikujeme v Kubernetes:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Kontrola<\/h2>\n
Na skontrolovanie, ako v predch\u00e1dzaj\u00facom pr\u00edklade, vytvor\u00edme PVC:<\/p>\n
---\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: csi-cephfs-pvc\nspec:\n  accessModes:\n    - ReadWriteMany\n  resources:\n    requests:\n      storage: 5Gi\n  storageClassName: csi-cephfs-sc<\/code><\/pre>\n
A skontrolujeme existenciu PVC\/PV:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Ak chcete vidie\u0165 s\u00fabory a adres\u00e1re v CephFS, m\u00f4\u017eete pripoji\u0165 tento s\u00faborov\u00fd syst\u00e9m niekam. Napr\u00edklad, ako je uveden\u00e9 ni\u017e\u0161ie.<\/p>\n
P\u00f4jdeme na jeden z uzlov klastru Ceph a vykon\u00e1me tieto kroky:<\/p>\n
# \u0422\u043e\u0447\u043a\u0430 \u043c\u043e\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f\nmkdir -p \/mnt\/cephfs\n\n# \u0421\u043e\u0437\u0434\u0430\u0451\u043c \u0444\u0430\u0439\u043b \u0441 \u043a\u043b\u044e\u0447\u043e\u043c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430\nceph auth get-key client.admin >\/etc\/ceph\/secret.key\n\n# \u0414\u043e\u0431\u0430\u0432\u043b\u044f\u0435\u043c \u0437\u0430\u043f\u0438\u0441\u044c \u0432 \/etc\/fstab\n# !! \u0418\u0437\u043c\u0435\u043d\u044f\u0435\u043c ip \u0430\u0434\u0440\u0435\u0441 \u043d\u0430 \u0430\u0434\u0440\u0435\u0441 \u043d\u0430\u0448\u0435\u0433\u043e \u0443\u0437\u043b\u0430\necho \"172.18.8.6:6789:\/ \/mnt\/cephfs ceph name=admin,secretfile=\/etc\/ceph\/secret.key,noatime,_netdev    0       2\" >> \/etc\/fstab\n\nmount \/mnt\/cephfs<\/code><\/pre>\n
Samozrejme, tak\u00e9to pripojenie FS na uzle Ceph je vhodn\u00e9 v\u00fdlu\u010dne na vzdel\u00e1vacie \u00fa\u010dely, \u010domu sa aj venujeme na na\u0161ich kurzoch Slurm<\/a><\/noindex>. Nemysl\u00edm si, \u017ee by to niekto robil v produkcii, riziko n\u00e1hodn\u00e9ho prep\u00edsania d\u00f4le\u017eit\u00fdch s\u00faborov je vysok\u00e9.<\/p>\n
A nakoniec si skontrolujme, ako je to v pr\u00edpade CephFS s menen\u00edm ve\u013ekosti objemu. Vraciam sa do Kubernetes a uprav\u00edm n\u00e1\u0161 manifest pre PVC \u2014 zv\u00e4\u010d\u0161\u00edme tam ve\u013ekos\u0165, napr\u00edklad na 7Gi.<\/p>\n
Aplikujeme upraven\u00fd s\u00fabor:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Pozrieme sa na pripojenom adres\u00e1ri, ako sa zmenila kv\u00f3ta:<\/p>\n
getfattr -n ceph.quota.max_bytes<\/code><\/pre>\n
Pre t\u00fato pr\u00edkaz m\u00f4\u017ee by\u0165 potrebn\u00e9 nain\u0161talova\u0165 do syst\u00e9mu bal\u00edk attr<\/strong>.<\/p>\n
O\u010di sa boja, ale ruky robia<\/h2>\n
Napriek tomu, \u017ee tieto zakl\u00ednadl\u00e1 a dlh\u00e9 manifesty YAML vyzeraj\u00fa na prv\u00fd poh\u013ead zlo\u017eito, \u0161tudenti Slovermu si s nimi v praxi celkom r\u00fdchlo poradia.
\nV tomto \u010dl\u00e1nku sme sa nep\u00fa\u0161\u0165ali do hlbok\u00fdch detailov \u2014 na to je ofici\u00e1lna dokument\u00e1cia. Ak v\u00e1s zauj\u00edmaj\u00fa podrobnosti o nastaven\u00ed \u00falo\u017eiska Ceph v spolupr\u00e1ci s Kubernetes klastrom, pom\u00f4\u017eu tieto odkazy:<\/p>\n
Z\u00e1kladn\u00e9 princ\u00edpy fungovania Kubernetes s objemami<\/a><\/noindex>
\nDokument\u00e1cia k RBD<\/a><\/noindex>
\nIntegr\u00e1cia RBD a Kubernetes z poh\u013eadu Ceph<\/a><\/noindex>
\nIntegr\u00e1cia RBD a Kubernetes z poh\u013eadu CSI<\/a><\/noindex>
\nV\u0161eobecn\u00e1 dokument\u00e1cia k CephFS<\/a><\/noindex>
\nIntegr\u00e1cia CephFS a Kubernetes z poh\u013eadu CSI<\/a><\/noindex><\/p>\n
Na kurze Sloverm Z\u00e1klady Kubernetes<\/a><\/noindex> m\u00f4\u017eete \u00eds\u0165 e\u0161te trochu \u010falej a nasadi\u0165 v Kubernetes skuto\u010dn\u00fa aplik\u00e1ciu, ktor\u00e1 bude pou\u017e\u00edva\u0165 CephFS ako \u00falo\u017eisko pre s\u00fabory. Pomocou GET\/POST po\u017eiadaviek budete m\u00f4c\u0165 s\u00fabory odosiela\u0165 a prij\u00edma\u0165 z Ceph.<\/p>\n
A ak v\u00e1s viac zauj\u00edma ukladanie d\u00e1t, prihl\u00e1ste sa na nov\u00fd kurz o Ceph<\/a><\/noindex>. K\u00fdm prebieha beta test, m\u00f4\u017eete z\u00edska\u0165 kurz so z\u013eavou a ovplyvni\u0165 jeho obsah.<\/p>\n
Autor \u010dl\u00e1nku: Alexander Shvalov, praktikuj\u00faci in\u017einier Southbridge<\/a><\/noindex>, Certified Kubernetes Administrator, autor a v\u00fdvoj\u00e1r kurzov Sloverm.<\/em><\/p>\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
Container Storage Interface (CSI) \u2014 \u044d\u0442\u043e \u0443\u043d\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f Kubernetes \u0438 \u0441\u0438\u0441\u0442\u0435\u043c \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445. \u0412\u043a\u0440\u0430\u0442\u0446\u0435 \u043e \u043d\u0451\u043c \u043c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u043b\u0438, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0435 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u0432\u044f\u0437\u043a\u0443 CSI \u0438 Ceph: \u043f\u043e\u043a\u0430\u0436\u0435\u043c, \u043a\u0430\u043a \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 Ceph \u043a \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0443 Kubernetes. \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u0440\u0435\u0430\u043b\u044c\u043d\u044b\u0435, \u0445\u043e\u0442\u044f \u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0443\u043f\u0440\u043e\u0449\u0451\u043d\u043d\u044b\u0435 \u0434\u043b\u044f \u0443\u0434\u043e\u0431\u0441\u0442\u0432\u0430 \u0432\u043e\u0441\u043f\u0440\u0438\u044f\u0442\u0438\u044f \u043f\u0440\u0438\u043c\u0435\u0440\u044b. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0443 \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Ceph \u0438 Kubernetes […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":94740,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-94739","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\udd47Praktick\u00fd pr\u00edklad pripojenia \u00falo\u017eiska zalo\u017een\u00e9ho na Ceph do klastru Kubernetes | ProHoster","description":"Container Storage Interface (CSI) je jednotn\u00fd rozhranie pre interakciu Kubernetes a syst\u00e9mov pre ukladanie d\u00e1t.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-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\u041f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440 \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u043d\u0430 \u0431\u0430\u0437\u0435 Ceph \u0432 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 Kubernetes | ProHoster","og:description":"Container Storage Interface (CSI) \u2014 \u044d\u0442\u043e \u0443\u043d\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f Kubernetes \u0438 \u0441\u0438\u0441\u0442\u0435\u043c \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-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-09-20T17:42:27+00:00","article:modified_time":"2021-01-02T11:05:08+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"94739","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","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 11:19:21","updated":"2022-09-30 10:03:10","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\/94739","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=94739"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/94739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/94740"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=94739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=94739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=94739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}