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).

* 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.

* Filter Kubernetes boards by Release, Cluster, and Namespace.

1. The refresh button will update the board with the current state of the clusters

1. The filtering menu can be used to further constrain the Helm releases shown on each column

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.

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.

1. The*edit properties* button allows you to change again the title of the board as well as a global filter for Helm releases

1. The*remove board* completely deletes the present board from the Codefresh UI

1. The environment details on the environment header are: