Skip to content

Commit b29e1fb

Browse files
committed
README adjustments from feedback
1 parent fc7d147 commit b29e1fb

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

README.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,9 @@ oc delete csv telemetry-operator.v0.0.1
5858
```
5959

6060
8.- Deploy custom telemetry-operator version
61+
62+
NOTE: If you intend to deploy a custom telemetry object *with pre-populated image URLs*, you can use `make run` instead of `make run-with-webhook`, because the webhooks will not be required.
63+
6164
```
6265
cd telemetry-operator
6366
@@ -68,8 +71,18 @@ make manifests generate
6871
OPERATOR_TEMPLATES=$PWD/templates make run-with-webhook
6972
```
7073

71-
9.- Deploy Telemetry:
74+
75+
9.- Deploy Telemetry
76+
77+
There are two options, either let openstack-operator manage a telemetry object, or disable openstack-operator and manage it yourself.
78+
79+
9a.- To continue running openstack-operator and use a telemetry object under its control, re-enable telemetry in the oscp:
80+
```
81+
oc patch openstackcontrolplane openstack-galera-network-isolation --type='json' -p='[{"op": "replace", "path": "/spec/telemetry/enabled", "value":true}]'
82+
```
83+
9b - To disable openstack-operator and use a custom telemetry object
7284
```
85+
oc scale deploy/openstack-operator-controller-manager --replicas=0 -n openstack-operators
7386
oc apply -f config/samples/telemetry_v1beta1_telemetry.yaml
7487
```
7588

0 commit comments

Comments
 (0)