Its been reported to me from a 3rd party that an update of the package to the latest 0.4.0 release of the python-k8sclient resolves this issue for them. They've been running for at least 24 hours and have not seen this traceback occur in any of their workloads.
Its been reported to me from a 3rd party that an update of the package to the latest 0.4.0 release of the python-k8sclient resolves this issue for them. They've been running for at least 24 hours and have not seen this traceback occur in any of their workloads.