Skip to content

Commit 7064eeb

Browse files
authored
Merge pull request #47364 from abhatt-rh/td-619
ECOPROJECT 615: Updating references to Poison Pill Operator with Self Node Remediation Operator in NHC files
2 parents ec919a5 + a721072 commit 7064eeb

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

modules/eco-node-health-check-operator-about.adoc

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@
66
[id="about-node-health-check-operator_{context}"]
77
= About the Node Health Check Operator
88

9-
The Node Health Check Operator deploys the `NodeHealthCheck` controller to detect the health of a node in the cluster. The `NodeHealthCheck` controller creates the `NodeHealthCheck` custom resource (CR), which defines a set of criteria and thresholds to determine the node's health.
9+
The Node Health Check Operator deploys the `NodeHealthCheck` controller to detect the health of a node in the cluster. The `NodeHealthCheck` controller creates the `NodeHealthCheck` custom resource (CR), which defines a set of criteria and thresholds to determine the node's health.
1010

11-
The Node Health Check Operator also installs the Poison Pill Operator as a default remediation provider.
11+
The Node Health Check Operator also installs the Self Node Remediation Operator as a default remediation provider.
1212

13-
When the Node Health Check Operator detects an unhealthy node, it creates a remediation CR that triggers the remediation provider. For example, the controller creates the `PoisonPillRemediation` CR, which triggers the Poison Pill Operator to remediate the unhealthy node.
13+
When the Node Health Check Operator detects an unhealthy node, it creates a remediation CR that triggers the remediation provider. For example, the controller creates the `SelfNodeRemediation` CR, which triggers the Self Node Remediation Operator to remediate the unhealthy node.
1414

1515
The `NodeHealthCheck` CR resembles the following YAML file:
1616

@@ -24,12 +24,12 @@ metadata:
2424
spec:
2525
minHealthy: 51% <1>
2626
pauseRequests: <2>
27-
- <pause-test-cluster>
27+
- <pause-test-cluster>
2828
remediationTemplate: <3>
29-
apiVersion: poison-pill.medik8s.io/v1alpha1
30-
name: group-x
29+
apiVersion: self-node-remediation.medik8s.io/v1alpha1
30+
name: self-node-remediation-resource-deletion-template
3131
namespace: openshift-operators
32-
kind: PoisonPillRemediationTemplate
32+
kind: SelfNodeRemediationTemplate
3333
selector: <4>
3434
matchExpressions:
3535
- key: node-role.kubernetes.io/worker
@@ -50,9 +50,9 @@ spec:
5050
====
5151
During the upgrade process, nodes in the cluster might become temporarily unavailable and get identified as unhealthy. In the case of worker nodes, when the Operator detects that the cluster is upgrading, it stops remediating new unhealthy nodes to prevent such nodes from rebooting.
5252
====
53-
<3> Specifies a remediation template from the remediation provider. For example, from the Poison Pill Operator.
53+
<3> Specifies a remediation template from the remediation provider. For example, from the Self Node Remediation Operator.
5454
<4> Specifies a `selector` that matches labels or expressions that you want to check. The default value is empty, which selects all nodes.
55-
<5> Specifies a list of the conditions that determine whether a node is considered unhealthy.
55+
<5> Specifies a list of the conditions that determine whether a node is considered unhealthy.
5656
<6> Specifies the timeout duration for a node condition. If a condition is met for the duration of the timeout, the node will be remediated. Long timeouts can result in long periods of downtime for a workload on an unhealthy node.
5757

5858
[id="understanding-nhc-operator-workflow_{context}"]
@@ -63,7 +63,7 @@ When a node is identified as unhealthy, the Node Health Check Operator checks ho
6363
When the node turns healthy, the controller deletes the external remediation template.
6464

6565
[id="how-nhc-prevent-conflict-with-mhc_{context}"]
66-
== About how node health checks prevent conflicts with machine health checks
66+
== About how node health checks prevent conflicts with machine health checks
6767

6868
When both, node health checks and machine health checks are deployed, the node health check avoids conflict with the machine health check.
6969

nodes/nodes/eco-node-health-check-operator.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
Use the Node Health Check Operator to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Poison Pill Operator to remediate the unhealthy nodes.
9+
Use the Node Health Check Operator to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes.
1010

1111
[role="_additional-resources"]
1212
.Additional resources

0 commit comments

Comments
 (0)