VictoriaMetrics / VictoriaMetrics/operator
BUG REPORT : useLegacyNaming doesn't handle correctly PVC naming for vlstorage inside VLCluster object
@AndrewChubatiuk is already working on this.
Since Jul 8, 2026.
- Dominant language
- Go
- Stars
- 589
- Forks
- 229
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 77
Description
Hi all,
Target : migration from Helm deployed victoria-logs-cluster to operator managed VLCluster without disruption
Issue : naming for vlselect and vlinsert deployment is correct and all objects are handled correctly as it seems but with the problem with PVC cannot confirm because operator failed at vlstorage stage
Descrpition :
problem with PVC name : iwith helm the pvc are build with the name : vlstorage-volume-<app_name>-vlstorage-<idx_sts> and operator even with useLegacyNaming flag build the PVC name like : vlstorage-db-<app_name>-vlstorage-<idx_sts>
Attended result : when useLegacyNaming is set PVC names are the same than with helm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.