{"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\/hr\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","title":{"rendered":"Prakti\u010dni primjer povezivanja Ceph pohrane u Kubernetes klaster","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Container Storage Interface (CSI) je jedinstveni su\u010delje za interakciju izme\u0111u Kubernetesa i sustava za pohranu podataka. O njemu smo ve\u0107 ukratko govorili<\/a><\/noindex>, a danas \u0107emo detaljnije razmotriti vezu izme\u0111u CSI i Cepha: pokazat \u0107emo kako povezati Ceph pohranu<\/a><\/noindex> s Kubernetes klasterom.
\nU \u010dlanku su navedeni stvarni, iako malo pojednostavljeni primjeri za bolju razumljivost. Instalaciju i konfiguraciju Ceph i Kubernetes klastera ne razmatramo.<\/p>\n

Zanima vas kako to funkcionira?<\/p>\n

\"Prakti\u010dni<\/p>\n

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

Dakle, imate pod rukom Kubernetes klaster, razvedren, na primjer, kubespray<\/a><\/noindex>. U blizini radi Ceph klaster \u2014 tako\u0111er ga mo\u017eete instalirati, na primjer, ovim setom playbookova<\/a><\/noindex>. Nadam se da nije potrebno spominjati da izme\u0111u njih mora biti mre\u017ea s propusnom mo\u0107i od najmanje 10 Gb\/s.<\/p>\n

Ako sve to imate, idemo!<\/p>\n

Prvo \u0107emo oti\u0107i na jedan od nodova Ceph klastera i provjeriti je li sve u redu:<\/p>\n

ceph health\nceph -s<\/code><\/pre>\n
Zatim \u0107emo odmah stvoriti bazen za RBD diskove:<\/p>\n
ceph osd pool create kube 32\nceph osd pool application enable kube rbd<\/code><\/pre>\n
Prelazimo u Kubernetes klaster. Tamo \u0107emo prvo instalirati Ceph CSI drajver za RBD. Instalirat \u0107emo ga, kao \u0161to i odgovara, putem Helma.
\nDodajemo repozitorij s chartom i dobivamo set varijabli chart-a 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
Sada trebate ispuniti datoteku cephrbd.yml. Za to saznajemo ID klastera i IP adrese monitora u Ceph-u:<\/p>\n
ceph fsid  # ovako saznajemo clusterID\nceph mon dump  # a ovako vidimo IP adrese monitora<\/code><\/pre>\n
Dobivene vrijednosti unosimo u datoteku cephrbd.yml. Usput uklju\u010dujemo stvaranje politika PSP (Pod Security Policies). Opcije u odjeljcima nodeplugin<\/strong> i provisioner<\/strong> ve\u0107 postoje u datoteci, one se mogu ispraviti na na\u010din kako je prikazano u nastavku:<\/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
Sve \u0161to nam preostaje jest instalirati chart u Kubernetes klaster.<\/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
Odli\u010dno, RBD drajver radi!
\nStvorimo novu StorageClass u Kubernetesu. Za to \u0107e ponovno biti potrebno malo raditi s Ceph-om.<\/p>\n
Stvaramo novog korisnika u Ceph-u i dodjeljujemo mu prava za pisanje u bazen kube<\/strong>:<\/p>\n
ceph auth get-or-create client.rbdkube mon 'profile rbd' osd 'profile rbd pool=kube'<\/code><\/pre>\n
A sada pogledajmo pristupni klju\u010d na istom mjestu:<\/p>\n
ceph auth get-key client.rbdkube<\/code><\/pre>\n
Komanda \u0107e izdati ne\u0161to poput ovoga:<\/p>\n
AQCO9NJbhYipKRAAMqZsnqqS\/T8OYQX20xIa9A==<\/code><\/pre>\n
Unesemo ovu vrijednost u tajnu u Kubernetes klasteru \u2014 tamo gdje je potrebna userKey<\/strong>:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-rbd-secret\n  namespace: ceph-csi-rbd\nstringData:\n  # Vrijednosti klju\u010deva odgovaraju imenu korisnika i njegovom klju\u010du, kako je navedeno u\n  # Ceph klasteru. ID korisnika mora imati pristup bazenu,\n  # navedenom u storage class\n  userID: rbdkube\n  userKey:<\/code><\/pre>\n
I kreiramo na\u0161u tajnu:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
Sljede\u0107i nam je potreban otprilike ovakav 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   # Ove tajne moraju sadr\u017eavati podatke za autorizaciju\n   # u va\u0161 bazen.\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
Potrebno je ispuniti clusterID<\/strong>, koji smo ve\u0107 saznali naredbom ceph fsid<\/em>, i primijeniti ovaj manifest u Kubernetes klasteru:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Da provjerimo rad klastera zajedno, stvorit \u0107emo ovakav 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
Odmah \u0107emo provjeriti kako je Kubernetes stvorio tra\u017eeni volumen u Ceph-u:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Izgleda odli\u010dno! A kako to izgleda sa strane Ceph-a?
\nDobijamo popis volumena u bazenu i pregledavamo informacije o na\u0161em volumenu:<\/p>\n
rbd ls -p kube\nrbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653  # ovdje \u0107e, naravno, biti drugi ID volumena koji je prethodna naredba vratila<\/code><\/pre>\n
Sada \u0107emo pogledati kako radi promjena veli\u010dine RBD volumena.
\nMijenjamo veli\u010dinu volumena u manifestu pvc.yaml na 2Gi i primjenjujemo ga:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Pri\u010dekajmo da promjene stupe na snagu i jo\u0161 jednom provjerimo veli\u010dinu volumena.<\/p>\n
rbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653\n\nkubectl get pv\nkubectl get pvc<\/code><\/pre>\n
Vidimo da se veli\u010dina PVC-a nije promijenila. Da bismo saznali razlog, mo\u017eemo zatra\u017eiti od Kubernetes-a opis PVC-a u YAML formatu:<\/p>\n
kubectl get pvc rbd-pvc -o yaml<\/code><\/pre>\n
I evo problema:<\/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
Dakle, disk se pove\u0107ao, ali datote\u010dni sustav na njemu \u2014 ne.
\nDa bismo pove\u0107ali datote\u010dni sustav, moramo montirati volumen. Na\u0161 stvoreni PVC\/PV trenutno se ni na koji na\u010din ne koristi.<\/p>\n
Mo\u017eemo stvoriti testni Pod, na primjer ovako:<\/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
I sada pogledajmo PVC:<\/p>\n
kubectl get pvc<\/code><\/pre>\n
Veli\u010dina se promijenila, sve je u redu.<\/p>\n
U prvom dijelu smo radili s blok ure\u0111ajem RBD (to je skra\u0107enica za Rados Block Device), ali to se ne mo\u017ee raditi ako razli\u010diti mikroservisi trebaju istovremeno raditi s ovim diskom. Za rad s datotekama, a ne s slikom diska, mnogo bolje odgovara CephFS.
\nNa primjeru klastera Ceph i Kubernetes postavit \u0107emo CSI i ostale potrebne entitete za rad s CephFS.<\/p>\n
Dohvatimo vrijednosti iz potrebnog novog Helm-charta:<\/p>\n
helm inspect values ceph-csi\/ceph-csi-cephfs > cephfs.yml<\/code><\/pre>\n
Ponovno je potrebno ispuniti datoteku cephfs.yml. Kao i ranije, pomo\u0107i \u0107e nam Ceph naredbe:<\/p>\n
ceph fsid\nceph mon dump<\/code><\/pre>\n
Ispunjavaju\u0107i datoteku sa vrijednostima pribli\u017eno ovako:<\/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
Obratite pa\u017enju da su adrese monitora navedene u jednostavnom obliku address:port. Za montiranje cephfs na \u010dvor, ove adrese se proslje\u0111uju u kernel modul, koji jo\u0161 ne zna raditi s v2 protokol monitora.
\nPort za httpMetrics (gdje \u0107e Prometheus i\u0107i po metrika za nadgledanje) mijenjamo kako se ne bi sukobljavao s nginx-proxy, koji se instalira Kubespray-om. Mo\u017eda vam to ne\u0107e biti potrebno.<\/p>\n
Instaliramo Helm-chart u Kubernetes klaster:<\/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
Prelazimo na Ceph spremi\u0161te podataka kako bismo tamo stvorili posebnog korisnika. U dokumentaciji se navodi da provizoru CephFS trebaju administratorska prava pristupa klasteru. No stvorit \u0107emo posebnog korisnika fs<\/em> s ograni\u010denim pravima:<\/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
I odmah \u0107emo pogledati njegov pristupni klju\u010d, trebat \u0107e nam kasnije:<\/p>\n
ceph auth get-key client.fs<\/code><\/pre>\n
Stvorimo posebne Secret i StorageClass.
\nNema ni\u0161ta novog, ve\u0107 smo to vidjeli na primjeru RBD:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-cephfs-secret\n  namespace: ceph-csi-cephfs\nstringData:\n  # Potrebno za dinami\u010dki kreirane volumene\n  adminID: fs\n  adminKey:<\/code><\/pre>\n
Primjenjujemo manifest:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
A sada \u2013 poseban 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  # Ime CephFS datote\u010dnog sustava u kojem \u0107e se stvoriti volumen\n  fsName: cephfs\n\n  # (opcionalno) Ceph bazen u kojem \u0107e se pohranjivati podaci volumena\n  # pool: cephfs_data\n\n  # (opcionalno) Opcije monta\u017ee odvojene zarezima za Ceph-fuse\n  # na primjer:\n  # fuseMountOptions: debug\n\n  # (opcionalno) Opcije monta\u017ee CephFS za kernel, odvojene zarezima\n  # Pogledajte man mount.ceph za popis ovih opcija. Na primjer:\n  # kernelMountOptions: readdir_max_bytes=1048576,norbytes\n\n  # Tajne moraju sadr\u017eavati pristupe za admina i\/ili Ceph korisnika.\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  # (opcionalno) Voza\u010d mo\u017ee koristiti ili ceph-fuse (fuse), \n  # ili ceph kernelclient (kernel).\n  # Ako nije navedeno, koristit \u0107e se zadana monta\u017ea volumena,\n  # to se odre\u0111uje pretragom ceph-fuse i mount.ceph\n  # mounter: kernel\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - debug<\/code><\/pre>\n
Ispunimo ovdje clusterID<\/strong> i primijenimo u Kubernetesu:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Provjera<\/h2>\n
Za provjeru, kao u prethodnom primjeru, stvorit \u0107emo 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
I provjerimo postoji li PVC\/PV:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Ako \u017eelite pogledati datoteke i mape u CephFS-u, mo\u017eete montirati ovaj datote\u010dni sustav negdje. Na primjer, kao \u0161to je prikazano u nastavku.<\/p>\n
Idemo na jedan od \u010dvorova Ceph klastera i izvr\u0161imo sljede\u0107e radnje:<\/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
Naravno, ovakvo montiranje FS na Ceph \u010dvoru je isklju\u010divo za edukacijske svrhe, \u010dime se i bavimo na na\u0161im Slurm te\u010dajevima<\/a><\/noindex>. Ne mislim da bi netko to radio u produkciji, postoji veliki rizik od slu\u010dajnog brisanja va\u017enih datoteka.<\/p>\n
Na kraju, provjerimo kako se situacija s promjenom veli\u010dine volumena odvija u slu\u010daju CephFS-a. Vra\u0107amo se u Kubernetes i ure\u0111ujemo na\u0161 manifest za PVC - pove\u0107avamo veli\u010dinu, recimo, na 7Gi.<\/p>\n
Primjenjujemo ure\u0111eni dokument:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Pogledajmo na montiranom direktoriju kako se promijenila kvota:<\/p>\n
getfattr -n ceph.quota.max_bytes<\/code><\/pre>\n
Za rad ove naredbe, mo\u017eda \u0107ete trebati instalirati paket attr<\/strong>.<\/p>\n
O\u010di se boje, a ruke rade<\/h2>\n
Na prvi pogled, sva ta \u010darolija i dugi YAML manifesti izgledaju slo\u017eeno, ali u praksi studenti Slayer-a ih prili\u010dno brzo savladaju.
\nU ovom \u010dlanku nismo ulazili previ\u0161e u detalje \u2014 za to postoji slu\u017ebena dokumentacija. Ako vas zanimaju detalji konfiguracije Ceph skladi\u0161ta u suradnji s Kubernetes klasterom, pomo\u0107i \u0107e vam sljede\u0107e veze:<\/p>\n
Op\u0107a na\u010dela rada Kubernetes-a s volumenima<\/a><\/noindex>
\nDokumentacija o RBD-u<\/a><\/noindex>
\nIntegracija RBD-a i Kubernetes-a s aspekta Ceph-a<\/a><\/noindex>
\nIntegracija RBD-a i Kubernetes-a s aspekta CSI-a<\/a><\/noindex>
\nOp\u0107a dokumentacija o CephFS-u<\/a><\/noindex>
\nIntegracija CephFS-a i Kubernetes-a s aspekta CSI-a<\/a><\/noindex><\/p>\n
Na te\u010daju Slayer-a Kubernetes Osnovna<\/a><\/noindex> mo\u017eete i\u0107i jo\u0161 malo dalje i implementirati stvarnu aplikaciju u Kubernetes-u koja \u0107e koristiti CephFS kao skladi\u0161te za datoteke. Putem GET\/POST zahtjeva mo\u0107i \u0107ete slati i primati datoteke iz Ceph-a.<\/p>\n
A ako vas vi\u0161e zanima pohrana podataka, prijavite se na novi te\u010daj o Ceph-u<\/a><\/noindex>. Dok traje beta testiranje, te\u010daj mo\u017eete dobiti uz popust i utjecati na njegov sadr\u017eaj.<\/p>\n
Autor \u010dlanka: Aleksandar \u0160valov, prakti\u010dni in\u017eenjer Southbridge<\/a><\/noindex>, Certified Kubernetes Administrator, autor i razvija\u010d te\u010dajeva Slayer-a.<\/em><\/p>\n
Izvor: 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\udd47Prakti\u010dni primjer povezivanja skladi\u0161ta temeljenog na Ceph-u u Kubernetes klaster | ProHoster","description":"Container Storage Interface (CSI) je jedinstveni su\u010delje za interakciju izme\u0111u Kubernetes-a i sustava za pohranu podataka.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/94739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=94739"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/94739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/94740"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=94739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=94739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=94739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}