Skip to content

BUG REPORT : useLegacyNaming doesn't handle correctly PVC naming for vlstorage inside VLCluster object #2385

Description

@ccaillet1974

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

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions