Andrew O.

@cgruver The rogue PVC is the claim-devworkspace PVC correct? It's very strange that this is getting created, especially given the fact you're using the per-workspace PVC strategy and not the...

@cgruver Do you mind sharing the DevWorkspace Operator logs if possible? They should be logging if the claim-devworkspace PVC is being created. I'm currently trying to reproduce this issue after...

@cgruver Thank you so much for the investigation and helpful information.. this is indeed a strange edge case bug. > The workspaces that it seems to be created for do...

@cgruver Sorry for the delayed reply. I'm still puzzled at this bug & have been preoccupied trying to resolve other tasks :l The fact that I haven't been able to...

@cgruver Thank you so much!! I was finally able to reproduce this myself. To reproduce: 1. Ensure you do not have a common PVC created in your Che user namespace...

@mcz-adhamsabry are you running on an Apple Silicon Mac (e.g. m1, m2, m3...)? Also, are you using Minikube or another variant of Kubernetes? I agree with your assumption that it...

@mcz-adhamsabry after doing a bit of digging, it seems like Che doesn't fully support deploying to k3s yet. This [comment](https://github.com/eclipse-che/che/issues/12973#issuecomment-612829002) might provide some clues on how to get it working,...

@SDAdham Glad to hear :) When things seem to be working as expected, please let us know if you could share any details (e.g. how to turned off single-host) and...

https://github.com/devfile/devworkspace-operator/pull/1321 has now been merged, which seems to [resolve this issue](https://github.com/devfile/devworkspace-operator/pull/1321#issuecomment-2410441654). This change will appear when DevWorkspace Operator 0.32.0 is released.

@tolusha @ibuziuk @dkwon17 let me know if you have any opinions on the suggested approach (or if the alternate approach seems better). I will handle the changes required to Che-Operator.