Grafana Admin Credentials Sourcing from PVC Instead of Secret
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- helm, kubernetes
- 领域
- devops, infrastructure
调研方向
从 values.yaml 配置开始，并使用文档中记录的 helm upgrade --install 命令复现部署。检查渲染后的 chart 配置和现有 PVC 的状态，以确定使用的是哪个凭据源。当使用现有 PVC 的部署通过 devlake-grafana-secret 中的凭据完成身份验证时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Description:
We are using DevLake's Helm chart to deploy Grafana in our Kubernetes cluster. However, despite configuring Grafana to use a pre-existing Kubernetes secret for the admin credentials, it appears that Grafana is still sourcing the admin credentials from the PVC. This is causing login issues where the password from the PVC is used instead of the password stored in the secret.
Steps to Reproduce:
Deployment Configuration: We have the following configuration in values.yaml:
persistence:
type: pvc
enabled: false
# storageClassName: default
accessModes:
- ReadWriteOnce
size: 10Gi
# annotations: {}
finalizers:
- kubernetes.io/pvc-protection
admin:
existingSecret: "devlake-grafana-secret"
userKey: admin-user
passwordKey: admin-password
Secret Creation: We have already created the secret (devlake-grafana-secret) with the following credentials:
kubectl create secret generic devlake-grafana-secret \
--from-literal=admin-user="admin" \
--from-literal=admin-password="yourStrongPassword"
Deployment: We then deploy or upgrade the Helm chart using the following command:
helm upgrade --install devlake-grafana grafana/grafana -f values.yaml
Login Attempt: After deployment, when we try to log in to Grafana using the admin user and the password (yourStrongPassword), we are unable to authenticate.
Expected Behavior:
- Use the admin credentials from the Kubernetes secret (devlake-grafana-secret) as configured in the values.yaml.
- Not use the credentials from the PVC, which are incorrect or outdated.
Actual Behavior:
Despite correctly configuring the secret in the values.yaml file, Grafana seems to be sourcing the admin credentials from the PVC, causing a failed login with the password stored in the PVC instead of the password defined in the secret.
I mentioned that it's using the PVC values because the PVC wasn’t deleted. The password currently working is the one that was set during the initial installation.
Impact:
Inability to login with the expected admin credentials (from the secret).
We are unable to authenticate as the admin user using the correct credentials.
Environment:
DevLake Version: 1.0.3-beta1
- 主要语言
- Go Template
- 星标
- 53
- 派生
- 72
- 平均合并
- 1 天 16 小时
- 30 天内合并 PR
- 2
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/devlake-helm-chart 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
apache/devlake-helm-chart#367 · 6 条评论 · 2 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 75/100
apache/devlake-helm-chart#366 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 48/100
apache/devlake-helm-chart#381 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 48/100
apache/devlake-helm-chart#374 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
apache/devlake-helm-chart#373 · 1 条评论 ·
查看 apache/devlake-helm-chart 的全部 Issue
相似的 Issue
-
push_gh-pages fails on master branch on forks可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭good first issue infrastructure
难度 2/5 1-3 小时 新手友好度 76/100
kuznia-rdzeni/coreblocks#1135 ·
-
automation models
难度 1/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
[Bug] Chatwoot v4.19.0 – Super Admin returns 500 due to missing superadmin.scss Vite manifest entry未关闭Bug
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
paperclipai/paperclip#17379 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
spliit-app/spliit#684 ·
维护者通常 3 天内回复