You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/deploy-to-kubernetes/environment-dashboard.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,17 +69,14 @@ caption="Creating an environment from the GUI"
69
69
max-width="50%"
70
70
%}
71
71
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
+
72
76
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/).
73
77
74
78
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).
75
79
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
-
83
80
##Understanding cluster issues
84
81
85
82
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.