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
Add optional cluster-name-suffix label support for remote clusters
- Remove ClusterNameSuffix field from Dashboard CRD spec
- Add support for cluster-name-suffix label in remoteClusters clusterLabels
- Suffix is only applied when label is set (opt-in behavior)
- Update config.go to read suffix from resource labels
- Simplify API by removing *WithSuffix functions
- Update tests to use label-based approach
- Update dashboard-shared.yaml to use cluster-name-suffix labels
- Update README documentation with new configuration format
This allows users to manually define custom suffixes per cluster
(e.g., ' (ottawa)', ' [prod]') without template interpolation.
If the label is not set, no suffix is added to service names.
Copy file name to clipboardExpand all lines: README.md
+22-5Lines changed: 22 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -724,16 +724,33 @@ spec:
724
724
- "api.example.com" # API endpoints
725
725
```
726
726
727
-
**Automatic Cluster Tagging:**
728
-
Services from remote clusters automatically get badge tags with the cluster name. Customize colors using the `cluster-tagstyle` label:
727
+
**Cluster Name Suffix:**
728
+
Append custom suffixes to service display names to distinguish items from different clusters. Configure using the `cluster-name-suffix` label in `clusterLabels`:
729
+
730
+
```yaml
731
+
remoteClusters:
732
+
- name: ottawa
733
+
clusterLabels:
734
+
cluster-name-suffix: " (ottawa)" # -> "Service Name (ottawa)"
735
+
# Other formats:
736
+
# " - ottawa" -> "Service Name - ottawa"
737
+
# " [ottawa]" -> "Service Name [ottawa]"
738
+
```
739
+
740
+
This suffix is only applied to items from **remote clusters**, not the local cluster. If the label is not set, no suffix is appended.
741
+
742
+
**Automatic Cluster Tagging (Optional):**
743
+
Services from remote clusters can also get badge tags with the cluster name when `cluster-tagstyle` is set in `clusterLabels`. Available colors:
729
744
- `is-danger`(red) - production
730
745
- `is-warning`(yellow) - staging
731
-
- `is-info`(blue, default) - development
732
-
- `is-success`(green) - QA
746
+
- `is-info`(blue) - development
747
+
- `is-success`(green) - QA/testing
733
748
- `is-light`(gray) - deprecated
734
749
750
+
**Important:** Tags are only added when `cluster-tagstyle` is explicitly configured. You can use both suffix and tags, or just one approach for cluster identification.
751
+
735
752
**Per-Cluster Domain Filtering:**
736
-
Each cluster can have independent `domainFilters` to control which services are discovered. If not specified, inherits from the main `spec.domainFilters`.
753
+
Each cluster can have independent `domainFilters` to control which services are discovered. If not specified for a remote cluster, no domain filtering is applied (all resources pass through). Dashboard-level `spec.domainFilters` only applies to the local cluster.
0 commit comments