feat: Introduce DashboardCNameRecord for custom domain handling in dashboards

This commit is contained in:
Nawaz Dhandala
2026-03-26 16:38:06 +00:00
parent c92e259978
commit b5bf1d6dd1
10 changed files with 51 additions and 18 deletions

View File

@@ -72,6 +72,8 @@ Usage:
value: {{ ternary "true" "false" $provisionSSL | quote }}
- name: STATUS_PAGE_CNAME_RECORD
value: {{ $.Values.statusPage.cnameRecord }}
- name: DASHBOARD_CNAME_RECORD
value: {{ $.Values.dashboard.cnameRecord | default "" }}
- name: ALLOWED_ACTIVE_MONITOR_COUNT_IN_FREE_PLAN
value: {{ $.Values.billing.allowedActiveMonitorCountInFreePlan | quote }}
- name: LOG_LEVEL

View File

@@ -784,6 +784,15 @@
},
"additionalProperties": false
},
"dashboard": {
"type": "object",
"properties": {
"cnameRecord": {
"type": ["string", "null"]
}
},
"additionalProperties": false
},
"probes": {
"type": "object",
"patternProperties": {

View File

@@ -324,6 +324,14 @@ alerts:
statusPage:
cnameRecord:
# If you would like to attach public dashboards to custom domains use this setting.
# Works the same way as statusPage.cnameRecord but for dashboards.
# For example, if you want dashboard.yourcompany.com to show a public dashboard:
# 1. Set the dashboard.cnameRecord to "oneuptime.yourcompany.com"
# 2. Create CNAME record in your DNS provider with the name "dashboard.yourcompany.com" and value "oneuptime.yourcompany.com"
dashboard:
cnameRecord:
probes:
one:
name: "Probe"