fix(014-galust-umbrella-chart): Galust Umbrella Chart

[aghamyan44]

No description provided.

[what-the-diff]

🎉 Fabulous news, team! 🎉 We've made significant progress on the Helm chart for our Galust AI layer. Here's a kick-off overview of the improvements:

💾 Package Improvements

• We've now included a .helmignore file, which helps keep our package neat and tidy by excluding non-relevant patterns. 🗑
• Our new Chart.yaml file neatly organizes the Galust AI layer chart and clearly spells out its dependencies. 📜

📚 Documentation and Guides

• Our newly crafted README.md is a comprehensive guide that clearly outlines our chart's purpose, deployment instructions, component details and some checks post-deployment - perfect for new team members! 📖
• We've created a NOTES.txt template, which will offer insightful output information upon chart installation. 📝

🔧 Handy Tools and Templates

• We have helper templates in _helpers.tpl that will assist in chart naming and label generation - a great time-saving feature! ⏳
• We've got a new template for the image pull secret in image-pull-secret.yaml. It's now easier than ever to create dynamic Docker registry secrets. 👏

👀 Configurations

• We've set up default specifications in values.yaml, which details settings for various components- it's a one-stop file for all the configuration needs. 🛠️
• For testing purposes, we've created values.test.yaml to provide minimal configurations. 🧪

🥳 But that's not all! Here's more that we've done:

🚀 New Deployments

• We've added a new Helm chart, charts/galust-ai-layer, to smoothly deploy various Galust AI layer components on Kubernetes! 🌐

📋 Task Outline

• We've neatly jotted down the outline for setting up, implementing and validating the new chart in tasks.md- now, tracking tasks is a breeze! 📌

🔄 Backward Compatibility

• We've preserved backward compatibility by maintaining existing deployment defaults from the ai-layer! No worries about breaking changes! 👍

🛡️ Security and Traffic Management

• We now have ingress configurations for all components to manage incoming traffic with settings for TLS and CORS support. 🚦

Shout out to everyone who was involved! Your efforts are definitely moving us forward. Let's continue this fantastic work! 🚀

[mrdntgrn]

we seems do not need this additional config, we can just mark imagePullSecret and use as anchor in places we need it

[mrdntgrn]

there I remember a known issue that aws ecr secrets getting expired after some time, and the pods fail to pull image until we manually renew the token again.
can we maybe integrate solution to renew thesecret here directly? as I remembre Hovo has this kind of fix/implementation for cloudbrowser.

[mrdntgrn]

lets move example to root examples folder

[mrdntgrn]

the base chart version seems quite old, lets use the latest one

[mrdntgrn]

where do we create cnpg-main-urls and cnpg-main-user secrets, if its being created out of this helm chart then lets have it in readme
will not it be mre convinent to have host and password in same secret?