Namespaces in ChartCenter are currently reserved on a first-come, first-serve basis. We are also considering enhanced options for chart inclusion, but the goal of this outline is to discuss namespacing issues.
Proposal Details:
Naming conventions
Guidelines for prohibited namespaces
How to check ownership of the Helm repo to reserve the namespace?
Will it be a manual process?
Discussion of Repos:
We need to support adding charts from git repos from source
User should be able to choose the name (which becomes the namespace) of the Helm repo name in ChartCenter
That repo can include many git repositories that the user owns, so this becomes validation of the ownership
Some users may not want to have their own repo, should we provide e.g. stable repo where they can put their charts?
Charts must be versioned: e.g. github/bitbucket/gitlab release, we should not use the code from the master
Questions / Considerations:
Do we allow maintainers to change a namespace?
Issues with immutability
Issues with ownership verification
Issues with reserved namespaces
Should we support/endorse official namespaces?:
Create a 2nd Tier Verification Process to verify organizational ownership
Create criteria to make stability, security, and maintenance of official namespaces a focus
Provide a badge on the ChartCenter UI to signify official namespaces from organizations
Namespaces in ChartCenter are currently reserved on a first-come, first-serve basis. We are also considering enhanced options for chart inclusion, but the goal of this outline is to discuss namespacing issues.
Proposal Details:
Discussion of Repos:
Questions / Considerations:
Should we support/endorse official namespaces?: