kubernetes-sigs/kubectl-validate

Schemas patched at runtime incorrectly set k8s version

eddycharly opened this issue · 3 comments

This PR introduced schema patching at runtime.

When calling ApplySchemaPatches it hardcodes the k8s version to 0.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

/lifecycle frozen

/remove-lifecycle stale