Modernize networking layer internals for future compatibility #2388
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This small PR updates the internal REST client's response handling (
kubernetes.client.rest.RESTResponse
) to address aDeprecationWarning
originating from theurllib3
library (version >= 2.0).The underlying
urllib3.HTTPResponse.getheaders()
method is deprecated and scheduled for removal inurllib3
v2.1.0. This PR replaces its usage with the recommended direct access to the.headers
attribute.This change resolves the deprecation warning observed during testing and ensures future compatibility of the Kubernetes Python client with upcoming versions of
urllib3
.Warning example:
Which issue(s) this PR fixes:
Special notes for your reviewer:
This change directly addresses the
DeprecationWarning
concerningHTTPResponse.getheaders()
as reported in CI logs and local testing. The fix involves switching from the deprecatedgetheaders()
method call to accessing the.headers
attribute on the underlyingurllib3
response object within ourRESTResponse
wrapper class.Does this PR introduce a user-facing change?