skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lvms:check-release-readiness

Validate LVMS release branches, Go and Kubernetes dependency versions, and CSI alignment.

7|15|Updated Jan 23, 2026
Search Tags:#lvms#release readiness#dependency validation#kubernetes versioning#topolvm sync#csi compatibility#upstream branch checks
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-check-release-readiness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lvms:check-release-readiness
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/lvms/skills/check-release-readiness
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-check-release-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken LVMS releases by catching missing or mismatched prereqs early, such as absent release branches, incorrect dependency versions, and stale fork syncs.

Core Features & Use Cases

  • Branch and dependency verification: Confirms required release branches exist and that Go/Kubernetes dependency versions align with the target Kubernetes release.
  • CSI and TopoLVM compatibility checks: Validates CSI dependency k8s.io versions and ensures the TopoLVM replacement and upstream sync are recent enough.
  • Release readiness report: Produces a structured readiness report with an overall status and actionable next steps for any pending items.

Quick Start

Run the readiness check for release version 4.21 targeting Kubernetes 1.34 by using: /lvms:check-release-readiness --version 4.21 --k8s 1.34

Frequently Asked Questions about lvms:check-release-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify LVMS release readiness before tagging a new version?▼

To verify LVMS release readiness, run a single command that validates release branches, Go and Kubernetes dependency versions, CSI k8s.io alignment, and TopoLVM replacement and sync freshness. It generates a categorized report with actionable next steps for any pending items.

What prerequisites cause broken LVMS releases?▼

Broken LVMS releases are caused by missing or mismatched prerequisites such as absent release branches, incorrect Go or Kubernetes dependency versions, stale TopoLVM fork syncs, and misaligned CSI k8s.io versions.

How do I check TopoLVM sync freshness and CSI compatibility for openshift/lvm-operator?▼

You can check TopoLVM sync freshness and CSI compatibility by running a readiness validation that parses upstream or local go.mod/Makefile/config files and uses GitHub APIs to ensure TopoLVM replacement and upstream sync are recent enough for openshift/lvm-operator.

Can I use this release readiness check for both openshift/lvm-operator and openshift/topolvm?▼

Yes, the release readiness check applies to both openshift/lvm-operator and openshift/topolvm across CI-prep and dependency-update workflows, validating branch existence and dependency alignment for each repository.

How do I validate Kubernetes versioning and Go dependencies for a target LVMS release?▼

To validate Kubernetes versioning and Go dependencies, pass the target release version and Kubernetes version as arguments. The check reads go.mod and Makefile data to confirm dependency versions align with the target Kubernetes release.

What does the LVMS readiness report include when prerequisites are not met?▼

The LVMS readiness report includes an overall status and categorized actionable next steps for any pending items, detailing which release branches, dependency versions, or TopoLVM syncs require attention before tagging.

Related Skills

Explore More Software Engineering Skills→
redhat-best-practices-for-k8sredhat-best-practices-for-k8s

xcrypto-scan

Scan go.mod files for outdated golang.org/x/crypto versions and advisories.

Official
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
TermiX-officialTermiX-official
109

prepare-pr

Rebase GitHub pull requests onto main and push prepared changes.

Official
Intermediate
tomazbtomazb
2

openshift-lvm-storage

Manage LVM Storage lifecycle on OpenShift with TopoLVM CSI volumes.

Community
Advanced