kaxil opened a new pull request, #68041: URL: https://github.com/apache/airflow/pull/68041
## What Allow the `kubernetes` and `kubernetes_asyncio` clients on the 36.x line in the `cncf.kubernetes` provider: - `kubernetes`: `>=35.0.0,<36.0.0` -> `>=35.0.0,!=36.0.0,<37.0.0` - `kubernetes_asyncio`: `>=32.0.0,<36.0.0` -> `>=32.0.0,<37.0.0` ## Why `35.0.0` is the only release in the previous `[35.0.0, 36.0.0)` range, and it ignores `NO_PROXY`/`no_proxy`: `Configuration.__init__` loads the value from the environment and then resets it to `None` ([kubernetes-client/python#2520](https://github.com/kubernetes-client/python/issues/2520)). Behind a corporate proxy this forces in-cluster API-server traffic through `HTTP(S)_PROXY`, so `KubernetesPodOperator`, the hooks, and the Kubernetes executor time out reaching the cluster. The fix only landed in the 36.x client, which the previous bound excluded, so there was no proxy-respecting version installable in range. `36.0.0` is excluded from the range: it shipped an in-cluster auth regression where `load_incluster_config()` writes `api_key['authorization']` while `auth_settings()` expects `api_key['BearerToken']`, sending in-cluster calls unauthenticated ([#2582](https://github.com/kubernetes-client/python/issues/2582), [#2584](https://github.com/kubernetes-client/python/issues/2584)). It is fixed in `36.0.1`. `kubernetes_asyncio` could not move before because it had no 36.x release; `36.1.0` is now available, so the async bound aligns with the sync one. ## Validation The provider unit suite passes against `kubernetes==36.0.1` + `kubernetes_asyncio==36.1.0` (1111 passed, 17 skipped; all provider modules import; 1128 tests collected with no errors). CI integration tests exercise the real-cluster paths (watch, auth, serialization) that the unit tests mock. Closed #67845 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
