Hi Plural team,
I'd like to contribute a net-new local-static-provisioner compatibility scraper under the Contributor Program and am requesting a vouch before opening a PR, per the repository's current gate.
I checked the current static/compatibilities catalog, scraper directory, and all open/closed PRs matching local-static-provisioner / local volume provisioner; I found no existing Plural compatibility entry or prior submission for this add-on.
The implementation is ready for review on the fork:
Scope:
- adds
static/compatibilities/local-static-provisioner.yaml
- adds
utils/compatibility/scrapers/local-static-provisioner.py
- registers the add-on in
static/compatibilities/manifest.yaml and aggregate data
- adds focused parser/scrape/generated-data regression tests
- derives Kubernetes compatibility from the upstream project's published Version Compatibility table rather than inventing ranges
- joins application versions to the published Helm repository where exact chart mappings exist
- fails closed if the Helm chart index cannot be resolved, and preserves already verified chart/image metadata for unchanged chart mappings when the index is only partially available
Authoritative sources:
Validation:
- 10 focused tests pass
- Python compilation passes
- individual table and aggregate compatibility YAML validate against
static/compatibilities/schema.json
- aggregate entry matches the individual table
- live upstream matrix currently resolves v2.9.0/v2.8.0/v2.7.0 to Kubernetes 1.21+
- live Helm index currently maps v2.9.0 -> chart 2.9.0 and v2.8.0 -> chart 2.8.0; older entries map chart 2.0.0 -> app 2.6.0 and chart 1.0.0 -> app 2.5.0, so the scraper only attaches exact published chart mappings to matching matrix releases
git diff --check passes- current broader compatibility test run: 136 passed, with one unrelated existing Argo Rollouts fixture mismatch (
2.43.0 expected vs 2.43.2 already on current master); this contribution does not touch Argo Rollouts
- regression coverage now includes partial Helm-index results preserving previously verified chart/image metadata and rejecting stale images when a chart version changes
AI assistance disclosure: implementation and verification were performed with OpenAI ChatGPT acting for this GitHub account. The eventual PR will retain this disclosure and source links.
This is intended for the README Contributor Program's advertised new-compatibility-scraper tier, subject to maintainer review and merge. Could a write collaborator please !vouch @vuongnguyen150297-commits if this contribution is in scope so CI can run on the submission?
Hi Plural team,
I'd like to contribute a net-new
local-static-provisionercompatibility scraper under the Contributor Program and am requesting a vouch before opening a PR, per the repository's current gate.I checked the current
static/compatibilitiescatalog, scraper directory, and all open/closed PRs matchinglocal-static-provisioner/local volume provisioner; I found no existing Plural compatibility entry or prior submission for this add-on.The implementation is ready for review on the fork:
Scope:
static/compatibilities/local-static-provisioner.yamlutils/compatibility/scrapers/local-static-provisioner.pystatic/compatibilities/manifest.yamland aggregate dataAuthoritative sources:
Validation:
static/compatibilities/schema.jsongit diff --checkpasses2.43.0expected vs2.43.2already on current master); this contribution does not touch Argo RolloutsAI assistance disclosure: implementation and verification were performed with OpenAI ChatGPT acting for this GitHub account. The eventual PR will retain this disclosure and source links.
This is intended for the README Contributor Program's advertised new-compatibility-scraper tier, subject to maintainer review and merge. Could a write collaborator please
!vouch @vuongnguyen150297-commitsif this contribution is in scope so CI can run on the submission?