gkarg commented on issue #21087: URL: https://github.com/apache/airflow/issues/21087#issuecomment-1088316897
@cansjt bookmark events being eaten by kubernetes-python is indeed a bug on their side, no arguments here. And I also thank you for digging into it and finding the root cause. > Also consider this: couldn't there be other reasons that would have Kubernetes' API answers with a 410 HTTP Error? I did consider this, and you're likely right! :( However, that's how airflow handled this "traditionally" https://github.com/apache/airflow/blob/2cf1ae30538e109627417e8f0c1650addac3311b/airflow/executors/kubernetes_executor.py#L178 so it's not a new behaviour, just restoration of old (arguably hacky) behaviour. I do agree that this is not a proper solution, just a workaround until something better comes along. > Though, honestly, having to periodically tear down and deploy again Airflow, is a bit of a hassle I feel your pain. BTW, been testing this patch, so far, so good. P.S. Just to be clear, the latest official airflow release 2.2.4 pins kubernetes library to 11.0.0, and thus can not exhibit this behaviour. So people experiencing this bug have likely tinkered with their kubernetes library version (I know I did). So I can't even say this is a critical issue, *yet*. It *will* become critical once next airflow version is released, as the pin was removed in a recent MR (I believe that change is slated for 2.3.0). -- 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]
