Nutanix Karbon上的Tillerless Helm |Nutanix社区 - 伟德1964手机,伟德国际19

Get a free certification exam when you complete a training course now through August 16! <\/strong><\/h3>
\u00a0<\/p>
Level up your Nutanix skills and get certified for free with Nutanix University Summer School! For the next two months, anyone who completes one of the following courses - whether it\u2019s online or in person - will also receive a FREE certification exam voucher.<\/span><\/p>
Eligible courses:<\/strong><\/p>
\t
Enterprise Cloud Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix Data Services Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix End User Computing Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix Database Management & Automation<\/span><\/p>\t<\/li>\t
\t
Nutanix Multicloud Automation Administration<\/span><\/p>\t<\/li><\/ul>
\u00a0<\/p>
Take this opportunity to invest in your career and grow your skill set.\u00a0<\/span><\/p>
\u00a0<\/h3>
Get started today!<\/a><\/h3>
\u00a0<\/p>
Thanks for waiting to everyone who got our sneak peek of this last week!\u00a0\ud83d\ude09<\/p>
\u00a0<\/p>
Terms and Conditions<\/strong><\/em><\/p>
\t
The exam voucher will be provided to you after you have completed the course. Self-paced online student\u2019s vouchers will be assigned through the Learning Plan within 24-hours after the completion of the course.<\/span><\/em><\/p>\t<\/li>\t
\t
You must complete the course between June 14, 2022 and August 16, 2022.\u00a0<\/span><\/em><\/p>\t<\/li>\t
\t
For online students, your exam voucher must be redeemed by 8\/23\/22. For instructor-led students, your exam voucher must be redeemed 6 months after you complete the course.\u00a0<\/span><\/em><\/p>\t<\/li>\t
\t
The exam voucher code can only be used once.<\/span><\/em><\/p>\t<\/li>\t
\t
You will receive one (1) NCP exam voucher for each class completed. The voucher can be used on any NCP exam.\u00a0\u00a0<\/span><\/em><\/p>\t<\/li><\/ul>
\u00a0<\/p>
This article was written by Karlie Beil, Customer Marketing Specialist.\u00a0<\/p><\/div><\/div><\/section>
\u00a0<\/p>
\u00a9\ufe0f\ufe0f\ufe0f 2022 Nutanix, Inc. \u00a0All rights reserved. Nutanix, the Nutanix logo and all Nutanix product, feature and service names mentioned herein are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. Other brand names mentioned herein are for identification purposes only and may be the trademarks of their respective holder(s). This post may contain links to external websites that are not part of Nutanix.com. Nutanix does not control these sites and disclaims all responsibility for the content or accuracy of any external site. Our decision to link to an external site should not be considered an endorsement of any content on such a site. This post may contain express and implied forward-looking statements, which are not historical facts and are instead based on our current expectations, estimates and beliefs. The accuracy of such statements involves risks and uncertainties and depends upon future events, including those that may be beyond our control, and actual results may differ materially and adversely from those anticipated or implied by such statements. Any forward-looking statements included herein speak only as of the date hereof and, except as required by law, we assume no obligation to update or otherwise revise any of such forward-looking statements to reflect subsequent events or circumstances.<\/p>
\u00a0<\/p>","id":40952,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/78f47513-ef06-4bf4-9b57-0269259ac6da_thumb.png","label":"Blog","replyCount":0,"views":3766,"post":{"id":61291,"author":{"id":113632,"url":"\/members\/karlie-beil-113632","name":"Karlie Beil","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/1581aab3-bcf6-49f4-b2fb-3d11e8c010dc.png","userTitle":"Community Manager","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Community Manager","color":"#0873ba"},"userLevel":2},"content":"
Get a free certification exam when you complete a training course now through August 16! <\/strong><\/h3>
\u00a0<\/p>
Level up your Nutanix skills and get certified for free with Nutanix University Summer School! For the next two months, anyone who completes one of the following courses - whether it\u2019s online or in person - will also receive a FREE certification exam voucher.<\/span><\/p>
Eligible courses:<\/strong><\/p>
\t
Enterprise Cloud Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix Data Services Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix End User Computing Administration<\/span><\/p>\t<\/li>\t
\t
Nutanix Database Management & Automation<\/span><\/p>\t<\/li>\t
\t
Nutanix Multicloud Automation Administration<\/span><\/p>\t<\/li><\/ul>
\u00a0<\/p>
Take this opportunity to invest in your career and grow your skill set.\u00a0<\/span><\/p>
\u00a0<\/h3>
Get started today!<\/a><\/h3>
\u00a0<\/p>
Thanks for waiting to everyone who got our sneak peek of this last week!\u00a0\ud83d\ude09<\/p>
\u00a0<\/p>
Terms and Conditions<\/strong><\/em><\/p>
\t
The exam voucher will be provided to you after you have completed the course. Self-paced online student\u2019s vouchers will be assigned through the Learning Plan within 24-hours after the completion of the course.<\/span><\/em><\/p>\t<\/li>\t
\t
You must complete the course between June 14, 2022 and August 16, 2022.\u00a0<\/span><\/em><\/p>\t<\/li>\t
\t
For online students, your exam voucher must be redeemed by 8\/23\/22. For instructor-led students, your exam voucher must be redeemed 6 months after you complete the course.\u00a0<\/span><\/em><\/p>\t<\/li>\t
\t
The exam voucher code can only be used once.<\/span><\/em><\/p>\t<\/li>\t
\t
You will receive one (1) NCP exam voucher for each class completed. The voucher can be used on any NCP exam.\u00a0\u00a0<\/span><\/em><\/p>\t<\/li><\/ul>
\u00a0<\/p>
This article was written by Karlie Beil, Customer Marketing Specialist.\u00a0<\/p><\/div><\/div><\/section>
\u00a0<\/p>
\u00a9\ufe0f\ufe0f\ufe0f 2022 Nutanix, Inc. \u00a0All rights reserved. Nutanix, the Nutanix logo and all Nutanix product, feature and service names mentioned herein are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. Other brand names mentioned herein are for identification purposes only and may be the trademarks of their respective holder(s). This post may contain links to external websites that are not part of Nutanix.com. Nutanix does not control these sites and disclaims all responsibility for the content or accuracy of any external site. Our decision to link to an external site should not be considered an endorsement of any content on such a site. This post may contain express and implied forward-looking statements, which are not historical facts and are instead based on our current expectations, estimates and beliefs. The accuracy of such statements involves risks and uncertainties and depends upon future events, including those that may be beyond our control, and actual results may differ materially and adversely from those anticipated or implied by such statements. Any forward-looking statements included herein speak only as of the date hereof and, except as required by law, we assume no obligation to update or otherwise revise any of such forward-looking statements to reflect subsequent events or circumstances.<\/p>
\u00a0<\/p>","url":"\/education-blog-153\/level-up-your-nutanix-skills-this-summer-and-get-a-free-exam-voucher-40952?postid=61291#post61291","creationDate":"2022-06-14T15:30:05+0000","relativeCreationDate":"21 days ago"},"contentType":"article","type":3,"likes":4,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

