Actually that wasn't the best response. I was thinking of a different set of creds in a different git. I do see that the .kube subdirectory was included in the git, which should have been in the .gitignore file. I can remove that. Ildikó, can you forward the email with the details of that info email. Perhaps there is more I haven't spotted yet. Scott On 2025-04-17 12:43, Scott Little wrote:
My thinking in the early days was that the StarlingX build was a build for developers. In order to facilitate contributions to StarlingX, we needed allow folks to build and install packages signed with the same common set of developer credentials.
Anyone looking to do a real world deployment was expected to rebuild the full load, substituting their own credentials, or employing a signing server.
At the next community meeting, we should switching to a secure set of credentials for our release branches. Or perhaps having two builds, one with secure creds and one with the current developer creds.
Scott