[英]Is Fabric8 for kubernetes client deprecated?
I've seen the fabric8 documentation and it says that fabric8 is already deprecated.我看过fabric8文档,它说fabric8 已经被弃用了。
I would like to know if is recommendable to use this API or is better to use the official Kubernetes client I started using fabric8, but now I wonder if I have to switch to the official API我想知道是否推荐使用这个API 还是使用官方的Kubernetes 客户端更好 我开始使用fabric8,但现在我想知道是否必须切换到官方的ZDB974238714CA8DE614FZA7CE1D083
I'm one of the maintainers of Fabric8 Kubernetes Client.我是 Fabric8 Kubernetes Client 的维护者之一。 Let me provide some background about the project and it's current status.
让我提供一些有关该项目的背景及其当前状态。
Back in 2015, the main Fabric8 platform project was quite active.早在 2015 年, Fabric8 主要平台项目就相当活跃。 At that time, Fabric8 project's vision was to be a PaaS platform for Cloud Native Micro-services running on top of Kubernetes.
当时,Fabric8 项目的愿景是成为一个运行在 Kubernetes 之上的云原生微服务的 PaaS 平台。 Fabric8 Kubernetes Client provided a key role in Fabric8 ecosystem as it provided as an abstraction over Kubernetes REST API.
Fabric8 Kubernetes 客户端在 Fabric8 生态系统中发挥了关键作用,因为它作为 Kubernetes RESTA81447CACED1871 的抽象提供Although the Fabric8 project was liked and appreciated by many people in the open source community, due to unfortunate reasons it could not become successful, and the idea of Fabric8 as an integrated development platform on top of Kubernetes died.
尽管 Fabric8 项目在开源社区受到了很多人的喜爱和赞赏,但由于不幸的原因未能成功,Fabric8 作为 Kubernetes 之上的集成开发平台的想法也夭折了。
Although the main project is archived, there are several repositories that are still active and used by the community, such as Fabric8 Docker Maven Plugin , Fabric8 Kubernetes Client and Fabric8 Maven Plugin (now known as Eclipse JKube ). Although the main project is archived, there are several repositories that are still active and used by the community, such as Fabric8 Docker Maven Plugin , Fabric8 Kubernetes Client and Fabric8 Maven Plugin (now known as Eclipse JKube ). These projects are still quite active due to their usages as general purpose Docker/Kubernetes tools/libraries.
这些项目仍然非常活跃,因为它们用作通用 Docker/Kubernetes 工具/库。
Now coming to Fabric8 Kubernetes Client , it's very far from being a deprecated/archived project.现在来到Fabric8 Kubernetes 客户端,它远不是一个弃用/存档的项目。 It has an extremely active community (check GitHub issues/release cycles).
它有一个非常活跃的社区(检查 GitHub 问题/发布周期)。 It's even integrated into Java Operator SDK and Strimzi Kafka Operator .
它甚至被集成到Java Operator SDK和Strimzi Kafka Operator中。 If you check the number of users, it's one of the most popular Kubernetes Client libraries (after client-go).
如果您检查用户数量,它是最流行的 Kubernetes 客户端库之一(在 client-go 之后)。
I have written a blogpost about feature differences between Fabric8 and Official Kubernetes Client: Difference between Fabric8 and Official Kubernetes Java Client .我写了一篇关于 Fabric8 和官方 Kubernetes 客户端的功能差异的博文: Fabric8 和官方 Kubernetes Java 客户端之间的区别。 It might help you in deciding which client would be better suited for your use case.
它可能会帮助您确定哪个客户端更适合您的用例。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.