今年夏天提高您的Nutanix技能，并获得免费的考试凭证！

21天前

社区

混合云基础架构

Karbon Kubernetes编排

nutanix karbon上的无舵头

nutanix karbon上的无舵头

3年前
2018年12月2日

2个答复

3301意见

UserLevel 4

+5

乔森纳克斯

Nutanix员工

80个答复

什么是头盔？

Helm是一种简化IT操作团队如何安装和管理Kubernetes应用程序的工具。您可以将其视为Linux（APT/YUM）中的软件包经理，但对于Kubernetes来说。

什么是舵图？

Helm图只是包含Kubernetes应用程序的软件包。这类似于您首选的Linux发行版上的.deb/.rpm软件包。

什么是舵机用例？

如果您想知道为什么使用Helm是个好主意，这里有一些原因：

大多数受欢迎的软件都有掌舵图表，可促进其在Kubernetes上的安装

如果您想共享自己的kubernetes应用程序，那么掌舵图是要走的方式

部署过程中的一致性是一个关键方面，图表带来了您的应用程序的可重复性构建

Kubernetes应用程序是一组清单文件。图表可帮助您管理这些Kubernetes清单文件的复杂性

管理Helm套件的版本

掌舵建筑

来自Helm网站：

Helm有两个部分：客户端（Helm）和服务器（Tiller）

