Skip to content

Support configuring the minimum TLS version #3140

Open

Description

@brendandburns

Problem

This client does not expose a way to set the TLS minimum version used for API connections. KubeConfig.applySecurityAuthentication() maps only a subset of TLS options, and createDispatcherOptions() does not pass minVersion to its dispatcher/connector. This prevents applications with TLS 1.3-only compliance requirements from enforcing that policy for Kubernetes API connections.

This is also being raised for client-go in kubernetes/kubernetes#143817.

Requested behavior

Add a documented way to configure the TLS minimum version (including TLS 1.3), preserve the current runtime default when unset, and apply it consistently to direct, HTTP-proxy, and SOCKS connections.

Acceptance criteria

  • Add a unit test first that sets the TLS minimum version and asserts it reaches the transport options used by each supported dispatcher path.
  • Run the new test against the existing code and verify that it fails for the missing option.
  • Commit the failing test separately from the implementation.
  • Implement the option and ensure the new test passes; commit the fix separately from the test.
  • Document the configuration and its default behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions