8000 GitHub - kubevirt/machine-remediation at v0.3.12
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jan 29, 2025. It is now read-only.

Incubating: Deploy all components to recognize unhealthy machines and apply different remediation strategies on it

License

Notifications You must be signed in to change notification settings

kubevirt/machine-remediation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Machine Remediation Operator

Remediation Flow

Remediation Flow

Architecture

The machine remediation operator deploys components to monitor and remediate unhealthy machines for different platforms, it works on top of cluster-api controllers.

It should deploy three controllers:

How to deploy

You can check the GitHub releases to get latest yaml file, that includes CRD's, RBAC rules and operator deployment and apply it to your cluster.

kubectl apply -f https://github.com/kubevirt/machine-remediation-operator/releases/download/v0.3.3/machine-remediation-operator.yaml
kubectl apply -f https://github.com/kubevirt/machine-remediation-operator/releases/download/v0.3.3/machine-remediation-operator-cr.yaml

After just wait until the operator will deploy all components.

How to run e2e tests

You should have k8s or OpenShift environment with at least two worker nodes and run:

export KUBECONFIG=/dir/cluster/kubeconfig
make e2e-tests-run

About

Incubating: Deploy all components to recognize unhealthy machines and apply different remediation strategies on it

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Contributors 6

0