-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CSV description #79
Conversation
Skipping CI for Draft Pull Request. |
6e1f9e2
to
d6b5cec
Compare
/test 4.13-openshift-e2e |
Improve FAR CSV short description to include that it provide HA and it is done automatically
22ee7f4
to
2e587ae
Compare
/test 4.13-openshift-e2e |
1 similar comment
/test 4.13-openshift-e2e |
Improve FAR CSV description better introduction to FAR, other remediatiors and NHC usability, and some pros for using FAR
Use FAR TBA link rather than general medik8s.io
2e587ae
to
6272d9c
Compare
@@ -352,7 +360,7 @@ spec: | |||
- baremetal | |||
links: | |||
- name: Fence Agents Remediation | |||
url: https://medik8s.io | |||
url: https://medik8s.io/fence-agents-remediation/fence-agents-remediation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is broken I'd probably wait to merge docs PR first
medik8s/docs#63
|
||
FAR is one of the remediator operators by [Medik8s](https://www.medik8s.io/remediation/remediation/), | ||
such as [Self Node Remediation](https://github.com/medik8s/self-node-remediation) and [Machine Deletion Remediation](https://github.com/medik8s/machine-deletion-remediation), | ||
that were designed to run with the Node HealthCheck Operator [(NHC)](https://github.com/medik8s/node-healthcheck-operator) as an external remediator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that external remediator
in the context of NHC is confusing.
IIRC it is relevant for MHC who both have an "internal" remediation mechanism and can also use different "external" remediators.
Since NHC is not a remediator by itself it would probably be best not to use this terminology here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed it a little bit, let me know if it looks better.
FAR is one of the remediator operators by [Medik8s](https://www.medik8s.io/remediation/remediation/), | ||
such as [Self Node Remediation](https://github.com/medik8s/self-node-remediation) and [Machine Deletion Remediation](https://github.com/medik8s/machine-deletion-remediation), | ||
that were designed to run with the Node HealthCheck Operator [(NHC)](https://github.com/medik8s/node-healthcheck-operator) as an external remediator. | ||
It is recommended to use FAR with NHC for an easier and smoother experience, but it can be used as a standalone remediator for the more experienced user. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I think the main role of NHC in this context is giving the user a fully automated remediation process
Correcting code review comments
/test 4.13-openshift-e2e |
/test 4.14-openshift-e2e |
Replace 'availability of workloads' with 'workload availability'
/test 4.13-openshift-e2e |
/test 4.14-openshift-e2e |
description: Fence Agents Remediation Operator uses well-known agents to fence | ||
and remediate unhealthy nodes. In this process it can minimize downtime for | ||
stateful applications, restores compute capacity if transient failures occur, | ||
and increases the availability of workloads. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: "availability" sounds like uncountable to me, so I'd say "improve", more than "increase"
smoother experience,\nbut it can also work as a standalonde remediator for the | ||
more advanced user.\n" | ||
description: | | ||
Fence Agents Remediation (*FAR*) is a Kubernetes operator that *fence* and remediate unhealthy to healthy nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typos
"fence" -> "fences"
"remediate" -> "remediates"
more advanced user.\n" | ||
description: | | ||
Fence Agents Remediation (*FAR*) is a Kubernetes operator that *fence* and remediate unhealthy to healthy nodes. | ||
Using a traditional Application Programming Interface (API) FAR runs uses well-known fence agents to remediate a node from an unhealthy state by power cycling the node, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: either runs or uses
description: | | ||
Fence Agents Remediation (*FAR*) is a Kubernetes operator that *fence* and remediate unhealthy to healthy nodes. | ||
Using a traditional Application Programming Interface (API) FAR runs uses well-known fence agents to remediate a node from an unhealthy state by power cycling the node, | ||
and afterwards it delets the node's resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: delets -> deletes
Fence Agents Remediation (*FAR*) is a Kubernetes operator that *fence* and remediate unhealthy to healthy nodes. | ||
Using a traditional Application Programming Interface (API) FAR runs uses well-known fence agents to remediate a node from an unhealthy state by power cycling the node, | ||
and afterwards it delets the node's resources. | ||
By doing so, FAR can minimize downtime for stateful applications, restores compute capacity if transient failures occur, and increases the availability of workloads. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is incorrect. The sentence begins with "FAR can..." so all the other verbs shouldn't use the third form present tense (FAR can minimize, can restore, can increase).
Maybe, you could just remove the first "can" and begin with "FAR minimizes..."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sentence begins with "FAR can..." so all the other verbs shouldn't use the third form present tense (FAR can minimize, can restore, can increase).
The can
is intended as a best effort from FAR, I will just use V1 of the verbs.
|
||
FAR is recommended when a node becomes unhealthy, and we want to completely fence/isolate the node from a cluster, since we can not “trust” the unhealthy node, | ||
to prevent it from accessing the shared resources like [RWO volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes). | ||
Moreover, FAR is *robust* as it can remediate an unhealthy node using a traditional API (e.g., IPMI) while still keeping control plane connectivity, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what you mean by "traditional API" 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As regular/known API. But maybe the traditional
isn't useful here.
what about using what we already have here: https://www.medik8s.io/remediation/fence-agents-remediation/fence-agents-remediation/ ? That one went through review and discussion already 🙂 |
Yes, I will use most of it with the addition of Compatability section for awareness of other Medik8s operators and a recommendation for using FAR with NHC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold give time to close other discussions |
The other discussions are old or by you, so I removing the draft for now, and waiting for more comments until all the tests are green (and the PR is still on hold). |
FAR is one of the remediator operators by [Medik8s](https://www.medik8s.io/remediation/remediation/), | ||
such as [Self Node Remediation](https://github.com/medik8s/self-node-remediation) and [Machine Deletion Remediation](https://github.com/medik8s/machine-deletion-remediation), | ||
that were designed to run with the Node HealthCheck Operator [(NHC)](https://github.com/medik8s/node-healthcheck-operator) which detects an unhealthy node and creates remediation CR. | ||
It is recommended to use FAR with NHC for an easier and smoother experience by fully automate the remediation process, but it can be used as a standalone remediator for the more experienced user. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/automate/automating
/test all |
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold cancel
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clobrano, razo7, slintes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Improve FAR CSV description to include how FAR works, why it is needed, what makes it a good remediator, and a recommendation to use it with NHC.