-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HELM 创建组件出现异常,有部分 K8S 资源创建失败,但界面显示成功 #1958
Comments
Title: An exception occurred when creating the HELM component. Some K8S resources failed to be created, but the interface displayed success. |
明确的bug,下个版本解决。 |
It is a clear bug and will be solved in the next version. |
5.17.3 版本已发布,经验证问题已解决,我将关闭该 issue ,如果后续有问题再随时打开。 |
Version 5.17.3 has been released, and after verification that the problem has been solved, I will close the issue and reopen it at any time if there are any problems later. |
Describe the bug
When utilizing the Helm model to create the RAM application, errors occur in the creation of K8s sources. However, the UI indicates a successful creation. Running the RAM component gets blocked, with no pods and no logs.
To Reproduce
Steps to replicate the behavior:
On the page 'New -> Helm -> Image Source (Upload)'
Click 'Confirm Creation'
Initiate the component
The page continuously shows 'Starting', and upon inspection, no new pods emerge on k8s, while the k8s resource page indicates a successful creation.
Execute kubectl get deployment -n {Team}; kubectl get deployment -n {Team} common-vaultwarden -o yaml to observe an error message: message: 'pods "common-vaultwarden-6c787c5cb5-" is forbidden: error looking up service account msga-cn/vaultwarden-svc: serviceaccount "vaultwarden-svc" not found'
Describe the bug
当使用 Helm 模型创建 RAM 应用程序时,K8s 资源的创建出现错误。然而,用户界面(UI)显示创建成功。运行 RAM 组件时出现阻塞,没有 Pod 且没有日志。
To Reproduce
kubectl get deployment -n {团队} ; kubectl get deployment -n {团队} common-vaultwarden -o yaml
查看有报错:message: 'pods "common-vaultwarden-6c787c5cb5-" is forbidden: error looking upservice account msga-cn/vaultwarden-svc: serviceaccount "vaultwarden-svc" not
found'
Screenshots

The relevant information:
The text was updated successfully, but these errors were encountered: