Self Node Remediation Operator Bundle

v0.11.0-1359dbe

v0.11

3bf8ef27f9a7f50c7e9fa066cabe8927efc8a3a890783bd9b60156b4ef417a77

v0.11.0

Overview

Description

This self node remediation operator is using an alternate mechanism for a node in a cluster to detect its health status and take actions to remediate itself in case of a failure. While not all remediation events can result in the node returning to a healthy state, the operator does allow surviving parts of the cluster to assume the node has reached a safe state so that it's workloads can be automatically recovered. A prerequisite for the self node remediation operator is a functioning health detection system that implements the external remediation API, such as Node Healthcheck Operator, Machine Health Check Controller (in OCP or Cluster-API based clusters). Once a node/machine is unhealthy, the detection system will create the SelfNodeRemediation CR, which triggers the self node remediation operator. To get started, a user would need to create a SelfNodeRemediationTemplate, and reference that CR with an NHC/MHC CR.

Products using this container

Workload Availability for Red Hat OpenShift

A collection of Operators that ensure stateful workloads can safely be recovered in the event of a complete or partial node failure.

Containerized application

Security

Technical information

General information

The following information was extracted from the containerfile and other sources.

Summary	Self Node Remediation bundle
Description	Self Node Remediation bundle
Provider	Red Hat
Maintainer	Dragonfly Team <team-dragonfly@redhat.com>

Technical information

The following information was extracted from the containerfile and other sources.

Repository name	workload-availability/self-node-remediation-bundle
Image version	v0.11.0
Architecture	amd64

Packages

Containerfile

Get this image

Terms & conditionsBefore downloading or using this Container, you must agree to the Red Hat subscription agreement located at redhat.com/licenses. If you do not agree with these terms, do not download or use the Container. If you have an existing Red Hat Enterprise Agreement (or other negotiated agreement with Red Hat) with terms that govern subscription services associated with Containers, then your existing agreement will control.

Using registry tokens

Registry

Repository

Image Digest

Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.

Using OpenShift secrets

First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.

Then, use the following from the command line or from the OpenShift Dashboard GUI interface.

Using podman login

Use the following command(s) from a system with podman installed

Using docker login

Use the following command(s) from a system with docker service installed and running

Registry

Repository

Image Digest

Use the following instructions to get images from a Red Hat container registry using your Red Hat login.

Using OpenShift

For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.

Using podman login

Use the following command(s) from a system with podman installed

Using docker login

Use the following command(s) from a system with docker service installed and running

Get the source

Registry

Repository

Image Digest

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.
Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Step one

Use skopeo to copy the source image to a local directory

Step two

Inspect the image

Step three

Untar the contents

Step four

Begin examining and using the content.

Description

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.

Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).

The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.

Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Description

Products using this container

Workload Availability for Red Hat OpenShift

Published

Release category

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Getting source containers

Step one

Step two

Step three

Step four

Platforms

Products & services

Try, buy, sell

Help

About Red Hat Ecosystem Catalog

Red Hat legal and privacy links

Red Hat legal and privacy links

Self Node Remediation Operator Bundle

Description

Products using this container

Workload Availability for Red Hat OpenShift

Published

Release category

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Getting source containers

Step one

Step two

Step three

Step four