Ritchie, Frank (fr801x) b2dc921b05 Use upstream rook yamls as base
This is a scaled back version of:

https://review.opendev.org/c/airship/treasuremap/+/792837

This PS basically uses kustomize patches to modify the upstream
yamls to create the base resources. Currently we manually
edit the upstream yamls. The yamls produced by "kubectl kustomize ."
are as before.

Kpt can be used for syncing to upstream once this issue is resolved:

https://github.com/GoogleContainerTools/kpt/issues/517

Change-Id: Idd7a3f4a61a9dae9ec82dd0a604eb371bdbb4ab4
2021-06-10 09:32:55 -05:00

23 lines
772 B
YAML

# Use the config section below to create your custom
# ceph.conf file
# Refer to the documentation at:
# https://rook.io/docs/rook/v1.6/ceph-advanced-configuration.html#custom-cephconf-settings
# Be aware - the rook operator doesn't perform any validations or syntax check against
# the configuration below. Even a typo in this file can cause an entire cluster failure.
kind: ConfigMap
apiVersion: v1
metadata:
name: rook-config-override
namespace: rook-ceph # namespace:cluster
data:
config: |
[global]
osd_pool_default_size = 3
mon_warn_on_pool_no_redundancy = true
# # You can add other default configuration sections
# # to create fully customized ceph.conf
[mon]
auth_allow_insecure_global_id_reclaim = false
# [osd]
# [rgw]