From 3afa3ee7c6cabe7eb9671f7d7eaf06f443ffd99e Mon Sep 17 00:00:00 2001 From: geekpi Date: Fri, 9 Nov 2018 08:48:09 +0800 Subject: [PATCH 1/2] translated --- ...athering Kubernetes resource statistics.md | 77 ------------------- ...athering Kubernetes resource statistics.md | 74 ++++++++++++++++++ 2 files changed, 74 insertions(+), 77 deletions(-) delete mode 100644 sources/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md create mode 100644 translated/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md diff --git a/sources/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md b/sources/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md deleted file mode 100644 index 50db9d728d..0000000000 --- a/sources/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md +++ /dev/null @@ -1,77 +0,0 @@ -translating---geekpi - -KRS: A new tool for gathering Kubernetes resource statistics -====== -Zero-configuration tool simplifies gathering information, such as how many pods are running in a certain namespace. -![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/tools_hardware_purple.png?itok=3NdVoYhl) - -Recently I was in New York giving a talk at O'Reilly Velocity on the topic of [troubleshooting Kubernetes apps][1] and, motivated by the positive feedback and great discussions on the topic, I decided to revisit tooling in the space. It turns out that, besides [kubernetes-incubator/spartakus][2] and [kubernetes/kube-state-metrics][3], we don't really have much lightweight tooling available to collect resource stats (such as the number of pods or services in a namespace). So, I sat down on my way home and started coding on a little tool—creatively named **krs** , which is short for Kubernetes Resource Stats—that allows you to gather these stats. - -You can use [mhausenblas/krs][5] in two ways: - - * directly from the command line (binaries for Linux, Windows, and MacOS are available); and - * in cluster, as a deployment, using the [launch.sh][4] script, which creates the appropriate role-based access control (RBAC) permissions on the fly. - - - -Mind you, it's very early days, and this is heavily a work in progress. However, the 0.1 release of **krs** offers the following features: - - * In a per-namespace basis, it periodically gathers resource stats (supporting pods, deployments, and services). - * It exposes these stats as metrics in the [OpenMetrics format][6]. - * It can be used directly via binaries or in a containerized setup with all dependencies included. - - - -In its current form, you need to have **kubectl** installed and configured for **krs** to work, because **krs** relies on a **kubectl get all** command to be executed to gather the stats. (On the other hand, who's using Kubernetes and doesn't have **kubectl** installed?) - -Using **krs** is simple; [Download][7] the binary for your platform and execute it like this: - -``` -$ krs thenamespacetowatch -# HELP pods Number of pods in any state, for example running -# TYPE pods gauge -pods{namespace="thenamespacetowatch"} 13 -# HELP deployments Number of deployments -# TYPE deployments gauge -deployments{namespace="thenamespacetowatch"} 6 -# HELP services Number of services -# TYPE services gauge -services{namespace="thenamespacetowatch"} 4 -``` - -This will launch **krs** in the foreground, gathering resource stats from the namespace **thenamespacetowatch** and outputting them respectively in the OpenMetrics format on **stdout** for you to further process. - -![krs screenshot][9] - -Screenshot of krs in action. - -But Michael, you may ask, why isn't it doing something useful (such as storing 'em in S3) with the metrics? Because [Unix philosophy][10]. - -For those wondering if they can directly use Prometheus or [kubernetes/kube-state-metrics][3] for this task: Well, sure you can, why not? The emphasis of **krs** is on being a lightweight and easy-to-use alternative to already available tooling—and maybe even being slightly complementary in certain aspects. - -This was originally published on [Medium's ITNext][11] and is reprinted with permission. - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/18/11/kubernetes-resource-statistics - -作者：[Michael Hausenblas][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/mhausenblas -[b]: https://github.com/lujun9972 -[1]: http://troubleshooting.kubernetes.sh/ -[2]: https://github.com/kubernetes-incubator/spartakus -[3]: https://github.com/kubernetes/kube-state-metrics -[4]: https://github.com/mhausenblas/krs/blob/master/launch.sh -[5]: https://github.com/mhausenblas/krs -[6]: https://openmetrics.io/ -[7]: https://github.com/mhausenblas/krs/releases -[8]: /file/412706 -[9]: https://opensource.com/sites/default/files/uploads/krs_screenshot.png (krs screenshot) -[10]: http://harmful.cat-v.org/cat-v/ -[11]: https://itnext.io/kubernetes-resource-statistics-e8247f92b45c diff --git a/translated/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md b/translated/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md new file mode 100644 index 0000000000..8bde9d0556 --- /dev/null +++ b/translated/tech/20181101 KRS- A new tool for gathering Kubernetes resource statistics.md @@ -0,0 +1,74 @@ +KRS：一个收集 Kubernetes 资源统计数据的新工具 +====== +零配置工具简化了信息收集，例如在某个命名空间中运行了多少个 pod。 +![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/tools_hardware_purple.png?itok=3NdVoYhl) + +最近我在纽约的 O'Reilly Velocity 就 [Kubernetes 应用故障排除][1]的主题发表了演讲，并且在积极的反馈和讨论的推动下，我决定重新审视这个领域的工具。结果，除了 [kubernetes-incubator/spartakus][2] 和 [kubernetes/kube-state-metrics][3] 之外，我们还没有太多的轻量级工具来收集资源统计数据（例如命名空间中的 pod 或服务）。所以，我在回家的路上开始编写一个小工具 - 创造性地命名为 **krs**，它是 Kubernetes Resource Stats 的简称 ，它允许你收集这些统计数据。 + +你可以通过两种方式使用 [mhausenblas/krs][5]： + + * 直接在命令行（有 Linux、Windows 和 MacOS 的二进制文件），以及 +  * 在集群中使用 [launch.sh][4] 脚本部署，该脚本动态创建适当的基于角色的访问控制 （RBAC） 权限。 + + +提醒你，它还在早期，并且还在开发中。但是，**krs** 的 0.1 版本提供以下功能： + + * 在每个命名空间的基础上，它定期收集资源统计信息（支持 pod、部署和服务）。 +  * 它以 [OpenMetrics 格式][6]公开这些统计。 +  * 它可以直接通过二进制文件使用，也可以在包含所有依赖项的容器化设置中使用。 + + + +目前，你需要安装并配置 **kubectl**，因为 **krs** 依赖于执行 **kubectl get all** 命令来收集统计数据。（另一方面，谁会使用 Kubernetes 但没有安装 **kubectl**？） + +使用 **krs** 很简单。[下载][7]适合你平台的二进制文件，并按如下方式执行： + +``` +$ krs thenamespacetowatch +# HELP pods Number of pods in any state, for example running +# TYPE pods gauge +pods{namespace="thenamespacetowatch"} 13 +# HELP deployments Number of deployments +# TYPE deployments gauge +deployments{namespace="thenamespacetowatch"} 6 +# HELP services Number of services +# TYPE services gauge +services{namespace="thenamespacetowatch"} 4 +``` + +这将在前台启动 **krs**，从名称空间 **thenamespacetowatch** 收集资源统计信息，并分别在**标准输出**中以 OpenMetrics 格式输出它们，以供你进一步处理。 + +![krs screenshot][9] + +krs 实战截屏 + +也许你会问，Michael，为什么不做一些有用的事（例如将指标存储在 S3 中）？因为 [Unix 哲学][10] + +对于那些想知道他们是否可以直接使用 Prometheus 或 [kubernetes/kube-state-metrics][3] 来完成这项任务的人：是的，你可以，为什么不行呢？ **krs** 的重点是作为已有工具的轻量级且易于使用的替代品 - 甚至可能在某些方面略微互补。 + +本文最初发表在 [Medium 的 ITNext][11] 上，并获得授权转载。 + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/18/11/kubernetes-resource-statistics + +作者：[Michael Hausenblas][a] +选题：[lujun9972][b] +译者：[geekpi](https://github.com/geekpi) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/mhausenblas +[b]: https://github.com/lujun9972 +[1]: http://troubleshooting.kubernetes.sh/ +[2]: https://github.com/kubernetes-incubator/spartakus +[3]: https://github.com/kubernetes/kube-state-metrics +[4]: https://github.com/mhausenblas/krs/blob/master/launch.sh +[5]: https://github.com/mhausenblas/krs +[6]: https://openmetrics.io/ +[7]: https://github.com/mhausenblas/krs/releases +[8]: /file/412706 +[9]: https://opensource.com/sites/default/files/uploads/krs_screenshot.png (krs screenshot) +[10]: http://harmful.cat-v.org/cat-v/ +[11]: https://itnext.io/kubernetes-resource-statistics-e8247f92b45c From 1992b612521dbfcfc10477912f3ff9f7f6004b53 Mon Sep 17 00:00:00 2001 From: geekpi Date: Fri, 9 Nov 2018 08:51:45 +0800 Subject: [PATCH 2/2] translating --- ...End Sync Support For All Filesystems Except Ext4 on Linux.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sources/talk/20180811 Dropbox To End Sync Support For All Filesystems Except Ext4 on Linux.md b/sources/talk/20180811 Dropbox To End Sync Support For All Filesystems Except Ext4 on Linux.md index 7d471f42bb..a10bffc707 100644 --- a/sources/talk/20180811 Dropbox To End Sync Support For All Filesystems Except Ext4 on Linux.md +++ b/sources/talk/20180811 Dropbox To End Sync Support For All Filesystems Except Ext4 on Linux.md @@ -1,3 +1,5 @@ +translating---geekpi + Dropbox To End Sync Support For All Filesystems Except Ext4 on Linux ====== Dropbox is thinking of limiting the synchronization support to only a handful of file system types: NTFS for Windows, HFS+/APFS for macOS and Ext4 for Linux.