![]() 09:19:25.448532 E | ceph-cluster-controller: failed to reconcile. 09:19:25.435642 I | ceph-cluster-controller: clusterInfo not yet found, must be a new cluster 09:19:25.433006 I | ceph-cluster-controller: reconciling ceph cluster in namespace "rook-ceph" $ k logs rook-ceph-operator-757bbbc4c6-mw4c4 My first try to get this stuff installed resulted in some errors on the operator side: A missing CRD ( CephFilesystemMirror)? Nope, I downloaded the wrong resources Note that I have left out a CephCluster object, and CephBlockPools and StorageClass objects as well. The files in the list above do contain some combined resource files (ex.rbac.yaml files have applicable Role, ClusterRole, RoleBinding and ClusterRoleBindings in them). A look at the actual pieces of a Rook install: Maybe refer to these sections if and only if you have issues down the road installing Ceph yourself.Īssuming you provisioned drives correctly (I have one drive free and 1 large partition as a result of the setup scripts), the basic rook simple is real easy, just install the operator with some curl | kubectl apply command right? Nope, we do things the hard way here – My first step when installing software is to decompose the large all-in-one YAML that comes and make some reasonably named pieces. Reading the titles for the subsections should be enough to get an idea of what I had to change. (Ceph recently changed how ceph-volume batch works). Just a heads up, you should skip/skim this LVM section if you don’t want to wade through me making almost every possible mistake in the book getting Ceph running, generally the only legitimate issue I ran into that isn’t attributable to user error in some way was downgrading to 15.2.6 to avoid issues with handling partitions. Ceph on LVM via Rook - STORAGE_PROVIDER=rook-ceph-lvm This is where things get spicy, and other cluster operators may find some insights. OK, so we’ve got a machine that’s ready, and a k8s cluster (of one, for now) install that is purring along, time to actually install the relevant storage provider(s). Now it’s time to install the storage plugins themselves so we can get to testing them.Ĭluster operators will probably gain the most insight (if any) here, whereas Sysadmins might have liked Part 1 better. In part 1 we got some nice automation for server set up, pre-requisite installation and Kubernetes install. Part 3 - Installing more storage plugins.Part 2 - Installing storage plugins (you are here).Part 1 - Intro & cloud server wrangling.The GitLab repository is up! You can skip this entire article and just go there. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |