Mario Loriedo

@dkwon17 can we close this issue? I am asking to decide if we can include it in 7.53 release notes

@metlos good point. We definitely need to label the target secrets/configmaps as `app.kubernetes.io/managed-by: che` and `app.kubernetes.io/created-by: che-server` or something like that. However I think we can leave the how to...

Related to https://github.com/eclipse/che/issues/13611

/remove-lifecycle stale

@tolusha this is the issue you are currently working on right?

Honestly that doesn't seams like a big deal as usually developers fork a GitHub repository and `git push` to their fork rather than to a dedicated branch of the upstream...

Hi @Divine1 we need more logs to figure out what's going on. Can you please look at following when the workspaces is starting: - the DW pod logs: (`DW="cbfsel-repo"; kubectl...

It looks like there is no PersistentVolume in your cluster that matches the PersistentVolumeClaim created by Che, hence the PVC remains unbound. You may want to decrease the `m2volume` size...

@AObuchow do you have any clue about the PVC problem above?

Closing. We will implement missing parts of the spec when there is a real request.