Releases

This page details the official releases of the Node Readiness Controller.

v0.2.0

Date: 2026-02-28

This release brings several new features, including a validating admission webhook that validates NodeReadinessRule configurations, prevents conflicting rules with overlapping node selectors, and warns against risky NoExecute enforcement. It also introduces metrics manifests natively integrated with Kustomize, which includes support for secure metrics via TLS. Finally, this release includes major documentation improvements.

Release Notes

Features & Enhancements

• Add webhook as kustomize component (#122)
• Enable metrics manifests (#79)
• Use status.patch api for node updates (#104)
• Mark controller as system-cluster-critical to prevent eviction (#108)
• Enhance Dockerfiles and bump Go module version (#113)
• Add build-installer make target to create CRD and install manifests (#95, #93)
• Add a pull request template (#110)

Bug Fixes

• Fix dev-container: disable moby in newer version of debian (#127)
• Add missing boilerplate headers in metrics.go (#119)
• Update path to logo in README (#115)

Code Cleanup & Maintenance

• Remove unused globalDryRun feature (#123, #130)
• Bump versions for devcontainer and golangci-kal (#132)

Documentation & Examples

• Document NoExecute taint risks and add admission warning (#120)
• Updates on getting-started guide and installation docs (#135, #92)
• Add example for security agent readiness (#101)
• Managing CNI-readiness with node-readiness-controller and switch reporter to daemonset (#99, #116)
• Update cni-patcher to use registry.k8s.io image (#96)
• Add video demo (#114) and update heptagon logo (#109)
• Remove stale docs/spec.md (#126)

Images

The following container images are published as part of this release.

// Node readiness controller
registry.k8s.io/node-readiness-controller/node-readiness-controller:v0.2.0

// Report component readiness condition from the node
registry.k8s.io/node-readiness-controller/node-readiness-reporter:v0.2.0

Installation

Prerequisites: If you plan to install with all optional features enabled (install-full.yaml), you must have cert-manager installed in your cluster.

To install the CRDs, apply the crds.yaml manifest for this version:

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.2.0/crds.yaml

To install the controller, choose one of the following manifests based on your requirements:

Standard Installation (Minimal): The simplest way to deploy the controller with no external dependencies.

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.2.0/install.yaml

Full Installation (Production Ready): Includes secure metrics (TLS-protected) and validating webhooks for rule conflict prevention. Requires cert-manager to be installed in your cluster.

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.2.0/install-full.yaml

This will deploy the controller into any available node in the nrr-system namespace in your cluster. Check here for more detailed installation instructions.

Contributors

• ajaysundark
• arnab-logs
• AvineshTripathi
• GGh41th
• Hii-Himanshu
• ketanjani21
• knechtionscoding
• OneUpWallStreet
• pehlicd
• Priyankasaggu11929
• sats-23

v0.1.1

Date: 2026-01-19

This patch release includes important regression bug fixes and documentation updates made since v0.1.0.

Release Notes

Bug or Regression

• Fix race condition where deleting a rule could leave taints stuck on nodes (#84)
• Ensure new node evaluation results are persisted to rule status (#87]

Documentation

• Add/update Concepts documentation (enforcement modes, dry-run, condition reporting) (#74)
• Add v0.1.0 release notes to docs (#76)

Images

The following container images are published as part of this release.

// Node readiness controller
registry.k8s.io/node-readiness-controller/node-readiness-controller:v0.1.1

// Report component readiness condition from the node
registry.k8s.io/node-readiness-controller/node-readiness-reporter:v0.1.1

Installation

To install the CRDs, apply the crds.yaml manifest for this version:

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.1.1/crds.yaml

To install the controller, apply the install.yaml manifest for this version:

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.1.1/install.yaml

This will deploy the controller into any available node in the nrr-system namespace in your cluster. Check here for more installation instructions.

Contributors

• ajaysundark

v0.1.0

Date: 2026-01-14

This is the first official release of the Node Readiness Controller.

Release Notes

• Initial implementation of the Node Readiness Controller.
• Support for NodeReadinessRule API (readiness.node.x-k8s.io/v1alpha1).
• Defines custom readiness rules for k8s nodes based on node conditions.
• Manages node taints to prevent scheduling until readiness rules are met.
• Includes modes for bootstrap-only and continuous readiness enforcement.
• Readiness condition reporter for reporting component health.

Images

The following container images are published as part of this release.

// Node readiness controller
registry.k8s.io/node-readiness-controller/node-readiness-controller:v0.1.0

// Report component readiness condition from the node
registry.k8s.io/node-readiness-controller/node-readiness-reporter:v0.1.0

Installation

To install the CRDs, apply the crds.yaml manifest for this version:

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.1.0/crds.yaml

To install the controller, apply the install.yaml manifest for this version:

kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.1.0/install.yaml

This will deploy the controller into any available node in the nrr-system namespace in your cluster. Check here for more installation instructions.

Contributors

• ajaysundark
• Karthik-K-N
• Priyankasaggu11929
• sreeram-venkitesh
• Hii-Himanshu
• Serafeim-Katsaros
• arnab-logs
• Yuan-prog
• AvineshTripathi