root

README

Machine Remediation

Remediation Flow

Architecture

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

It contains:

• machine-remediation controller
• node-reboot

How to deploy

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

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

Once the deployment finishes, create a MachineHealthCheck object and be sure to give it the healthchecking.openshift.io/strategy: reboot annotation that instructs the Machine Healthcheck controller to delegate remediation to us.

An example MachineHealthCheck object that covers all nodes in the cluster is as follows:

apiVersion: healthchecking.openshift.io/v1alpha1
kind: MachineHealthCheck
metadata:
 name: some-example
 namespace: openshift-machine-api
 annotations:
   healthchecking.openshift.io/strategy: reboot
spec:
 selector:
   matchLabels:
     kubernetes.io/os: linux
 unhealthyConditions:
 - type: Healthy
   status: Unknown
   timeout: 60s

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

Documentation

Overview

* This file is part of the KubeVirt project * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. * * Copyright 2019 Red Hat, Inc. *