Feature Request - External Helm Deployments

[cberg-aot]

See separating templating and deployment libraries.

Want: Ability to deploy external (artifacthub or private helm registry) charts as part of deploy backend.

How:

• Refactor action-deployer-openshift to accept helm generated templates?
• Refactor repo to expect helm templates and not OC.yaml? (changes how templating is done, logic remains same)
• Other ideas?

Route verification and other sanity tests are desired, but current logic is integrated with templating & OC expectations (ImageStreams & DeploymentConfigs not used in 3rd party charts, etc).

[DerekRoberts]

Helm support is on the roadmap! I'm not familiar with Artifacthub. Is it worthless, self-hosted garbage, like Artifactory?

[cberg-aot]

LOL 😂 It's essentially dockerhub for Helm charts. Most Official Vendor charts are located there. This is all stemming from the Q&A question I outlined. Contemplating coupling the service deploy to the application pipeline since its a dependant service..... But this just SCREAMS separate project/deploy entirely to me as well

…

On Thu, Feb 23, 2023 at 9:00 AM Derek Roberts ***@***.***> wrote: Helm support is on the roadmap! I'm not familiar with Artifacthub. Is it worthless garbage, like Artifactory? — Reply to this email directly, view it on GitHub <#990 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWHIKRJR2ROHPK3A4GTUWJDWY6JUHANCNFSM6AAAAAAVEUCIIE> . You are receiving this because you authored the thread.Message ID: <bcgov/nr-quickstart-typescript/repo-discussions/990/comments/5090914@ github.com>

[DerekRoberts]

Okay, now I'm getting kinda psyched for the idea! Helm is just sooooo much easier than K8s/oc templating. Issue created.

#993