6 Commits

Include renames

Author	SHA1	Message	Date
Sébastien Han	c890710b63	core: change directory layout ... As per discussion, proposing a new layout for the charts/yaml/olm files. ./deploy ├── charts │ ├── rook-ceph │ │ └── templates │ └── rook-ceph-cluster │ └── templates ├── examples │ ├── csi │ │ ├── cephfs │ │ └── rbd │ ├── flex │ ├── monitoring │ ├── pre-k8s-1.16 └── olm └── assemble Signed-off-by: Sébastien Han <seb@redhat.com>	2021-11-30 09:12:53 +01:00
Mara Sophie Grosch	00a5debbab	monitoring: allow overriding monitoring labels ... The templates for the mgr-generated ServiceMonitor and PrometheusRule objects included the labels prometheus and team, making it impossible to override them as user. This adds a new method `OverwriteApplyToObjectMeta` to pkg/apis/ceph.rook.io/v1.Labels, which, contrary to the existing `ApplyToObjectMeta` method, overwrites existing labels. Closes: https://github.com/rook/rook/issues/8502 Signed-off-by: Mara Sophie Grosch <littlefox@lf-net.org>	2021-11-17 17:32:05 +01:00
Sébastien Han	dea3273eaf	ceph: do not force go path in unit tests ... Do not force unit tests to be run while the rook repo is in the GOPATH. Now that Rook uses go modules, this is no longer necessary. Allow this by creating a helper function that unit tests can use that return the on-host path to the `rook` project root. Followup of https://github.com/rook/rook/pull/7119/commits/15a487cd5aa5d4dc59bc15ef610cb182257d9287 Signed-off-by: Sébastien Han <seb@redhat.com>	2021-02-03 08:56:41 +01:00
Blaine Gardner	15a487cd5a	ceph: do not force go path in unit tests ... Do not force unit tests to be run while the rook repo is in the GOPATH. Now that Rook uses go modules, this is no longer necessary. Allow this by creating a helper function that unit tests can use that return the on-host path to the `rook` project root. Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>	2021-02-01 18:28:36 -07:00
Alexander Trost	430e4dc0f4	k8sutil: set ResourceVersion for PrometheusRule ... This change sets the ResourceVersion on the PrometheusRule object before it is updated in Kubernetes. This change fixes the following error ``` is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update ``` which can occur during update when no ResourceVersion is set. Resolves #4528 Signed-off-by: Alexander Trost <galexrt@googlemail.com>	2020-02-10 13:36:46 +01:00
Umanga Chapagain	732f3030d0	integrate prometheus based monitoring with rook-ceph ... > add new field to cluster spec > deploy servicemonitor > deploy prometheusRule Signed-off-by: Umanga Chapagain <chapagainumanga@gmail.com>	2019-07-08 11:40:17 +05:30