Skip to content

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

emesika/machine-remediation-operator

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

55 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

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

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Languages

  • Go 81.8%
  • Python 11.8%
  • Shell 5.6%
  • Other 0.8%