npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

node-auto-repair

v1.1.1

Published

Automatically detect unhealthy Kubernetes nodes and repair them

Downloads

2

Readme

node-auto-repair

Automatically detect unhealthy Kubernetes nodes and repair them.

Inspiration

Google Kubernetes Engine can automatically repair unhealthy nodes and then replacing them with a new node. This might not be possible when running Kubernetes on-premise. Instead of replacing the nodes, an attempt to repair them can be made by first identifying the problem, and then attempting to repair it.

Usage

The NodeAutoRepair class listens for unhealthy nodes using the Kubernetes API. When a node becomes unhealthy, it first waits a given period of time and then checks if the node is still unhealthy. If it is still unhealthy, then a repair attempt is made. If the node doesn't become healthy after a given period of time, then another attempt is made. This continues until either the node becomes healthy, or max repair attempts has been made.

To use NodeAutoRepair, create a class that implements the AutoRepair interface. The repair function is called when a node needs to be repaired. It should find the problem, and then attempt to fix it. Multiple attempts can be made to fix the problem. For example, if one fix didn't work, then a different fix could be tried.

Example

import { NodeAutoRepair, AutoRepair } from 'node-auto-repair';

class CustomAutoRepair implements AutoRepair {
  async repair(apiObj: V1Node, attempts: number): Promise<void> {
    console.log(
      'Attempt #' + attempts + ' to repair node ' + apiObj.metadata.name,
    );

    // Do something to repair node
    await findTheProblem();
    await attemptToFixTheProblem();
  }

  repairAttemptFailed(apiObj: V1Node, attempts: number): void {
    console.log(
      'Attempt #' +
        attempts +
        ' to repair node ' +
        apiObj.metadata.name +
        ' failed',
    );
  }

  repairAttemptsFailed(apiObj: V1Node, attempts: number): void {
    console.log(
      'Failed to repair node ' +
        apiObj.metadata.name +
        ' after ' +
        attempts +
        ' attempts',
    );
  }

  repairSuccess(apiObj: V1Node, attempts: number): void {
    console.log(
      'Repaired node ' +
        apiObj.metadata.name +
        ' after ' +
        attempts +
        ' attempts',
    );
  }
}

const NodeAutoRepair = new NodeAutoRepair(new CustomAutoRepair(), {
  kubeConfigPath: 'path/to/kubeconfig',
});

NodeAutoRepair.start();