Tiller在Kubernetes群集内部运行，并管理图表的版本（安装）。

Helm在笔记本电脑，CI/CD或您想要运行的任何地方运行。

图表是至少包含两件事的舵机包：

*包装的描述（Chart.yaml）
*一个或多个模板，其中包含kubernetes清楚文件

图表可以存储在磁盘上，也可以从远程图表存储库中获取（例如Debian或Redhat软件包）

Tiller（Helm Server）周围的安全问题

Tiller负责管理Kubernetes应用程序的版本。蒂勒（Tiller）在kubernetes群集上使用root Access运行，这带来了极大的风险，并且有人可以未经授权访问您的服务器。

这种安全风险将在未来的Helm V3版本中解决。在新版本发布之前，我们有一种方法可以减轻Helm V2的风险。

耕种以营救！

Tillerless是由Rimas Mocevicius在Jfrog。简而言之，此插件的作用是在工作站或CI/CD管道上本地运行分er，而无需在Kubernetes簇上安装分erer。

安装

在您开始使用Tillerless Helm Sportination之前，重要的是kubectl和Kubeconfig文件正确配置并在计算机上工作。Helm Client对Kubeconfig文件具有依赖性。

掌舵客户

首先安装Helm Client（Helm）。我建议您遵循步骤这个链接对于您的操作系统平台。就我而言，我是MacOS用户，所以我使用Homebrew来安装Helm。

酿造安装kubernetes-helm

初始头盔

确保您用正确的标志初始化头盔，- 仅愿意。如果您不这样做，则将安装在Kubernetes群集上。

Helm Init-仅愿意
输出：
$ helm_home已在/users/jose.gomez/.helm上配置。由于设置了愉快的Helming，因此未安装Tiller，因为“只有客户”的标志！

安装Tillerless插件

使用Helm初始化的下一步是安装Tillerless插件。请记住，此插件将使Tiller可以在您的工作站上运行，而不是Kubernetes群集。

Helm插件安装https://github.com/rimusz/helm-tiller
我们已经准备好开始使用无辫子的头盔了。

在本地使用插件

默认情况下，Tillerless在本地和命名空间开始Kube-System。您可以从不同的名称空间开始，但请确保以前存在Kubernetes名称空间。在这篇文章中，我们使用了Tillerless使用的默认名称空间，Kube-System。

舵蒂勒开始
输出：
已安装的Helm版本v2.9.1复制/usr/usr/local/bin/tiller到Helm-Tiller/bin Helm和Tiller是同一版本！启动分er ... tiller名称空间：kube-system
已经打开了一个新的外壳，您可以以安全的方式运行任何Helm命令。为了本文的目的，我们将部署领事图以检查所有正在运行的内容。

舵机安装 - 名字领事稳定/领事
输出：
姓名：领事上次部署：12月2日14：03：00 2018 2018名称空间：默认状态：部署资源：==> v1beta1/statefulset名称所需的当前年龄领事3 1 0S ==> v1beta1/poddisisportionbudgetbudtionbudgetbudget name name name name bassion baste wassion wassion wassion wassion wassion washe wassion washe wassion washe年龄领事pdb n/a 1 0 0S ==> v1/pod（相关）名称ready status starts age consul-0 0/1待定0 0S ==> v1/秘密名称类型数据类型consul-gossip-keye opaque 10S ==> v1/configmap名称数据年龄领事考试1 0S ==> v1/服务名称类型cluster-ip外部-IP端口（S）年龄领事集群无8500/tcp，8400/tcp，8301/tcp，8301，8301/UDP，8302/TCP，8302/UDP，8300/TCP，8600/TCP，8600/UDP 0S Consul-UI NodePort 172.19.19.210.185 8500：31820/TCP 0S注意：1。注意所有集群成员。$ kubectl get pods -namespace =默认值-W 2.使用Helm Test测试群集健康。$ HELM TEST CONSUL 3.（可选）手动确认领事群集健康。$ consul_pod = $（kubectl get pods -l ='发行= consul' - output = jsonpath = {。items [0] .metadata.name}）$ kubectl exec $ consul_pod consul_pod consul consul consul consul -namespace = default = default | default |GREP服务器
完全部署领事大约需要五分钟。您可以使用以下命令检查状态：

