Cannot start any workspaces after creating an ssh key pair with a colon in the name

[ChristianSchenk711]

I accidentally provided "hostname:v3" as a name to a keypair created via "SSH: create key pair for particular host".
Afterwards I was not able to start any workspaces: Workspace start failed with a message about an invalid character (:), see below.
I had to manually delete the keypair from the sshkeypair table to fix that.

We currently use Che 7.4.0 on a kubernetes infrastructure.

Error message when starting workspaces is:

Error: Failed to run the workspace: "Failure executing: POST at: https://10.2.0.1/api/v1/namespaces/che7-che-workspace/secrets. Message: Secret "workspaceubl83l6plbjhrjl9-sshprivatekeys" is invalid: data[ab:c]: Invalid value: "ab:c": a valid config key must consist of alphanumeric characters, '-', '_' or '.' (e.g. 'key.name',  or 'KEY_NAME',  or 'key-name', regex used for validation is '[-._a-zA-Z0-9]+'). Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=data[ab:c], message=Invalid value: "ab:c": a valid config key must consist of alphanumeric characters, '-', '_' or '.' (e.g. 'key.name',  or 'KEY_NAME',  or 'key-name', regex used for validation is '[-._a-zA-Z0-9]+'), reason=FieldValueInvalid, additionalProperties={})], group=null, kind=Secret, name=workspaceubl83l6plbjhrjl9-sshprivatekeys, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Secret "workspaceubl83l6plbjhrjl9-sshprivatekeys" is invalid: data[ab:c]: Invalid value: "ab:c": a valid config key must consist of alphanumeric characters, '-', '_' or '.' (e.g. 'key.name',  or 'KEY_NAME',  or 'key-name', regex used for validation is '[-._a-zA-Z0-9]+'), metadata=ListMeta(_continue=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Invalid, status=Failure, additionalProperties={})."

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[skabashnyuk]

Fixed in #19031