[JIRA] (JENKINS-57328) Should not use secret name as credential ID
Title: Message Title
Ankur Patel commented on JENKINS-57328
Re: Should not use secret name as credential ID
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.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199101.1557040941000.1213.1568904180926%40Atlassian.JIRA.
[JIRA] (JENKINS-57328) Should not use secret name as credential ID
Title: Message Title James Nord commented on JENKINS-57328 Re: Should not use secret name as credential ID we only support a single namespace so this should not be an issue unless JENKINS-57329 is implemented Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199101.1557040941000.11985.1561747320362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57328) Should not use secret name as credential ID
Title: Message Title
Share Cheng created an issue
Jenkins / JENKINS-57328
Should not use secret name as credential ID
Issue Type:
Bug
Assignee:
James Nord
Components:
kubernetes-credentials-provider-plugin
Created:
2019-05-05 07:22
Priority:
Major
Reporter:
Share Cheng
Currently, this plugin will use secret's name as the credential ID to create a credential. It may cause problems when there are secrets have the same name but in different namespaces. It is better to use namespace and name to generate the credential ID - like '{namespace}-{name}'.
Add Comment