掌舵测试领事 - 清洁
当领事准备就绪时，上一个命令应具有以下输出。你会得到通过部署完成后消息。

跑步：Consul-UI测试YHT8O通过：领事-UI检验YHT8O
下一步是检查已分配了哪些端口领事服务。您可以在图表安装输出上获取信息。检查其服务部分。

==> v1/服务名称类型类型cluster-ip外部-IP端口（S）年龄领事集群无8500/tcp，8400/tcp，8301/tcp，8301/udp，8302/tcp，8302，8302/udp，8300/tcp，8300/tcp，，83008600/TCP，8600/UDP 1M CONSUL-UI NODEPORT 172.19.210.185 8500：31820/TCP 1M
在我的情况下领事港口8500已与港口映射31820。打开网络浏览器，并使用您的一位工人和映射端口的IP地址。快速获取您的工人IP地址的方法。

kubectl获取节点-O yaml |GREP地址
输出：
地址： - 地址：10.10.56.161-地址：Tillerless-F42DCF-K8S-Master-0地址： - 地址：10.10.56.162-地址：Tillerless-F42DCF-K8S-Worker-0
这里是领事部署的屏幕截图

完成掌舵任务后，您可以关闭外壳并停止分er服务。

退出舵手耕种停止

结论

凭借不懈的头盔，您无需在Kubernetes群集上安装分erer或为其创建任何类型的RBAC。通过这种方法，您可以获得一种安全的方式来部署头盔图表。

1个附件

何塞·戈麦斯（Jose Gomez）|技术营销工程师|jose.gomez@nutanix.com |@pipoe2H

AHV

容器

舵

What is Helm?<\/h2>
Helm is a tool that simplifies how your IT operation team install and manage Kubernetes applications. You could consider it like a package manager in Linux (apt\/yum) but for Kubernetes.
\u00a0<\/p>
What is a Helm chart?<\/h2>
A Helm chart is just a package that contains the Kubernetes application. This is similar to a .deb\/.rpm package on your preferred Linux distribution.
\u00a0<\/p>
What are the Helm use cases?<\/h2>
If you are wondering why use Helm is a good idea, here some of the reasons:<\/p>
Most of the popular software has a Helm chart to facilitate its installation on Kubernetes<\/li>\t
If you are looking to share your own Kubernetes application, a Helm chart is the way to go<\/li>\t
Consistency during deployments is a key aspect, charts bring reproducible builds of your applications<\/li>\t
Kubernetes applications are a group of manifest files. A chart helps you to manage the complexity of those Kubernetes manifest files<\/li>\t
Manage releases of Helm packages<\/li><\/ul>
Helm architecture<\/h2>
From Helm website:<\/p>
Helm has two parts: a client (helm) and a server (tiller)<\/em><\/li>\t
Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts.<\/em><\/li>\t
Helm runs on your laptop, CI\/CD, or wherever you want it to run.<\/em><\/li>\t
Charts are Helm packages that contain at least two things:<\/em><\/li><\/ul>
* A description of the package (Chart.yaml)<\/em>
* One or more templates, which contain Kubernetes manifest files<\/em><\/p>
\u00a0<\/p>
Charts can be stored on disk, or fetched from remote chart repositories (like Debian or RedHat packages)<\/em><\/li><\/ul>
\u00a0<\/p>
$\"fa2af93e-44da-4ba4-a8b4-e39215f61a03.png\"$ <\/a><\/p>
\u00a0<\/p>
\u00a0<\/p>
Security concern around Tiller (Helm Server)<\/h2>
Tiller is responsible for managing the releases of your Kubernetes Apps. Tiller runs with root access on your Kubernetes cluster what poses a great risk, and someone can get unauthorised access to your server.

