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

Commitd02cd84

Browse files
committed
Update environment dashboard
Added new options for Helm and K8s app definitions, and replaced screenshot
1 parentaab5082 commitd02cd84

File tree

3 files changed

+5
-9
lines changed

3 files changed

+5
-9
lines changed

‎_docs/deploy-to-kubernetes/environment-dashboard.md‎

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -69,17 +69,14 @@ caption="Creating an environment from the GUI"
6969
max-width="50%"
7070
%}
7171

72+
When you create an environment for your application, you can define the following:
73+
* Helm boards: Namespace, Cluster, and Release. Namespace is useful when you have more than one Helm release per namespace, or you have the same Helm release in more than one namespace.
74+
* Kubernetes boards: Release, Cluster, and Namespace.
75+
7276
Once you create the environment, Codefresh will pull automatically the status of pods/deployments/services from the cluster and show it at the environment status bar. To link specific pipelines to that environment follow the[env syntax guide]({{site.baseurl}}/docs/codefresh-yaml/deployment-environments/).
7377

7478
You can also combine the two ways by first creating an environment in the GUI and then associating it with a pipeline. But notice that in that case the environment details you selected in the GUI must**EXACTLY** match those defined in the pipeline (so that the pipeline can detect which environment entry it should update).
7579

76-
##Filtering environments boards
77-
78-
* Filter Helm boards by Namespace, Cluster, and Release. The Namespace filter is useful when you have more than one Helm release per namespace, or you have the same Helm release in more than one* namespace.
79-
* Filter Kubernetes boards by Release, Cluster, and Namespace.
80-
81-
82-
8380
##Understanding cluster issues
8481

8582
There is no restriction to the number of pipelines linked to an environment (and the number of environments affected by a single pipeline). In fact the true power of the environment dashboard becomes evident when you link multiple pipelines to a single environment.

‎_docs/new-helm/helm-environment-promotion.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -251,8 +251,7 @@ max-width="80%"
251251

252252

253253
1. The refresh button will update the board with the current state of the clusters
254-
1. The filtering menu can be used to further constrain the Helm releases shown in each column. You can filter by Namespace, Cluster and Release.
255-
Filtering by Namespace is useful when you have more than one Helm release per namespace or you have the same Helm release in more than one namespace.
254+
1. The filtering menu can be used to further constrain the Helm releases shown in each column.
256255
1. The*edit properties* button allows you to change again the title of the board as well as a global filter for Helm releases
257256
1. The*remove board* completely deletes the present board from the Codefresh UI
258257
1. The environment details on the environment header are:
-43.3 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp