RobertIndie opened a new issue, #1546:
URL: https://github.com/apache/streampipes/issues/1546

   ### Apache StreamPipes version
   
   dev (current development state)
   
   ### Affected StreamPipes components
   
   Backend, Connect, Processing Elements, UI
   
   ### What happened?
   
   When running `helm upgrade streampipes ./` to upgrade the helm chart, it 
will throw errors:
   ```
   Error: UPGRADE FAILED: cannot patch "backend-pvc" with kind 
PersistentVolumeClaim: PersistentVolumeClaim "backend-pvc" is invalid: spec: 
Forbidden: spec is immutable after creation except resources.requests for bound 
claims
     core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "50Mi", Format: 
"BinarySI"}}},
        VolumeName:       "pvc-a85d92d5-ab2f-4500-9d22-326629e3365b",
   -    StorageClassName: &"hostpath",
   +    StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        DataSourceRef:    nil,
     }
    && cannot patch "consul-pvc" with kind PersistentVolumeClaim: 
PersistentVolumeClaim "consul-pvc" is invalid: spec: Forbidden: spec is 
immutable after creation except resources.requests for bound claims
     core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "20M", Format: 
"DecimalSI"}}},
        VolumeName:       "pvc-89730b87-f414-48a9-b842-58a677f2ddb6",
   -    StorageClassName: &"hostpath",
   +    StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        DataSourceRef:    nil,
     }
    && cannot patch "couchdb-pvc" with kind PersistentVolumeClaim: 
PersistentVolumeClaim "couchdb-pvc" is invalid: spec: Forbidden: spec is 
immutable after creation except resources.requests for bound claims
     core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "50M", Format: 
"DecimalSI"}}},
        VolumeName:       "pvc-1f227581-aa7c-4ed4-a30f-3c2abc302118",
   -    StorageClassName: &"hostpath",
   +    StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        DataSourceRef:    nil,
     }
    && cannot patch "influxdb-pvc" with kind PersistentVolumeClaim: 
PersistentVolumeClaim "influxdb-pvc" is invalid: spec: Forbidden: spec is 
immutable after creation except resources.requests for bound claims
     core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "250Mi", 
Format: "BinarySI"}}},
        VolumeName:       "pvc-e1f7a48e-5c10-4d57-90c5-6a95d5eab867",
   -    StorageClassName: &"hostpath",
   +    StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        DataSourceRef:    nil,
     }
    && cannot patch "influxdb2-pvc" with kind PersistentVolumeClaim: 
PersistentVolumeClaim "influxdb2-pvc" is invalid: spec: Forbidden: spec is 
immutable after creation except resources.requests for bound claims
     core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "250Mi", 
Format: "BinarySI"}}},
        VolumeName:       "pvc-776895f1-3137-4853-b02a-22eae07f7cc7",
   -    StorageClassName: &"hostpath",
   +    StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        DataSourceRef:    nil,
     }
   ```
   
   ### How to reproduce?
   
   1. Deploy the streampipes according to 
https://github.com/apache/streampipes/blob/dev/installer/k8s/README.md
   2. Upgrade the helm chart by executing `helm upgrade streampipes ./`.
   
   ### Expected behavior
   
   _No response_
   
   ### Additional technical information
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   None


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to