{"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\/et\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","title":{"rendered":"Praktiline n\u00e4ide Ceph-p\u00f5hise salvestuse \u00fchendamisest Kubernetes klastrisse","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Container Storage Interface (CSI) on \u00fchtne liides Kubernetes'e ja salvestuss\u00fcsteemide vahel. L\u00fchidalt oleme sellest juba r\u00e4\u00e4kinud, olen r\u00e4\u00e4kinud<\/a><\/noindex>, aga t\u00e4na vaatame l\u00e4hemalt CSI ja Ceph seost: n\u00e4itame, kuidas \u00fchendada Ceph salvestus<\/a><\/noindex> Kubernetes klastriga.
\nArtiklis on toodud reaalsed, kuigi veidi lihtsustatud n\u00e4ited mugavuse huvides. Ceph ja Kubernetes klastrite installimist ja seadistamist ei k\u00e4sitleta.<\/p>\n

Kas teil on huvi, kuidas see t\u00f6\u00f6tab?<\/p>\n

\"Praktiline<\/p>\n

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

Nii et teil on olemas Kubernetes klaster, mis on v\u00e4lja arendatud, n\u00e4iteks kubespray<\/a><\/noindex>. K\u00f5rval t\u00f6\u00f6tab Ceph klaster \u2014 selle v\u00f5ib samuti paigaldada, n\u00e4iteks selle playbookide komplekti<\/a><\/noindex>. Loodan, et ei pea mainima, et tootmisv\u00f5rgu vahel peab olema v\u00e4hemalt 10 Gbit\/s l\u00e4bilaskev\u00f5ime.<\/p>\n

Kui see k\u00f5ik on olemas, siis alustame!<\/p>\n

Esiteks logime Ceph klastrinoodi ja kontrollime, et k\u00f5ik on korras:<\/p>\n

ceph health\nceph -s<\/code><\/pre>\n
Seej\u00e4rel loome siinkohal RBD-diskide jaoks basseinid:<\/p>\n
ceph osd pool create kube 32\nceph osd pool application enable kube rbd<\/code><\/pre>\n
Liigume Kubernetes klastrisse. Seal paigaldame esmalt Ceph CSI draiveri RBD jaoks. Paigaldame, nagu tavaliselt, l\u00e4bi Helm.
\nLisame repositooriumi chart'iga, saades ceph-csi-rbd chart'i muutujate komplekti:<\/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
N\u00fc\u00fcd peame t\u00e4itma faili cephrbd.yml. Selleks saame clusterID ja Ceph'i monitoride IP-aadressid:<\/p>\n
ceph fsid  # nii saame teada clusterID\nceph mon dump  # ja nii n\u00e4eme monitoride IP-aadresse<\/code><\/pre>\n
Saadud v\u00e4\u00e4rtused paneme kirja faili cephrbd.yml. Samuti l\u00fclitame sisse PSP (Pod Security Policies) loomise. V\u00f5imalused sektsioonides nodeplugin<\/strong> ja provisioner<\/strong> on faili juba olemas, neid saab parandada nagu allpool n\u00e4idatud:<\/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
Edasi peame lihtsalt installima chart'i Kubernetes'i klastrisse.<\/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
Suurep\u00e4rane, RBD draiver t\u00f6\u00f6tab!
\nLoome Kubernetes'is uue StorageClass'i. Selleks on taas vajalik veidi t\u00f6\u00f6tada Ceph'iga.<\/p>\n
Loome Ceph'is uue kasutaja ja anname talle kirjutamis\u00f5igused basseinile kube<\/strong>:<\/p>\n
ceph auth get-or-create client.rbdkube mon 'profile rbd' osd 'profile rbd pool=kube'<\/code><\/pre>\n
Ja n\u00fc\u00fcd vaatame juurdep\u00e4\u00e4su v\u00f5tme seal samas:<\/p>\n
ceph auth get-key client.rbdkube<\/code><\/pre>\n
K\u00e4sk v\u00e4ljastab midagi sellist:<\/p>\n
AQCO9NJbhYipKRAAMqZsnqqS\/T8OYQX20xIa9A==<\/code><\/pre>\n
Kandideerime selle v\u00e4\u00e4rtuse Kubernetes'i klastris salajaseks \u2014 sinna, kus see vajalik on userKey<\/strong>:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-rbd-saladus\n  namespace: ceph-csi-rbd\nstringData:\n  # V\u00f5tme v\u00e4\u00e4rtused vastavad kasutajanimele ja tema v\u00f5tmele, nagu on m\u00e4rgitud\n  # Ceph klastris. Kasutaja ID peab omama juurdep\u00e4\u00e4su tiigile,\n  # mis on m\u00e4\u00e4ratletud salvestusklassides\n  userID: rbdkube\n  userKey:<\/code><\/pre>\n
Ja loome meie saladuse:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
Edasi vajame umbkaudu sellist StorageClass'i manifeste:<\/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   # Need saladused peaksid sisaldama autoriseerimise andmeid\n   # teie tiiki.\n   csi.storage.k8s.io\/provisioner-secret-name: csi-rbd-saladus\n   csi.storage.k8s.io\/provisioner-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/controller-expand-secret-name: csi-rbd-saladus\n   csi.storage.k8s.io\/controller-expand-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/node-stage-secret-name: csi-rbd-saladus\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
Peame t\u00e4itma clusterID<\/strong>, mille oleme juba saanud k\u00e4suga ceph fsid<\/em>, ja rakendame selle manifeste Kubernetes'i klastris:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Klastrite koost\u00f6\u00f6d kontrollimiseks loome sellise 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
Vaata n\u00fc\u00fcd, kuidas Kubernetes Cephis loodud mahuti v\u00e4lja n\u00e4eb:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Tundub, et k\u00f5ik on suurep\u00e4rane! Kuidas see Cephis v\u00e4lja n\u00e4eb?
\nSaame loendi mahutitest bassinis ja vaatame meie mahuti kohta teavet:<\/p>\n
rbd ls -p kube\nrbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653  # siin on muidugi teine mahuti ID, mille eelmine k\u00e4sk tagastas<\/code><\/pre>\n
N\u00fc\u00fcd vaatame, kuidas RBD mahuti suuruse muutmine t\u00f6\u00f6tab.
\nMuudame mahuti suurust failis pvc.yaml 2Gi peale ja rakendame selle:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Ootame, kuni muudatused j\u00f5ustuvad, ja vaatame veel kord mahuti suurust.<\/p>\n
rbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653\n\nkubectl get pv\nkubectl get pvc<\/code><\/pre>\n
N\u00e4eme, et PVC suurus ei ole muutunud. P\u00f5hjuse v\u00e4ljaselgitamiseks saab Kuberneteselt k\u00fcsida PVC kirjeldust YAML formaadis:<\/p>\n
kubectl get pvc rbd-pvc -o yaml<\/code><\/pre>\n
Ja siin on probleem:<\/p>\n
message: Ootame, et kasutaja (uuesti) k\u00e4ivitaks pod'i, et l\u00f5pule viia mahuti failis\u00fcsteemi suuruse muutmine s\u00f5lmes. type: FileSystemResizePending<\/em><\/p>\n
See t\u00e4hendab, et ketas on suurenenud, kuid sellel failis\u00fcsteem ei ole.
\nFailis\u00fcsteemi suurendamiseks tuleb mahutit manustada. Meil on loodud PVC\/PV, mis praegu ei ole kuidagi kasutuses.<\/p>\n
Saame luua proovipodi n\u00e4iteks nii:<\/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
N\u00fc\u00fcd vaatame PVC-d:<\/p>\n
kubectl get pvc<\/code><\/pre>\n
Suurus on muutunud, k\u00f5ik on korras.<\/p>\n
Esimeses osas t\u00f6\u00f6tasime RBD plokiseadmestikuga (mis t\u00e4hendab Rados Block Device), kuid see ei sobi, kui erinevad mikroteenused peavad samaaegselt selle kettaga t\u00f6\u00f6tama. Failidega, mitte ketta pildiga, sobib palju paremini CephFS.
\nSeadistame CSI ja teised vajalikud \u00fcksused CephFS-i t\u00f6\u00f6ks Ceph ja Kubernetes klastrite n\u00e4itel.<\/p>\n
Saame vajalikud v\u00e4\u00e4rtused uuest Helm-graafikust:<\/p>\n
helm inspect values ceph-csi\/ceph-csi-cephfs > cephfs.yml<\/code><\/pre>\n
Peame uuesti t\u00e4itma faili cephfs.yml. Nagu varem, aitavad Ceph k\u00e4sud:<\/p>\n
ceph fsid\nceph mon dump<\/code><\/pre>\n
T\u00e4idame v\u00e4\u00e4rtustega faili umbes nii:<\/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
P\u00f6\u00f6rake t\u00e4helepanu, et monitoride aadressid on esitatud lihtsa kujuga address:port. CephFS-i mountimiseks s\u00f5lmes edastatakse need aadressid tuumamoodulile, mis ei oska veel kasutada monitori protokolli v2.
\nMuudame httpMetrics'i porti (kuhu Prometheus kogub andmeid j\u00e4lgimiseks), et v\u00e4ltida konflikti nginx-proxy'ga, mis installitakse Kubespray'ga. Teile ei pruugi see vajalik olla.<\/p>\n
Paigaldame Helm-chart'i Kubernetes klastrisse:<\/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
Liigume Ceph andmem\u00e4lusse, et seal luua eraldi kasutaja. Dokumentatsioonis on m\u00e4rgitud, et CephFS-i provisioneerijatel on vaja klastrihalduse \u00f5igus. Kuid loome eraldi kasutaja fs<\/em> piiratud \u00f5igustega:<\/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
Ja vaatame kohe tema juurdep\u00e4\u00e4suv\u00f5tit, see tuleb meile hiljem kasuks:<\/p>\n
ceph auth get-key client.fs<\/code><\/pre>\n
Loome eraldi Secret'i ja StorageClass'i.
\nMidagi uut pole, oleme seda juba RBD n\u00e4itel n\u00e4inud:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-cephfs-secret\n  namespace: ceph-csi-cephfs\nstringData:\n  # Vajalik d\u00fcnaamiliselt loodud mahtude jaoks\n  adminID: fs\n  adminKey:<\/code><\/pre>\n
Rakendame manifesti:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
Ja n\u00fc\u00fcd \u2013 eraldi 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  # CephFS failiss\u00fcsteemi nimi, kus maht luuakse\n  fsName: cephfs\n\n  # (valikuline) Ceph puu, kus mahu andmed salvestatakse\n  # pool: cephfs_data\n\n  # (valikuline) Ceph-fuse jaoks eraldatud komadega paigaldusvalikud\n  # n\u00e4iteks:\n  # fuseMountOptions: debug\n\n  # (valikuline) CephFS tuuma paigaldusvalikud\n  # Vaata man mount.ceph, et n\u00e4ha nende valikute loendit. N\u00e4iteks:\n  # kernelMountOptions: readdir_max_bytes=1048576,norbytes\n\n  # Saladused peavad sisaldama administraatori ja\/v\u00f5i Ceph'i kasutaja juurdep\u00e4\u00e4se.\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  # (valikuline) Juht edastab v\u00f5ib kasutada kas ceph-fuse (fuse)\n  # v\u00f5i ceph kernelclient (kernel).\n  # Kui ei ole m\u00e4\u00e4ratud, kasutatakse vaikimisi mahtude paigaldamist,\n  # mis m\u00e4\u00e4ratakse ceph-fuse ja mount.ceph otsimise kaudu\n  # mounter: kernel\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - debug<\/code><\/pre>\n
T\u00e4idame selle siia clusterID<\/strong> ja rakendame Kuberneteses:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Kontrollimine<\/h2>\n
Kuna kontrollime, kuidas nagu eelmisel juhul, loome 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
Ja kontrollime PVC\/PV olemasolu:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Kui soovite vaadata faile ja kaustu CephFS-is, saate selle failis\u00fcsteemi kuhugi mountida. N\u00e4iteks, nagu allpool n\u00e4idatud.<\/p>\n
L\u00e4heme \u00fchte Ceph-klastri s\u00f5lmest ja teeme j\u00e4rgmised toimingud:<\/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
Loomulikult sobib selline FS mountimine Ceph-i s\u00f5lmes ainult \u00f5ppe eesm\u00e4rkidel, millega me tegeleme meie Sl\u00f5rm kursustel.<\/a><\/noindex>Ei usu, et keegi selle tootmises teeks, sest on suur risk kogemata kustutada olulisi faile.<\/p>\n
Ja l\u00f5puks vaatame, kuidas on CephFS-i puhul suuruse muutmisega. Naaseme Kubernetesesse ja redigeerime oma PVC manifeste \u2014 suurendame seal suurust n\u00e4iteks kuni 7Gi.<\/p>\n
Rakendame redigeeritud faili:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Vaadake mountitud kataloogis, kuidas on kvota muutunud:<\/p>\n
getfattr -n ceph.quota.max_bytes<\/code><\/pre>\n
Selle k\u00e4su t\u00f6\u00f6ks v\u00f5ite vajada s\u00fcsteemis paketti attr<\/strong>.<\/p>\n
Silmad kardavad, aga k\u00e4ed teevad<\/h2>\n
Esialgu v\u00f5ivad k\u00f5ik need manused ja pikad YAML manifestid tunduda keerulised, kuid praktikas saavad Sl\u00ebrmi \u00f5pilased nendega \u00fcsna kiiresti hakkama.
\nSelles artiklis me ei s\u00fcvene s\u00fcvitsi \u2013 selleks on ametlik dokumentatsioon. Kui teid huvitavad Ceph\u2019i salvestus\u00e4ri seadistamise \u00fcksikasjad koos Kubernetes klastriga, siis aitavad j\u00e4rgmised lingid:<\/p>\n
Kubernetes'i ja mahutite \u00fcldp\u00f5him\u00f5tted<\/a><\/noindex>
\nRBD dokumentatsioon<\/a><\/noindex>
\nRBD ja Kubernetes'i integreerimine Ceph'i vaatenurgast<\/a><\/noindex>
\nRBD ja Kubernetes'i integreerimine CSI vaatenurgast<\/a><\/noindex>
\nCephFS \u00fcldine dokumentatsioon<\/a><\/noindex>
\nCephFS ja Kubernetes'i integreerimine CSI vaatenurgast<\/a><\/noindex><\/p>\n
Sl\u00ebrm kursusel Kubernetes Baas<\/a><\/noindex> v\u00f5ite minna veelgi kaugemale ja k\u00e4ivitada Kubernetes'is t\u00f5eline rakendus, mis kasutab CephFS-i failide salvestamiseks. GET\/POST p\u00e4ringute kaudu saate faile edastada ja neid Ceph'ist hankida.<\/p>\n
Kui teid huvitab rohkem andmete salvestamine, siis registreeruge uuele Ceph kursusele<\/a><\/noindex>. Seni kui k\u00e4ib beetatestimine, saab kursust soodushinnaga ja m\u00f5jutada selle sisu.<\/p>\n
Artikli autor: Aleksandr Shvalov, praktiseeriv insener Southbridge<\/a><\/noindex>, Certified Kubernetes Administrator, Sl\u00ebrm kursuste autor ja arendaja.<\/em><\/p>\n
Allikas: 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\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\udd47Praktiline n\u00e4ide Ceph-p\u00f5hise salvestuse \u00fchendamisest Kubernetes'i klastrisse | ProHoster","description":"Container Storage Interface (CSI) on ain \u00fchtne liidese Kubernetes'i ja andmehoidlate s\u00fcsteemide vahel. Oleme sellest juba l\u00fchidalt r\u00e4\u00e4kinud, kuid t\u00e4na vaatleme l\u00e4hemalt CSI ja Cephi sidet: n\u00e4itame, kuidas \u00fchendada Cephi salvestus Kubernetes'i klastriga. Artiklis on toodud reaalsed, kuigi veidi lihtsustatud n\u00e4ited mugavuse huvides. Cephi ja Kubernetes'i klastrite paigaldamine ja seadistamine.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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. \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","og:url":"https:\/\/prohoster.info\/et\/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"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/94739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=94739"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/94739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/94740"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=94739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=94739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=94739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}