Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit47ac877

Browse files
committed
Update using-helm-in-codefresh-pipeline.md
1 parent0ce4777 commit47ac877

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

‎_docs/new-helm/using-helm-in-codefresh-pipeline.md‎

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,6 @@ caption="Name of Kubernetes cluster"
5454
max-width="70%"
5555
%}
5656

57-
<!--- If you are still using Helm 2 make sure also that your Kubernetes cluster has the server part of Helm installed (called Tiller).
58-
The easiest way to do that is to run `helm init` from the command shell of your cloud provider or
59-
any other terminal that has access to your cluster via `kubectl`. This process is not needed if you use Helm 3.-->
6057

6158
To verify that your cluster is setup for Helm select the*Helm Releases* item from the left sidebar in the Codefresh UI. You should see the[Helm releases]({{site.baseurl}}/docs/new-helm/helm-releases-management/) in your cluster or an empty screen if you just started using Helm.
6259

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp