它还导致NUATNIX在平台顶部启用K8S API一致解决方案所做的事情。我认识到,我们可以作为客户作为K8S运行时分层,但类似于我们在利用BOSH的Pivotal LeveraL of Day 2 K8工作的情况下,似乎对集成选项有需求。机构存储知识确实可以将状态的集合提升到一个新的水平,而与雅典卫城有很多相似之处。
我知道在服务编排方面可能会与平静重叠,但是K8S已成为编排容器提供的应用程序的DefaTso语言。
最好的答案阿基姆
\r\n
\r\nI'd like to clarify this:
\r\n
\r\nRedHat is part of the Technical Support Alliance Network, like many vendors and editors. https:\/\/tsanet.org\/members\/
\r\n
\r\nRedHat Support policy for third party platforms<\/a>, hence running RHEL as guest OS on AHV, is pretty clear: They will provide you support according to your entitlement and if they think AHV is the root cause, they will get in contact with Nutanix through the Technical Support Alliance Network.
\r\n
\r\nIf you have any reason to think this is not working, or if you have found any document suggesting otherwise, please let us know.
\r\n
\r\nIf for any reason, you have any doubt when you need to open a case, you can open it at Nutanix who will help you sort it out, and get in contact with RH via TSANET if it's necessary, and work together with you and RedHat to help you.
\r\n
\r\nHope this clarifies the situation.","className":"post__content__best_answer"}">