SSH-private key is incorrectly base64 encoded through OpenShift dashboard

4.13.1

Always

1. In the OpenShift pipeline to clone github private repo please provide ssh-private key in SSH private key space.
2. When pipeline is triggered it failed to clone with permission issue.The ssh private key is stored in git-credentials secret.
3. Using oc cli if i try to check secret git-credentials manually i could see base64 encoded value of ssh private key is incorrect.If i correct the base64 encoded value using oc edit and retrigger pipeline then git clone works well.

Git clone is failing due to incorrect base64 encoded value generated for ssh private key through OpenShift console.

Base64 encoded value should be correct for git clone from private git repository to work well.

Not sure but it seems to be some bug in console since edit secret git-credentials manually using oc edit  with base64 encoded value it works well and git clone is successfull from private git repo.
I will attach screenshot of issue.

One more issue i could see is ssh-private key is not accepted in dashboard with tickmark and it gives error Error "Required value" for field "data[ssh-privatekey]".
So if i edit ssh private key one alpabhet and revert back changes then tickmark works well and base64 encoded is generated but with incorrect value.