Kubernetes Removed API Lint
Runs the same checker as the npm package
@readystack/k8s-removed-api-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
15 checks for the apiVersions kubectl no longer serves, on the manifest open in your editor
Install
k8s-removed-api-lint file
Node 18+. The same 15 rules as the VS Code extension, from a terminal or CI.
Free
- Check the manifest open in the editor against all 15 rules and get the removal release and the replacement apiVersion for every hit - a finished answer for that file, no key
--ruleslists every rule
With a licence ($29 once)
- Sweep every manifest in the workspace and write one dated migration report ordered by removal version - the same 15 rules at repo scope
@readystack/k8s-removed-api-lint --dir ./templates --report html --out report.html
A freelance Kubernetes consultant bills about 120 US dollars an hour, and reading one chart repo for beta apiVersions before an upgrade is most of a day
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "k8s-removed-api-lint": { "command": "npx", "args": ["-y", "@readystack/k8s-removed-api-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Kubernetes Removed API Lint
run: npx -y @readystack/k8s-removed-api-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/k8s-removed-api-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-k8s-removed-api-lint
k8s-removed-api-lint --help
Metadata
Release files for readystack-k8s-removed-api-lint 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_k8s_removed_api_lint-1.0.6.tar.gz | 16.3 kB | Without provenance | Details for readystack_k8s_removed_api_lint-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_k8s_removed_api_lint-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for readystack_k8s_removed_api_lint-1.0.6-py3-none-any.whl |
Total release size: 35.0 kB
Release files / readystack_k8s_removed_api_lint-1.0.6.tar.gz
| Download URL | readystack_k8s_removed_api_lint-1.0.6.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
710c29b002ccb17239a0668c32cadeb0600b3c0af4dccc2f52a655e6f5705f7a
|
|
BLAKE2b-256 checksum How to use checksums |
fb69245de9c59ff6149836c8ca957c06df037029843b7556c50c8a7b418f0331
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_k8s_removed_api_lint-1.0.6-py3-none-any.whl
| Download URL | readystack_k8s_removed_api_lint-1.0.6-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6b5dcd578d10f3f830cc2de22c1f5b0684ee615b95e930672d300517ac3cd24
|
|
BLAKE2b-256 checksum How to use checksums |
a723c9ddde503cfb808b34b3554a4ea9a1dda0235f00e64ade7fc1f06db239ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-k8s-removed-api-lint 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.