Andrew O.

Note: the [usersettings code](https://github.com/openshift/console/commit/c5c4ffe157cae5029760dafe1e82394110ee3659) makes a special case for `kube:admin` and simply uses the value `kubeadmin` [instead](https://github.com/openshift/console/commit/c5c4ffe157cae5029760dafe1e82394110ee3659) of its hashed-then-hex'ed representation. I'm not sure if there was a particular reason...

This issue is now no longer required, see https://github.com/redhat-developer/web-terminal-operator/issues/162#issuecomment-2206400246

> @AObuchow @dkwon17 so, if I understand correctly, the suggestion is - exclude the command from the devfile task list using hard-coded id. correct? @RomanNikitenko Correct :) I think this...

> With this PR: [devfile/devworkspace-operator#1329](https://github.com/devfile/devworkspace-operator/pull/1329), the command ids are now: `init-ssh-agent-command-1`, `init-ssh-agent-command-2`, ..., etc. > > Please see: https://github.com/devfile/devworkspace-operator/pull/1329/files#r1809335501 @RomanNikitenko With these changes, maybe a regex should be used to...

> I think the next time we have a similar need - we could consider adding an attribute for commands that should not be displayed on the UI. This way...

This bug somewhat resembles https://github.com/eclipse-che/che/issues/23103#issuecomment-2299334154, which occurs on a Kubernetes (K3s) cluster. However, for that bug, the issue occurs with the empty workspace sample which uses the UDI - so...

Linking this [comment](https://github.com/eclipse-che/che/issues/22880#issuecomment-2394342451) from another issue, as it seems to be a similar issue to my description of the postStart event failing. My description: > Using another UBI9 based image...

@azatsarynnyy @vitaliy-guliy @RomanNikitenko It's possible that the che code entrypoint postStart event might be failing for UBI9 images (see above [comment](https://github.com/eclipse-che/che/issues/23179#issuecomment-2394431759)). Please let me know if you have any thoughts...

I tested installing Che on minikube using chectl `chectl server:deploy --platform minikube` and then tried creating a workspace with the reproducer devfile. The dashboard goes into a loop of alternating...

@RomanNikitenko Thank you for the follow-up. I checked the `/che/entrypoint-logs.txt` when creating a workspace with my reproducer [devfile](https://github.com/AObuchow/python-endpoint-devfile-test/tree/main) on Minikube and found something: `A system error occurred: uv_os_get_passwd returned ENOENT...