Allow to Pass CA Certificate for K8s Cluster Config in Base64
Problem to solve
When adding an existing K8s cluster, GitLab asks for the CA Certificate in PEM format. However many providers give the users the CA Certificate in Base64. We should allow the users to pass the CA certificate in Base64
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
Further details
Expanding on this functionality decreases the friction when it comes to creating and configuring resources inside GitLab. This contributes to the vision by enhancing the user experience customers have when interacting with GitLab.
Proposal
- The user decides to add a K8s cluster.
- The user has an existing cluster so they choose that option.
- The user gets to the point where they have to enter the CA certificate.
- The user can enter the CA Certificate in PEM format or Base64.
We could allow them to switch between PEM and Base64 by using a dropdown or radio buttons. Decoding the certificate from Base64 is a super simple operation that can be done client-side.