Skip to content

Commit d383f83

Browse files
committed
Docs: CRDS: shows how to get crds names for config and adds an image
1 parent f7a22f7 commit d383f83

File tree

2 files changed

+28
-8
lines changed

2 files changed

+28
-8
lines changed

docs/images/crd_demo.png

127 KB
Loading

docs/setup-robusta/crds.rst

Lines changed: 28 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,11 @@ The CRDs monitoring feature enables you to view and manage Custom Resource Defin
1313
* Full YAML manifests
1414
* Detailed resource descriptions
1515

16+
.. image:: /images/crd_demo.png
17+
:width: 800
18+
:align: center
19+
:alt: CRDs monitoring in Robusta UI
20+
1621
Prerequisites
1722
-------------
1823

@@ -21,6 +26,29 @@ To enable CRD monitoring, the Robusta agent needs appropriate permissions to rea
2126
Configuration
2227
-------------
2328

29+
Finding CRD Names and API Groups
30+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
31+
32+
Get the CRD names and API groups to use in the configuration below:
33+
34+
.. code-block:: bash
35+
36+
kubectl get crd \
37+
-o custom-columns=NAME:.spec.names.plural,API_GROUP:.spec.group
38+
39+
This will output something like:
40+
41+
.. code-block:: text
42+
43+
NAME API_GROUP
44+
alertmanagerconfigs monitoring.coreos.com
45+
alertmanagers monitoring.coreos.com
46+
imagejobs eraser.sh
47+
imagelists eraser.sh
48+
nodenetworkconfigs acn.azure.com
49+
overlayextensionconfigs acn.azure.com
50+
...
51+
2452
Basic Configuration
2553
^^^^^^^^^^^^^^^^^^^
2654

@@ -40,14 +68,6 @@ Specify read permissions for the CRDs you need to monitor:
4068
verbs:
4169
- "list"
4270
- "get"
43-
- apiGroups:
44-
- "acme.cert-manager.io"
45-
resources:
46-
- "challenges"
47-
- "orders"
48-
verbs:
49-
- "list"
50-
- "get"
5171
5272
Applying the Configuration
5373
^^^^^^^^^^^^^^^^^^^^^^^^^^^

0 commit comments

Comments
 (0)