Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Universal-Kubernetes-Helm-Charts
Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
-
aws-helm-multi-deploy-prebuilt
Deploys all helm chart folders inside the 'deployment' folder in the root of a repository.
-
aws-helm-multi-deploy-nodocker
Deploys all helm chart folders inside the 'deployment' folder in the root of a repository.
-
helmfile
Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD. (by helmfile)
-
InfluxDB
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.
Use multi-values files with helm ALWAYS. Allowing an env-specific overlay to tweak your default values files. See: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver/deployment/boilerplate-echoserver
Rendering out the manifests is something I have been pushing for. Not having to understand how every templating tool works and what actually is being changed is key. Though, it gets complicated when you use helm (or any templating/patching tool) that produces many variants. You also lose any release/deployment time hooks that are provided (helm hooks or recently "patched" kustomize env variables).
See: Open-Source Universal Helm Charts See: Boilerplates of using Open-Source Helm Charts (as a sub-chart)
Deploy with Github Actions with - https://github.com/DevOps-Nirvana/aws-helm-multi-deploy-prebuilt or https://github.com/DevOps-Nirvana/aws-helm-multi-deploy-nodocker . Both of these support built-in my recommended path of env-specific values overlays
Deploy with Github Actions with - https://github.com/DevOps-Nirvana/aws-helm-multi-deploy-prebuilt or https://github.com/DevOps-Nirvana/aws-helm-multi-deploy-nodocker . Both of these support built-in my recommended path of env-specific values overlays
I've used helmfile before to declaratively manage multiple helm charts. It's a higher-level tool, and still uses helm under the hood.
I'm interested cdk8s but haven't tried it yet: https://github.com/cdk8s-team/cdk8s
Related posts
- Project recommendations - Go, Kubernetes & Docker
- Launch HN: Nullstone (YC W22) – An easier way to deploy and manage cloud apps
- What k8s related tool you wish you knew earlier?
- Kubernetes cluster on-premises. Best practice?
- In a gitops world, what does your team do to reduce cycle time for devs?