[GitHub] [airflow] mik-laj commented on pull request #20759: Remove RefreshConfiguration workaround for K8s token refreshing

[GitBox <gi...@apache.org>]

mik-laj commented on pull request #20759:
URL: https://github.com/apache/airflow/pull/20759#issuecomment-1007846780


   This is a bit of a risky change, and I wonder if we should wait until we have at least one release that is compatible with a wide range of Kubernetes Client versions ie. until a provider package is released that is compatible with a old and a new version of Kubernetes client versions. See: https://github.com/apache/airflow/pull/18797
   
   After we release a package that includes this change, we can release another package that will only be compatible with the new versions of the K8s client to avoid having to upgrade the kubernetes client and the provider package simultaneously. It especially makes sense that this change only includes code cleanup and we are under no pressure to merge it quickly. We can wait for users to test new versions of k8s clients and return to us with feedback.
   
   What do you think? Do we need to merge it quickly or can we wait for the compatibility with the new version of the k8s client to mature?
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org