Typical project structure

• helm-service-chart

  1 - -

When they git commit+push to main until now, Github Actions pick this up, build a new image and then do during the last step more or less helm upgrade my-service https://github.com/orgname/helm-service-chart -f chart/values.yaml.

• shortlink

  4 672 10.0 Go

  Shortlink service (Microservice example) ⭐️ Star the repo if you like it! (by shortlink-org)

  

I think that for real projects it is better to separate argocd and our applications. For my pet project I use one mono repository: - `ops/Helm` - description of all helm-charts - `ops/argocd` - description of argocd applications that refer to helm charts So when you update a helm chart it is immediately applied to the k8s cluster. You can see my example - https://github.com/shortlink-org/shortlink

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project