Group Kubernetes Integration Doesn't Accept Valid Certificate from API
Summary
Using the API to add an existing GKE cluster to a private group at the free tier on gitlab.com fails with
{
"message": {
"platform_kubernetes.ca_cert": [
"must be a valid PEM certificate"
]
}
}
Steps to reproduce
Use API to add an existing cluster with command similar to
https://gitlab.com/api/v4/groups/6356238/clusters/user?name=steevo-dod-kc-wkshp&platform_kubernetes_attributes[api_url]=https://34.68.134.20&platform_kubernetes_attributes[token]=eyXXXXXXXXXXzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6ImRlZmF1bHQtdG9rZW4teGpqbWYiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGVmYXVsdCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6Ijk1ODY0ZjIxLWY0ZGMtMTFlOS1hMmRhLTQyMDEwYTgwMDIwMiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpkZWZhdWx0OmRlZmF1bHQifQ.GLbQGsYuBfNrzNr6nbg8O2EjccDJqbIf3y0oqtmbULFtjIevDQik1l-iBpl3m2EAenME4j3XwyCuhODl4Y1DRT_AJljq3omvoWuyI-VyjRBt7dCGSY2IRvh8ZpvYSq7Mx7-BgU06OXMJVXBRXb0nTEw0RxIRHu0BrcSbrLvmzghhf-qAiwKj4gO7hswYyYafsaSkQ980qGWr8R2fZe10ikhwHaho7ilZg74IhgT0Sn6siI5JYDEYtC5fME8283-9ZUXyLOALJpioZShQNJLmrfsc1kuWhagLWFP4Y1XPTt8JaUSbeblawUUvbGAv8-BsqerbmRaYDFZRVtwIZl-GXw&platform_kubernetes_attributes[ca_cert]=-----BEGIN CERTIFICATE-----
XXXXXXXXXXOgAwIBAgIQCHRGN0XoKNY/ZEQqWWaW6TANBgkqhkiG9w0BAQsFADAv
MS0wKwYDVQQDEyQ2OTgzY2Y3Yi00YmJkLTQ0YTgtYmY3MC02YWVkZmYwZTVmYTgw
HhcNMTkxMDIyMTM1MzUzWhcNMjQxMDIwMTQ1MzUzWjAvMS0wKwYDVQQDEyQ2OTgz
Y2Y3Yi00YmJkLTQ0YTgtYmY3MC02YWVkZmYwZTVmYTgwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQCuEgGSSkqYS8OKRZfluvrDkWfFLWMpA2p3YRSXvAoK
g5O8wRG52Pw5tyg6NewCN4B826ifTBhihicOSXBjx+Y6dn+U9kzRnF7+jYWAh0df
TW5+luS0RahwKknxhDIez7RPnq+uNxWiQEVT3wkDEaf2Mc96SS6PqJX6i80B3Wo8
PPxWyyFL/eS11+zrCm/0Prn4DBiDbiuOjLU7mFp7a+iHAXOY7xtmwmKI8oQdniFs
KCYmdmORf/4QoII1t4ncBZjEFPnYYgd6M1PvOux/z5IyMgC6uV2fI9S2ZSJqmVvK
0qr9FBgx2XECVUoGA82O3179vubR7LVuJCz0o8WEt/mjAgMBAAGjIzAhMA4GA1Ud
DwEB/wQEAwICBDAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBU
sfR+rIwqZOg54wpKTtRdOp8Jc1H1D43kv4t50WnlZ1qJSvpoCq3TA92IMLpHXyI3
MKkLfC7OnCBXZMhOablOSKXj9fPcZYzZOTAXw+kbtq1UxpCHlo7q3I0z9Ip7Y17v
LhMtld2Iju3xlU4RThj1G0oZVrjfumK3bRmnYob6ylAFpA4QTUc4zOpEyRM5YKsd
RzdXBOwo7BG1leba3g38Nrn+JbNQR4xySsi5eAxRTNyT4A4MkQq4aVHcddaaUO8M
TsI0OR6FaxayqLgyLX75v1FrOt6ZovaX6FuvTwSm75DfhL3dcVB52MQ/yahqrwmN
Vht3Ntw7b2Mmyk9SfLaf
-----END CERTIFICATE-----
Or a similar API call to edit and the output returned is that the certificate is not a valid PEM certificate. Pasting the same certificate into the Web UI works, the certificate is accepted as valid and works to connect to the cluster.
Alternatively, using the same command as above except without
platform_kubernetes_attributes[ca_cert]
and the cert adds the cluster to the group without the certificate, but the command succeeds.
Example Project
https://gitlab.com/devopsdayskc
What is the current bug behavior?
{
"message": {
"platform_kubernetes.ca_cert": [
"must be a valid PEM certificate"
]
}
}
What is the expected correct behavior?
The cluster added to the GitLab group without errors
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Results of GitLab application Check
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)