You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
== Understanding the Self Node Remediation Operator configuration
15
15
16
-
The Self Node Remediation Operator creates the `SelfNodeRemediationConfig` CR with the name `self-node-remediation-config` in the Self Node Remediation Operator's namespace. You can edit this CR. However, you cannot create a new CR for the Self Node Remediation Operator.
16
+
The Self Node Remediation Operator creates the `SelfNodeRemediationConfig` CR with the name `self-node-remediation-config`. The CR is created in the namespace of the Self Node Remediation Operator.
17
17
18
18
A change in the `SelfNodeRemediationConfig` CR re-creates the Self Node Remediation daemon set.
19
19
@@ -28,7 +28,7 @@ metadata:
28
28
namespace: openshift-operators
29
29
spec:
30
30
safeTimeToAssumeNodeRebootedSeconds: 180 <1>
31
-
watchdogFilePath: /test/watchdog1 <2>
31
+
watchdogFilePath: /dev/watchdog1 <2>
32
32
isSoftwareRebootEnabled: true <3>
33
33
apiServerTimeout: 15s <4>
34
34
apiCheckInterval: 5s <5>
@@ -52,6 +52,20 @@ If a watchdog device is unavailable, the `SelfNodeRemediationConfig` CR uses a s
52
52
<9> Specify the timeout duration to get a response from the peer.
53
53
<10> Specify the frequency to update peer information, such as IP address.
54
54
55
+
[NOTE]
56
+
====
57
+
You can edit the `self-node-remediation-config` CR that is created by the Self Node Remediation Operator. However, when you try to create a new CR for the Self Node Remediation Operator, the following message is displayed in the logs:
58
+
59
+
[source,text]
60
+
----
61
+
controllers.SelfNodeRemediationConfig
62
+
ignoring selfnoderemediationconfig CRs that are not named 'self-node-remediation-config'
0 commit comments