Kubernetes Grafana仪表板不适用于入口
我已经安装在kube prometheus stack下面,在尝试使用Grafana仪表板自己的入口URL访问它时出错。我相信我在这里遗漏了一些愚蠢的东西,但找不到任何线索。我已经看过这里和其他地方 图表:kube-prometheus-stack-9.4.5 应用程序版本:0.38.1 当我导航到URL时,我会被重定向到以下消息 对grafana/values.yaml所做的更改:Kubernetes Grafana仪表板不适用于入口,kubernetes,prometheus,grafana,Kubernetes,Prometheus,Grafana,我已经安装在kube prometheus stack下面,在尝试使用Grafana仪表板自己的入口URL访问它时出错。我相信我在这里遗漏了一些愚蠢的东西,但找不到任何线索。我已经看过这里和其他地方 图表:kube-prometheus-stack-9.4.5 应用程序版本:0.38.1 当我导航到URL时,我会被重定向到以下消息 对grafana/values.yaml所做的更改: grafana.ini: server: # The full public facing url y
grafana.ini:
server:
# The full public facing url you use in browser, used for redirects and emails
root_url: https://myorg.grafanatest.com
进行上述更改后,用于安装普罗米修斯·格拉法纳操作员的舵指令
helm install pg kube-prometheus-stack/ -n monitoring
我在grafana pod中的grafana.ini文件中看到以下设置
[analytics]
check_for_updates = true
[grafana_net]
url = https://grafana.net
[log]
mode = console
[paths]
data = /var/lib/grafana/data
logs = /var/log/grafana
plugins = /var/lib/grafana/plugins
provisioning = /etc/grafana/provisioning
[server]
root_url = https://myorg.grafanatest.com/
您需要从parent charts values.yaml编辑
## Using default values from https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
##
#### This below line is in 509 line
grafana:
enabled: true
namespaceOverride: ""
## Deploy default dashboards.
##
defaultDashboardsEnabled: true
adminPassword: prom-operator
ingress:
## If true, Grafana Ingress will be created
##
enabled: true
## Annotations for Grafana Ingress
##
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
## Labels to be added to the Ingress
##
labels: {}
## Hostnames.
## Must be provided if Ingress is enable.
##
# hosts:
# - grafana.domain.com
hosts:
- myorg.grafanatest.com
## Path for grafana ingress
path: /
到grafana.ingres.enabled
true
addgrafana.ingres.hosts
-myorg.grafanatest.com
希望能帮助您您需要从父图表中编辑值。yaml
## Using default values from https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
##
#### This below line is in 509 line
grafana:
enabled: true
namespaceOverride: ""
## Deploy default dashboards.
##
defaultDashboardsEnabled: true
adminPassword: prom-operator
ingress:
## If true, Grafana Ingress will be created
##
enabled: true
## Annotations for Grafana Ingress
##
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
## Labels to be added to the Ingress
##
labels: {}
## Hostnames.
## Must be provided if Ingress is enable.
##
# hosts:
# - grafana.domain.com
hosts:
- myorg.grafanatest.com
## Path for grafana ingress
path: /
到grafana.ingres.enabled
true
addgrafana.ingres.hosts
-myorg.grafanatest.com
希望能帮助您在这里发布解决方案,因为它现在正在运行。按照上面提到的gumelaragum的步骤创建values.yaml并更新其中的以下值,并将该values.yaml传递给helm安装步骤。不知道为什么它在没有从子路径启用SERVICE_的情况下不起作用,但它现在可以工作了。请注意,我没有启用入口部分,因为我已经在安装过程之外创建了入口路由
helm show values prometheus com/kube prometheus stack>custom values.yaml
然后通过在custom-values.yaml中更改以下值来安装。根据需要更改名称空间
helm-n监控安装-f./custom-values.yaml pg prometheus com/kube prometheus stack
grafana:
enabled: true
namespaceOverride: ""
# set pspUseAppArmor to false to fix Grafana pod Init errors
rbac:
pspUseAppArmor: false
grafana.ini:
server:
domain: mysb.grafanasite.com
#root_url: "%(protocol)s://%(domain)s/"
root_url: https://mysb.grafanasite.com/grafana/
serve_from_sub_path: true
## Deploy default dashboards.
##
defaultDashboardsEnabled: true
adminPassword: prom-operator
ingress:
## If true, Grafana Ingress will be created
##
enabled: false
## Annotations for Grafana Ingress
##
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
## Labels to be added to the Ingress
##
labels: {}
## Hostnames.
## Must be provided if Ingress is enable.
##
# hosts:
# - grafana.domain.com
hosts:
- mysb.grafanasite.com
## Path for grafana ingress
path: /grafana/
我在grafana容器装载路径(/etc/grafana/grafana.ini)内的grafana.ini文件中看到了相同的值
在此处发布解决方案,因为它正在工作。按照上面提到的gumelaragum的步骤创建values.yaml并更新其中的以下值,并将该values.yaml传递给helm安装步骤。不知道为什么它在没有从子路径启用SERVICE_的情况下不起作用,但它现在可以工作了。请注意,我没有启用入口部分,因为我已经在安装过程之外创建了入口路由
helm show values prometheus com/kube prometheus stack>custom values.yaml
然后通过在custom-values.yaml中更改以下值来安装。根据需要更改名称空间
helm-n监控安装-f./custom-values.yaml pg prometheus com/kube prometheus stack
grafana:
enabled: true
namespaceOverride: ""
# set pspUseAppArmor to false to fix Grafana pod Init errors
rbac:
pspUseAppArmor: false
grafana.ini:
server:
domain: mysb.grafanasite.com
#root_url: "%(protocol)s://%(domain)s/"
root_url: https://mysb.grafanasite.com/grafana/
serve_from_sub_path: true
## Deploy default dashboards.
##
defaultDashboardsEnabled: true
adminPassword: prom-operator
ingress:
## If true, Grafana Ingress will be created
##
enabled: false
## Annotations for Grafana Ingress
##
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
## Labels to be added to the Ingress
##
labels: {}
## Hostnames.
## Must be provided if Ingress is enable.
##
# hosts:
# - grafana.domain.com
hosts:
- mysb.grafanasite.com
## Path for grafana ingress
path: /grafana/
我在grafana容器装载路径(/etc/grafana/grafana.ini)内的grafana.ini文件中看到了相同的值
我按照上面的步骤进行操作,仍然得到了与Grafana URL相同的消息。我不得不为Grafana部分添加rbac:pspUseAppArmor:false以及入口和主机更改。由于我们使用Traefike ingress,我也尝试将ingress设置为false,但没有成功。使用grafani.ini文件内容更新,检查是否有任何问题。如果使用kubectl port forward to grafanam di,仪表板错误?我在本次安装中没有尝试,但在不同设置中测试时,端口转发确实起作用,在没有入口的情况下,我按照上面的步骤进行操作,仍然得到了与Grafana URL相同的消息。我不得不为Grafana部分添加rbac:pspUseAppArmor:false以及入口和主机更改。由于我们使用Traefike ingress,我也尝试将ingress设置为false,但没有成功。使用grafani.ini文件内容更新,检查是否有任何问题。如果使用kubectl port forward to grafanam di,仪表板错误?我在本次安装中没有尝试,但在不同设置中测试时,端口转发确实起作用,没有适当的入口。
[analytics]
check_for_updates = true
[grafana_net]
url = https://grafana.net
[log]
mode = console
[paths]
data = /var/lib/grafana/data
logs = /var/log/grafana
plugins = /var/lib/grafana/plugins
provisioning = /etc/grafana/provisioning
[server]
domain = mysb.grafanasite.com
root_url = https://mysb.grafanasite.com/grafana/
serve_from_sub_path = true