docs: add v0.2.0 release notes by AvineshTripathi · Pull Request #141 · kubernetes-sigs/node-readiness-controller

AvineshTripathi · 2026-02-28T07:35:31Z

related to #136

will add more description later!

netlify · 2026-02-28T07:35:37Z

✅ Deploy Preview for node-readiness-controller ready!

Name	Link
🔨 Latest commit	`e79617f`
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/69a7b5bb1b07a40008f6bffc
😎 Deploy Preview	https://deploy-preview-141--node-readiness-controller.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

AvineshTripathi · 2026-02-28T07:42:50Z

docs/book/src/releases.md

+To install the controller, apply the `install.yaml` manifest for this version:
+
+```sh
+kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.2.0/install.yaml


Question:

We recently introduced support for metrics and webhooks. However, in previous releases, we only provided a default install.yaml. Should we start publishing multiple versions of install.yaml like metrics-intall.yaml, or should users continue building their own from the source code?

We could certainly add additional manifests in this release.

How about something like, install-with-secure-metrics.yaml?

I think we should also ensure we update our installation documentation flow for completeness.

do we want the documentation changes to be part of this branch, or do we create a new one?

@ajaysundark added here 6b3ee84

I suggested an alternate for the published manifests. PTAL.
also, does this PR merge to new branch? seems to be still merging to main.

also, does this PR merge to new branch? seems to be still merging to main.

i am a little confused here. which branch should it be pointing too?

docs/book/src/releases.md

docs/book/src/user-guide/installation.md

Makefile

ajaysundark · 2026-03-02T09:34:35Z

docs/book/src/releases.md

+To install the controller, apply the `install.yaml` manifest for this version:
+
+```sh
+kubectl apply -f https://github.com/kubernetes-sigs/node-readiness-controller/releases/download/v0.2.0/install.yaml


I suggested an alternate for the published manifests. PTAL.
also, does this PR merge to new branch? seems to be still merging to main.

docs/book/src/releases.md

docs/book/src/user-guide/installation.md

ajaysundark · 2026-03-03T05:54:46Z

/lgtm

ajaysundark · 2026-03-03T06:53:47Z

/approve

Thanks!

ajaysundark · 2026-03-03T06:54:15Z

/hold

ajaysundark · 2026-03-03T06:55:23Z

@AvineshTripathi I added hold for you to continue on rest of the release flow as you progress. Please feel free to unhold this whenever you're ready to publish this.

Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

…metrics, and webhooks, alongside updated documentation. Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

This commit simplifies the published manifests down to 'install.yaml' and 'install-full.yaml'. Co-authored-by: ajaysundar.k <ajaysundar.k@gmail.com> Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

k8s-ci-robot · 2026-03-04T04:31:55Z

New changes are detected. LGTM label has been removed.

ajaysundark

@AvineshTripathi Instead of this triggering v0.2.1 patch release from main, I'm wondering if it's cleaner to just create a followup v0.3.0 release with other changes?

I'm prefering this as this commit is required only for publishing new artifacts. I'll do that manually from main after this PR is merged.

We will plan v0.3.0 picking up 6fa1e93 and other changes after. wdyt?

TODO: please revert the VERSION changes so we can merge this as-is in main for v0.2.0.

ajaysundark · 2026-03-04T18:21:11Z

docs/book/src/releases.md


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

+## v0.2.0


The docs now point to v0.2.0 but we are managing a v0.2.1 release, and leaving a hanging v0.2.0 :/

k8s-ci-robot · 2026-03-04T18:27:16Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AvineshTripathi
Once this PR has been reviewed and has the lgtm label, please ask for approval from ajaysundark. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot · 2026-03-05T18:42:17Z

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

ajaysundark · 2026-03-05T19:17:47Z

This PR has been split into two and merged as discussed offline

/close

k8s-ci-robot · 2026-03-05T19:17:53Z

@ajaysundark: Closed this PR.

Details

In response to this:

This PR has been split into two and merged as discussed offline

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

k8s-ci-robot requested review from dchen1107 and mrunalp February 28, 2026 07:35

k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 28, 2026

AvineshTripathi commented Feb 28, 2026

View reviewed changes

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 1, 2026

ajaysundark reviewed Mar 2, 2026

View reviewed changes

k8s-ci-robot assigned ajaysundark Mar 3, 2026

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2026

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2026

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 3, 2026

AvineshTripathi added 4 commits March 4, 2026 09:48

docs: add v0.2.0 release notes

b00d081

Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

feat(docs): introduce new installation manifests for metrics, secure …

15e416a

…metrics, and webhooks, alongside updated documentation. Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

docs: simplify installation release manifests and update documentation

b28c5e1

This commit simplifies the published manifests down to 'install.yaml' and 'install-full.yaml'. Co-authored-by: ajaysundar.k <ajaysundar.k@gmail.com> Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

bump release version v0.2.1

e79617f

Signed-off-by: AvineshTripathi <avineshtripathi1@gmail.com>

AvineshTripathi force-pushed the release-v0.2.0 branch from 504347e to e79617f Compare March 4, 2026 04:31

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 4, 2026

ajaysundark requested changes Mar 4, 2026

View reviewed changes

k8s-ci-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 4, 2026

This was referenced Mar 4, 2026

feat(Makefile): add tls and webhook installation support to makefile #146

Merged

docs: add installation steps for deploy-full target #147

Merged

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 5, 2026

k8s-ci-robot closed this Mar 5, 2026


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

		## v0.2.0

Conversation

AvineshTripathi commented Feb 28, 2026

Uh oh!

netlify bot commented Feb 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for node-readiness-controller ready!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ajaysundark commented Mar 3, 2026

Uh oh!

ajaysundark commented Mar 3, 2026

Uh oh!

ajaysundark commented Mar 3, 2026

Uh oh!

ajaysundark commented Mar 3, 2026

Uh oh!

k8s-ci-robot commented Mar 4, 2026

Uh oh!

ajaysundark left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

k8s-ci-robot commented Mar 4, 2026

Uh oh!

k8s-ci-robot commented Mar 5, 2026

Uh oh!

ajaysundark commented Mar 5, 2026

Uh oh!

k8s-ci-robot commented Mar 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

netlify bot commented Feb 28, 2026 •

edited

Loading