install error
- Dominant language
- Java
- Stars
- 2k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
my k8s version is v1.25.6+k3s1
error message:
helm install sreworks ./ --create-namespace --namespace sreworks --set global.accessMode="nodePort" --set appmanager.home.url="http://127.0.0.1:30767" --set saas.onlyBase=true
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "local-path-provisioner-role" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "sreworks"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "sreworks"
Contributor guide
Research direction
Start by reproducing the reported helm install command on Kubernetes v1.25.6+k3s1 and inspect the chart resources related to the existing ClusterRole local-path-provisioner-role. Determine how the chart should handle that pre-existing resource, then verify that installation completes without the ownership metadata error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100