This security risk is addressed on the future Helm v3 release. Until the new version is out, we have a way to mitigate this risk on Helm v2.<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
Tillerless to the rescue!<\/h2>
Tillerless is a Helm plug-in developed by Rimas Mocevicius<\/a> at Jfrog. In a nutshell what this plug-in does is to run Tiller locally on your workstation or in CI\/CD pipelines without installing Tiller on your Kubernetes clusters.<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
Installation<\/h2>
Before you start with the Tillerless Helm installation it is important you have kubectl<\/strong> and the kubeconfig<\/strong> file properly configured and working on your machine. Helm client has a dependency with the kubeconfig file.<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
Helm client<\/h3>First install the Helm client (helm). I recommend you to follow the steps on this link<\/a> for your OS platform. In my case I\u2019m a macOS user so I\u2019m using Homebrew to install Helm.

brew install kubernetes-helm <\/code><\/p>
\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>
Initialise Helm<\/h3>Make sure you initialise Helm with the right flag, --client-only<\/strong>. If you don\u2019t do it Tiller will be installed on your Kubernetes cluster. helm init --client-only <\/code> Output: $HELM_HOME has been configured at \/Users\/jose.gomez\/.helm. Not installing Tiller due to 'client-only' flag having been set Happy Helming! <\/code><\/p> \u00a0<\/p> \u00a0<\/p>
Install Tillerless plug-in<\/h3>With Helm initialised the next step is to install the Tillerless plug-in. Remember, this plug-in will make Tiller to run on your workstation instead of the Kubernetes cluster. helm plugin install https:\/\/github.com\/rimusz\/helm-tiller <\/code> We are ready to start using Tillerless Helm.<\/p> \u00a0<\/p> \u00a0<\/p>
\u00a0<\/h3>\u00a0<\/p>
Using the plug-in locally<\/h3>
Tillerless by default starts locally and with the namespace kube-system<\/strong>. You can start with a different namespace, but make sure the Kubernetes namespace previously exists. On this post we are using the default namespace used by Tillerless, kube-system<\/strong>.

helm tiller start <\/code> Output: Installed Helm version v2.9.1 Copied found \/usr\/local\/bin\/tiller to helm-tiller\/bin Helm and Tiller are the same version! Starting Tiller... Tiller namespace: kube-system <\/code> A new shell has been opened where you can run on a secure manner any helm command. For the purpose of this post we are going to deploy the Consul chart to check everything is running. helm install --name consul stable\/consul <\/code> Output: NAME: consul LAST DEPLOYED: Sun Dec 2 14:03:00 2018 NAMESPACE: default STATUS: DEPLOYED RESOURCES: ==> v1beta1\/StatefulSet NAME DESIRED CURRENT AGE consul 3 1 0s ==> v1beta1\/PodDisruptionBudget NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE consul-pdb N\/A 1 0 0s ==> v1\/Pod(related) NAME READY STATUS RESTARTS AGE consul-0 0\/1 Pending 0 0s ==> v1\/Secret NAME TYPE DATA AGE consul-gossip-key Opaque 1 0s ==> v1\/ConfigMap NAME DATA AGE consul-tests 1 0s ==> v1\/Service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE consul ClusterIP None 8500\/TCP,8400\/TCP,8301\/TCP,8301\/UDP,8302\/TCP,8302\/UDP,8300\/TCP,8600\/TCP,8600\/UDP 0s consul-ui NodePort 172.19.210.185 8500:31820\/TCP 0s NOTES: 1. Watch all cluster members come up. $ kubectl get pods --namespace=default -w 2. Test cluster health using Helm test. $ helm test consul 3. (Optional) Manually confirm consul cluster is healthy. $ CONSUL_POD=$(kubectl get pods -l='release=consul' --output=jsonpath={.items[0].metadata.name}) $ kubectl exec $CONSUL_POD consul members --namespace=default | grep server <\/code> It takes about five minutes to fully deploy Consul. You can check the status with the following command: helm test consul --cleanup <\/code> When Consul is ready the previous command should have the following output. You will get the PASSED<\/em> message once the deployment is done. RUNNING: consul-ui-test-yht8o PASSED: consul-ui-test-yht8o <\/code> Next step is to check what port has been assigned to the consul-ui<\/strong> service. You can get the information on the chart installation output. Check the service section of it. ==> v1\/Service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE consul ClusterIP None 8500\/TCP,8400\/TCP,8301\/TCP,8301\/UDP,8302\/TCP,8302\/UDP,8300\/TCP,8600\/TCP,8600\/UDP 1m consul-ui NodePort 172.19.210.185 8500:31820\/TCP 1m <\/code> On my case the consul-ui<\/strong> port 8500<\/em> has been mapped with the port 31820<\/em>. Open a web browser and use the IP address of one of your workers and your mapped port. A quick way to get your worker IP addresses. kubectl get node -o yaml | grep address <\/code> Output: addresses: - address: 10.10.56.161 - address: tillerless-f42dcf-k8s-master-0 addresses: - address: 10.10.56.162 - address: tillerless-f42dcf-k8s-worker-0 <\/code> Here a screenshot for the Consul deployment with Tireless Helm<\/p>
<\/a><\/p>
When you have finished with your Helm tasks you can close the shell and stop the Tiller service. exit helm tiller stop <\/code><\/p>
Conclusion<\/h2>With Tireless Helm you don\u2019t have the need to install Tiller on your Kubernetes cluster or create any kind of RBAC for it. With this approach you get a secure way to deploy your Helm charts.<\/p> \u00a0<\/p> \u00a0<\/p>","quoteUsername":"JoseNutanix","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}"> 喜欢引用分享
该主题已关闭以供评论 2个答复最古老的第一新的先来最佳投票 C cprey 旅行者 1回复 3年前 2019年6月6日这真的很好。我们很高兴能够以Nutanix的方式运行Kubernetes ...没有管理安装和升级的难以忍受的O＆M。我无法使插件正常工作……可能是由于舵手和分er进行破坏的变化。看来社区建议在本地运行舵手和耕种。这篇文章让我朝正确的方向走了这么大的方向谢谢为了那个原因！启动仅掌舵客户代码： Helm Init-仅愿意开始分erer 代码： tiller＆设置Helm Host Env var。代码：导出helm_host = localhost：44134 \r\n \r\nI was not able to get the plugin working...likely due to Helm and Tiller making breaking changes. It appears the community recommends running helm and tiller locally. This post got me going in the right direction so big THANKS<\/b> for that! \r\n \r\nstart helm client-only \r\ncode:<\/b>helm init --client-only <\/pre><\/div> \r\nstart tiller \r\ncode:<\/b>tiller & <\/pre><\/div> \r\nset HELM HOST env var. \r\ncode:<\/b>export HELM_HOST=localhost:44134 <\/pre><\/div>","quoteUsername":"cprey","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}"> 喜欢引用 UserLevel 7 +34 阿卢西亚尼更 338个答复 2年前 2019年10月31日感谢分享 @cprey 在Twitter上关注我：https：//twitter.com/angeloluciani Thanks for sharing @cprey<\/user-mention>\u00a0 <\/p>","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}"> 喜欢引用
由内部提供动力条款和条件注册已经有一个帐户？登录使用您的帐户登录登录社区使用您的帐户登录输入您的用户名或电子邮件地址。我们将向您发送带有指令的电子邮件以重置您的密码。用户名或电子邮件返回概述扫描病毒文件。抱歉，我们仍在检查该文件的内容，以确保它可以安全下载。请在几分钟后再试一次。好的该文件无法下载抱歉，我们的病毒扫描仪检测到该文件无法安全下载。好的 Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic Functional","cookiepolicy.modal.level2":"Normal Functional + analytics","cookiepolicy.modal.level3":"Complete Functional + analytics + social media + embedded videos"}}}">

\u00a0<\/h3>

\u00a0<\/h3>

什么是头盔？

什么是舵图？

什么是舵机用例？

掌舵建筑

Tiller（Helm Server）周围的安全问题

耕种以营救！

安装

掌舵客户

初始头盔

安装Tillerless插件

在本地使用插件

结论

1个附件

What is a Helm chart?<\/h2>A Helm chart is just a package that contains the Kubernetes application. This is similar to a .deb\/.rpm package on your preferred Linux distribution.\u00a0<\/p>

注册

登录社区

扫描病毒文件。

该文件无法下载

What is a Helm chart?<\/h2>
A Helm chart is just a package that contains the Kubernetes application. This is similar to a .deb\/.rpm package on your preferred Linux distribution.
\u00a0<\/p>