• Release Signoff Checklist
• Summary
• Motivation
  • Goals
  • Non-Goals
• Proposal
  • Risks and Mitigations
• Design Details
  • Versioned API Change: NodeStatus v1 core
  • NodeStatus Internal Representation
  • Test Plan
    • Prerequisite testing updates
    • Unit tests
    • Integration tests
    • e2e tests
  • Graduation Criteria
    • Alpha
    • Beta
    • GA
  • Upgrade / Downgrade Strategy
  • Version Skew Strategy
• Production Readiness Review Questionnaire
  • Feature Enablement and Rollback
  • Rollout, Upgrade and Rollback Planning
  • Monitoring Requirements
  • Dependencies
  • Scalability
  • Troubleshooting
• Implementation History
• Drawbacks
• Alternatives

Items marked with (R) are required prior to targeting to a milestone / release.

• (R) Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
• (R) KEP approvers have approved the KEP status as implementable
• (R) Design details are appropriately documented
• (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
  • e2e Tests for all Beta API Operations (endpoints)
  • (R) Ensure GA e2e tests meet requirements for Conformance Tests
  • (R) Minimum Two Week Window for GA e2e tests to prove flake free
• (R) Graduation criteria is in place
  • (R) all GA Endpoints must be hit by Conformance Tests
• (R) Production readiness review completed
• (R) Production readiness review approved
• "Implementation History" section is up-to-date for milestone
• User-facing documentation has been created in kubernetes/website, for publication to kubernetes.io
• Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Deprecate the status.nodeInfo.kubeProxyVersion field of v1.Node

This field is not accurate, the field is set by kubelet, which does not actually know the kube-proxy version, or even if kube-proxy is running.

• Mark status.nodeInfo.kubeProxyVersion deprecated.
• Find any places use it and get them to stop.
• Make kubelet stop setting the field.

• Having kube-proxy itself set status.nodeInfo.kubeProxyVersion. Components should not be trying to figure out what Service features are available based on the kube-proxy version anyway, since some clusters may run an alternative service proxy implementation. If there is a need for a Service proxy feature discovery feature in the future, then that would need to be designed at that time.

• Changing v1.Node validation to require that the field be unset.

The proposal is to deprecate the kubeProxyVersion field of NodeStatus, and to have kubelet set it to an empty string, rather than the kubelet version, in the future.

This field was used by the GCP cloud provider up until 1.28 for the legacy built-in cloud provider (kubernetes #117806, and up until 1.29 for the external cloud-provider (cloud-provider-gcp #533). It may also be used by other components. Thus, we will use a feature gate to protect it until all components are fixed.

Mark the kubeProxyVersion field as Deprecated.

// Deprecated: KubeProxy Version reported by the node.
KubeProxyVersion string `json:"kubeProxyVersion" protobuf:"bytes,8,opt,name=kubeProxyVersion"`

Mark the kubeProxyVersion field as Deprecated.

// Deprecated: KubeProxy Version reported by the node.
KubeProxyVersion string

[x ] I/we understand the owners of the involved components may require updates to existing tests to make this code solid enough prior to committing the changes necessary to implement this enhancement.

• Add a test to TestVersionInfo in pkg/kubelet/nodestatus to see if FeatureGate behaves as expected when it is turned on or off.
• If DisableNodeKubeProxyVersion FeatureGate is enabled:
  • status.nodeInfo.kubeProxyVersion will remain unset if it is initially unset.
  • status.nodeInfo.kubeProxyVersion will be cleared if it is set.
• Else:
  • status.nodeInfo.kubeProxyVersion will be set to the same value as status.nodeInfo.kubeletVersion

• N/A

• N/A

• Created the feature gate, disabled by default.
• Started looking for components that might be using the deprecated field.

• Make sure that upgrades to the Beta version will work across supported levels of version skew.

• No issues reported during two releases.

N/A

• Feature gate (also fill in values in kep.yaml)
  • Feature gate name: DisableNodeKubeProxyVersion
  • Components depending on the feature gate: kubelet

Yes, it makes kubelet stop setting node.status.nodeInfo.kubeProxyVersion.

Yes. Using the featuregate is the only way to enable/disable this feature.

The feature should continue to work just fine.

In addition to the unit tests, we will manually confirm that restarting kubelet with the feature gate toggled has the expected behavior (that it sets kubeProxyVersion if the feature gate is disabled, even if it doesn't also need to set kubeletVersion, and that it clears kubeProxyVersion if the feature gate is enabled).

If there is a component that we didn't know about using kubeProxyVersion, then it may fail in some unknown way when the administrator upgrades to a version with that field disabled. It should be possible to just roll back in this case.

N/A

N/A

No

• N/A

No

No

No

No

No

No

No

- 2023-05-15: Initial draft KEP