How do you version public and private Helm Charts for the same application?

Question

Continuous Integration

Gentlemen, share your secrets. I'm trying to work out a working strategy for myself. Based on Best Practices.
I want to be able to quickly change and make changes to versioned Helm Charts in the future without too much headache.
Googled a bit, found a few articles, here for example. But how to stack and version charts is individual for each company.
https://docs.eupraxia.io/docs/new-helm/helm-best-p...

My question is a bit different.
How good is it to keep your charts and public ones together?
For example, there is an application in which there are 5 microservices and Mysql. So, installing Mysql from a public repository is easy, but how do you keep all versions together?
How to locate Values.yaml (each service has its own settings and mysql too)?
Chars and subcharts? - But I want to use public charts from MySQL.

A little chaotic, but I hope someone will understand me and either share secrets or, for example, a link where you can read something like that.

Thanks a lot.!

Answer 1

I usually mirror a public chart repository or pull/cache chart into my Nexus.
In case the original chart disappears, moves or ceases to be compatible, or maybe the Internet is banned in the country. Or I want to make my own changes to it.

Chars and subcharts? - But I want to use public charts from MySQL.

Subchart can be specified as a Dependency (or connected as a git submodule if it's a turnip.).
Configure values.yaml in the same way as for subcharts.

Is there a separate repository for each chart?

Charts are not always in the helm repository.