reliza-cli
flux2-kustomize-helm-example
Our great sponsors
reliza-cli | flux2-kustomize-helm-example | |
---|---|---|
10 | 9 | |
4 | 881 | |
- | 6.0% | |
7.1 | 4.3 | |
6 days ago | 8 days ago | |
Go | Shell | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
reliza-cli
- Track all software deployments across all instances at any point in time with Reliza Hub
- Reliza Hub manages bundles of microservices - especially when you feel you have too many. Know what is and should be deployed on every instance at any time.
- Reliza Hub - Take Control Of All Your Software Changes
- Reliza Hub - Revolutionary Platform to Manage All Your Software Releases
-
How are you measuring DevOps performance?
We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.
-
Best Practices for managing parent docker images used by several services
You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment
- Ask HN: How do you keep track of releases/deployments of dozens micro-services?
-
How do you manage multiple environments with GitOps?
Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.
-
Service Config Management tools
We're building Reliza Hub for this purpose - https://relizahub.com
-
Full CI/CD pipeline delivered via ArgoCD
Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision
flux2-kustomize-helm-example
- Flux: can I add a monitored path after bootstrap?
- Is it possible to deploy to KIND cluster via GitHub actions?
-
How to structure Terraform with multi-env + multi-regions for TBD in monorepo
Any public repo show-casing a nice structure? (I am used to the Gitops world on K8s, and for the case of FluxCD for instance I would recommend this repo as a good practice to start multi-tenancy. https://github.com/fluxcd/flux2-kustomize-helm-example. I am looking for a similar "boilerplate" but for TF 😅)
- Am I wrong for avoiding helm completely?
- fluxcd/flux2-kustomize-helm-example: A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
-
Helm chart release management between environments
My recommendation would be to take a look at their documented example of this exact scenario with various overlays for production and staging, but you could ofc add as many as you wanted. All you would do is for production point flux to the production overlay/ directory, which then calls all your normal files but overrides some values you desire. Further to this you can keep your helm chart focused on lets say the "most-common" use case, then just call it with whatever additional values you would like, E.G here in the same repo as above. Notice the values at the bottom of the yaml file which override the charts default values.
-
Multi clusters deploy/automation
Here's an example using flux v2 to deploy to multiple environments/clusters: https://github.com/fluxcd/flux2-kustomize-helm-example
-
How do you manage multiple environments with GitOps?
We are using flux2, which uses Kustomize under the hood. It takes a little bit of time to learn about the different CRD's which are available but once you do it works excellent. They also have an example project which sounds like it might fit your use case https://github.com/fluxcd/flux2-kustomize-helm-example
-
Version Control / Tracked Changes For K8
As /u/vincentdesmet mentioned Kustomize will most likely to solve your many "apps" with slightly difference issue, this is a good example https://github.com/fluxcd/flux2-kustomize-helm-example (also include helm one)
What are some alternatives?
argocd-image-updater - Automatic container image update for Argo CD
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
DevOpsMetrics - A project to extract and process high performing DevOps metrics (DORA) from GitHub and Azure DevOps
k8s-gitops - GitOps principles to define kubernetes cluster state via code
release-please-action - automated releases based on conventional commits
zim - A caching build system for teams using monorepos
gitops-playground - Creates a complete GitOps-based operational stack on your Kubernetes clusters
crane - ⬆ A GitLab CI ready image to upgrade services in Rancher
k8s-wait-for - A simple script that allows to wait for a k8s service, job or pods to enter a desired state
sauron - Sauron, the all seeing eye! It is a service to generate automated reports and track migrations, changes and dependency versions for backend services also report on known CVE and security issues.
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]