Currently, when a user runs up enterprise install they are prompted for a License ID and Token. These are then used to fetch an access key from DMV and download the appropriate Helm chart from Upbound Registry. However, the images referenced in the Helm chart will also need to be able to be pulled after chart install. The same License ID and Token can be used as an imagePullSecret to pull the images.
How could Upbound help solve your problem?
up enterprise install should create the necessary Secret used to pull images referenced in the Helm chart. We should also provide a flag for users to skip creating this Secret as there is a good chance many enterprise customers will be copying the images to their own internal registries, in which case they will need to supply their own image pull Secret manually. We may support prompting for these credentials at install in the future via some of the ideas expressed in #113.
hasheddan
commented
2 years ago
What problem are you facing?
Currently, when a user runs
up enterprise installthey are prompted for aLicense IDandToken. These are then used to fetch an access key from DMV and download the appropriate Helm chart from Upbound Registry. However, the images referenced in the Helm chart will also need to be able to be pulled after chart install. The same License ID and Token can be used as animagePullSecretto pull the images.How could Upbound help solve your problem?
up enterprise installshould create the necessarySecretused to pull images referenced in the Helm chart. We should also provide a flag for users to skip creating thisSecretas there is a good chance many enterprise customers will be copying the images to their own internal registries, in which case they will need to supply their own image pullSecretmanually. We may support prompting for these credentials at install in the future via some of the ideas expressed in #113.Epic #