您为什么不应该在Composer上运行Kubernetes

您为什么不应该在Composer上运行Kubernetes

本文介绍了您为什么不应该在Composer上运行Kubernetes Pod超过一个小时呢?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Cloud Composer文档明确指出:

但是,它没有提供更多的上下文信息,而且我在Kubernetes Python客户端项目上找不到明确相关的问题.

However, it doesn't provide any more context than that, and I can't find a definitively relevant issue on the Kubernetes Python client project.

为了测试它,我跑了一个豆荚两个小时,没有发现任何问题.哪个问题造成了此限制,它如何体现?

To test it, I ran a pod for two hours and saw no problems. What issue creates this restriction, and how does it manifest?

推荐答案

我对Cloud Composer或Kubernetes Python客户端库生态系统并不十分熟悉,但是按大多数评论对GitHub问题跟踪器进行排序显示,该开放项目靠近列表顶部: https://github.com/kubernetes-client/python/issues /492

I'm not deeply familiar with either the Cloud Composer or Kubernetes Python client library ecosystems, but sorting the GitHub issue tracker by most comments shows this open item near the top of the list: https://github.com/kubernetes-client/python/issues/492

听起来好像存在令牌过期问题:

It sounds like there is a token expiration issue:

-@flylo, https://github.com/kubernetes -client/python/issues/492#issuecomment-376581140

这篇关于您为什么不应该在Composer上运行Kubernetes Pod超过一个小时呢?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-01 21:14