# Addon: rook-ceph

**URL:** <https://discuss.kubernetes.io/t/addon-rook-ceph/25042>\
**Category:** microk8s\
**Tags:** docs\
**Created:** [August 8, 2023, 2:32pm UTC](https://discuss.kubernetes.io/t/addon-rook-ceph/25042 "2023-08-08T14:32:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kjackal](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/kjackal/32/1750_2.png) [@kjackal](https://discuss.kubernetes.io/u/kjackal)\
**Post date:** [August 8, 2023, 2:32pm UTC](https://discuss.kubernetes.io/t/addon-rook-ceph/25042/1 "2023-08-08T14:32:01Z")

</div>

![1.28](https://img.shields.io/badge/From%20version-1.28-brightgreen?style=for-the-badge&logo=kubernetes&labelColor=ddd)  
**Compatibility** : ![amd64](https://img.shields.io/badge/amd64-%E2%9C%93-383) ![arm64](https://img.shields.io/badge/arm64-%E2%9C%93-orange)  
**Source** : See [rook.io](https://rook.io/) website for more details.

Rook turns distributed storage systems into self-managing, self-scaling, self-healing storage services.  
It automates the tasks of a storage administrator: deployment, bootstrapping, configuration, provisioning, scaling, upgrading, migration, disaster recovery, monitoring, and resource management.

This addon deploys the Rook Kubernetes Operator for Ceph.

## Usage

To enable the addon:

```auto
microk8s enable rook-ceph

```

The addon can be disabled at any time with:

```auto
microk8s disable rook-ceph

```

## Specify Rook version

It is possible to specify the Rook version to install using the `--rook-version` argument when enabling the addon:

```auto
microk8s enable rook-ceph --rook-version v1.11.9

```

## Consume storage from external Ceph clusters

When enabled, the addon enhances the `microk8s` cli with a `connect-external-ceph` command through which you can import external Ceph clusters:

Explore the available options of this command with:

```auto
microk8s connect-external-ceph --help

```

## Links

To learn more about Rook and Ceph visit:

- [rook.io](https://rook.io/)
- [ceph.io](https://ceph.io/)
- [MicroCeph](https://canonical-microceph.readthedocs-hosted.com/en/latest/)

---

<div class="post-metadata">

**Author:** ![roadSurfer](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/roadsurfer/32/13997_2.png) [@roadSurfer](https://discuss.kubernetes.io/u/roadSurfer)\
**Post date:** [January 8, 2024, 2:54pm UTC](https://discuss.kubernetes.io/t/addon-rook-ceph/25042/2 "2024-01-08T14:54:07Z")

</div>

Is there any documentation on the required values for and format of the files for `--ceph-conf` and `--keyring` and how these values are created/obtained?  
Maybe it is hiding within the Rook and/or Ceph documentation, but I have been unable to find anything.

**Note:** I am trying to connect to a remote Ceph cluster, not something running within my local K8s cluster.

---

<div class="post-metadata">

**Author:** ![Gustavo\_Sanchez](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/gustavo_sanchez/32/14878_2.png) [@Gustavo\_Sanchez](https://discuss.kubernetes.io/u/Gustavo_Sanchez)\
**Post date:** [May 1, 2024, 7:47pm UTC](https://discuss.kubernetes.io/t/addon-rook-ceph/25042/3 "2024-05-01T19:47:57Z")

</div>

Yeah that would be more on Ceph side of things

For the **keyring files**  
You could use the Ceph root credentials (unsecure)  
Or create new Ceph keyrings (credentials)

```bash
sudo ceph auth add [..] 
sudo ceph auth get <name>

```

[https://docs.ceph.com/en/latest/rados/operations/user-management/](https://docs.ceph.com/en/latest/rados/operations/user-management/)

For the **configuration file**  
You can obtain it like this

```bash
sudo ceph config generate-minimal-conf

```