IP/CIDR validation improvements

[danwinship]

Enhancement Description

• One-line enhancement description (can be used as a release note): Improvements to validation of IP addresses and CIDR values.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4858-ip-cidr-validation
• Discussion Link: Tighten IP/CIDR validation kubernetes#122550 has background; I am belatedly writing a KEP to centralize further discussion and because it will just be easier to track this work with a KEP.
• Primary contact (assignee): @danwinship
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y): 1.36
  • Stable release target (x.y): 1.38
• Alpha (1.33)
  • KEP (k/enhancements) update PR(s): KEP-4858: IP/CIDR Validation Improvements #4899
  • Code (k/k) update PR(s):
    • Tighten IP/CIDR validation kubernetes#122550
    • warn on bad IPs in objects kubernetes#128786
    • Canonicalize IPs written out by controllers kubernetes#130101
  • Docs (k/website) update PR(s): KEP-4858: Add StrictIPCIDRValidation feature gate file website#49942
• Beta (1.36)
  • KEP (k/enhancements) update PR(s): KEP-4858: update StrictIPCIDRValidation to Beta #5781, KEP-4858: fix status #5909
  • Code (k/k) update PR(s): KEP-4858: update StrictIPCIDRValidation to Beta kubernetes#137053
  • Docs (k/website) update(s): Update StrictIPCIDRValidation for Beta website#54723
• Stable (1.38)
  • KEP (k/enhancements) update PR(s): Update KEP-4858 IP/CIDR validation to GA #6337
  • Code (k/k) update PR(s): KEP-4858 IP/CIDR Validation to GA kubernetes#141979
  • Docs (k/website) update(s): Update the version data on some SIG Network feature gates website#57469
• Cleanup (1.41)
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[danwinship]

/sig network
/assign

[k8s-triage-robot]

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

[danwinship]

/remove-lifecycle stale

[danwinship]

/remove-lifecycle stale
/label lead-opted-in
/milestone v1.33

targeting alpha for 1.33