You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the request
At the moment storage is being created dynamically, which is not good in a lot of cases: no way to put correct tags, for example.
especially very useful for single nodes, like standalone or license manager.
Expected behavior
there is a way to pass vol-id identifier.
maybe as array(or map), as there maybe several replicas. and in that case field "replicas" may be omitted, if several ids passed.
The text was updated successfully, but these errors were encountered:
this also leads to one of the issues with creating pvc's: no way to extend disks in case it is needed.
You will be forced to recreate ebs.
if somebody will try to edit pvc, so there will be next error:
error: persistentvolumeclaims "pvc-var-splunk-prod-monitoring-console-0" could not be patched: persistentvolumeclaims "pvc-var-splunk-prod-monitoring-console-0" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
@yaroslav-nakonechnikov we will look into this issue and get back to you. have you tried recreating the pvc before , CR is created with the same names?
Please select the type of request
Feature Request
Tell us more
Describe the request
At the moment storage is being created dynamically, which is not good in a lot of cases: no way to put correct tags, for example.
especially very useful for single nodes, like standalone or license manager.
Expected behavior
there is a way to pass vol-id identifier.
maybe as array(or map), as there maybe several replicas. and in that case field "replicas" may be omitted, if several ids passed.
The text was updated successfully, but these errors were encountered: