| For my case, I am using a Helm Chart to deploy Jenkins and its naming standard prefixes the secret names with the chart name. (ex: '{chartName}-{credname}'.) I've resolved to modify the secret template and use the name as written to get around this, so breaking convention to workaround it. Another issue is that, Kubernetes naming convention doesn't allow mixed-case names. So credential names are forced to follow the same convention. ("lower case alphanumeric characters, -, and .") Not a terrible issue, just forced to update all the pipelines. So this change would afford a good deal of flexibility. |
