Helm-Chart-Boilerplates
sparrowci_web
Helm-Chart-Boilerplates | sparrowci_web | |
---|---|---|
12 | 11 | |
8 | 1 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
Makefile | Raku | |
- | - |
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.
Helm-Chart-Boilerplates
-
Dedpulication standards of Helm Charts values file for a global chart with subcharts for our app. What's the right way to only need to specify a value once?
I would point you to what I call the "Universal Helm Charts" and some examples of how to use them.
-
Monitoring many cluster k8s
Shameless Plug: Here's one of my dashboards I made for Ingress-Nginx, which is my recommended border router/gateway into all the services. It adds deep robust metrics and configurability, and if you've got years of experience with Nginx also, it allows you rich complex customization via nginx's configuration structure via kubernetes annotations. Besides that I have open-source helm charts which are easy to use, boilerplates showing how to use them, a volume autoscaler to automatically resize your disks as they get full, and a blog where I share various of my experience which is a companion blog to my upcoming book of the same name. Hope this helps! Feel free to ask if you have any further questions.
-
Best way of managing Helm?
Here is an example of a repo that uses an sub-chart: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-apache-with-configmap-template/deployment
-
Helm makes it overly complex, or is it just me?
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
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
Helm charts - https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts Example using helm charts as sub charts - https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver
- How do you guys manage your deployment pipelines?
-
Monthly 'Shameless Self Promotion' thread - 2023/01
Helm Chart Boilerplates are examples of usage of the above Universal Helm Charts to help people understand how to use them more, a stop-gap until I add more documentation
- Deploying with Helm - extra manifests?
-
Creating Kubernetes Templates
Helm Chart Usage Boilerplates (Examples of using these helm chart)
-
Use Kubernetes to load test my product.
To help you on deploying your service, I've created open source generic/universal Helm Charts to make it easy to do the above. Here are the Universal Helm Charts and here's some boilerplate examples of using them. These built-in have support for HPAs, services, ingresses, etc, making it as easy as autoscaling.enable: true I haven't gotten around to documenting the helm charts yet, but there's lots of comments in the values.yaml file explaining everything.
sparrowci_web
-
Monthly 'Shameless Self Promotion' thread - 2023/02
I continue to build community around SparrowCI - https://ci.sparrowhub.io - flexible CI system with many languages support. Welcome in! We already have active uses , but we welcome 🤗 more.
-
But really, why is all CI/CD pipelines?
With SparrowCI you have a compromise of having yaml based structure and flexibility to use many programming languages for tasks, and tasks act as functions accepting and returning parameters accessible within other tasks. You can check more out at https://ci.sparrowhub.io/
-
Monthly 'Shameless Self Promotion' thread - 2023/01
Continue to build super flexible CICD framework - https://ci.sparrowhub.io , recently I’ve added self hosted deployment support that allows people to install the system on their infrastructure. Another interesting feature is gitea integration
-
Monthly 'Shameless Self Promotion' thread - 2022/12
Checkout more on https://ci.sparrowhub.io
-
Sunday Daily Thread: What's everyone working on this week?
Keep building my own free CI service extendable by many languages including Python, please check out Python examples here - https://github.com/melezhik/SparrowCI/tree/main/examples/python
-
Monthly 'Shameless Self Promotion' thread - 2022/11
Now officially support builds for Alpine Linux, Debian and Arch Linux containers - see examples at https://ci.sparrowhub.io
-
Streamline your GitHub Actions dependencies using Nix
For example, in SparrowCI pipeline this could be achieved by a simple Bash task:
- Building raku alpine package on vanilla Alpine Linux
-
SparkyCI update
For more sophisticated scenarios try out .sparkyci.yaml DSL
-
SparkyCI Update
For more sophisticated scenarios there is .sparkyci.yaml DSL that allows to install none Raku packages, external services and so on, an example is my fork of DBIish::Pool repo - https://github.com/melezhik/DBIish-Pool/blob/main/.sparkyci.yaml
What are some alternatives?
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
py-template - One-click GitHub Actions pipelines for Python!
argocd-autopilot - Argo-CD Autopilot
DBIish-Pool - DBIish Connection Pool
helm-charts - A collection of Helm charts
PoC_CVEs - PoC_CVEs
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
featbit - A feature flags service written in .NET
Kubernetes-Volume-Autoscaler - Autoscaling volumes for Kubernetes (with the help of Prometheus)
DictDataBase - A python NoSQL dictionary database, with concurrent access and ACID compliance
eksctl - The official CLI for Amazon EKS