Helm-Chart-Boilerplates
ngs
Helm-Chart-Boilerplates | ngs | |
---|---|---|
12 | 94 | |
8 | 1,367 | |
- | 2.3% | |
0.0 | 3.0 | |
over 1 year ago | 11 days ago | |
Makefile | C | |
- | GNU General Public License v3.0 only |
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.
ngs
- Next Generation Shell – a modern programming language for DevOps
-
Ask HN: Show me your half baked project
Next Generation Shell. As a shell, it's a programming language and a UI. Half baked: programming language - pretty much done, we use it at work; UI - just starting to work on.
Ananlysis of what's wrong with current shells' UIs and how to fix it - https://blog.ngs-lang.org/2023/09/30/ui-in-ngs/
Project - https://github.com/ngs-lang/ngs
Any help would be appreciated of course :)
-
AWS while being great at the underlying services, had by far the worst user experience ever existed on a platform at that scale
The plan for UI is at https://github.com/ngs-lang/ngs/wiki/UI-Design
- NGS v0.2.16 is out
-
How NGS started? – Next Generation Shell
The site is at https://ngs-lang.org/
-
Next Generation Shell
Project: https://github.com/ngs-lang/ngs
-
I'm trying to switch from Python to Lua so I can get into game development... where do I start?
There are number of new ones coming out ...and I'm curious of https://github.com/ngs-lang/ngs. As a language nerd, have you seen that?
- Monthly 'Shameless Self Promotion' thread - 2023/01
-
Telegraph and the Unix Shell
Thanks, took a note - https://github.com/ngs-lang/ngs/issues/621
- Building a simple shell in C – Part 3
What are some alternatives?
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
nushell - A new type of shell
argocd-autopilot - Argo-CD Autopilot
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
helm-charts - A collection of Helm charts
fx - Terminal JSON viewer & processor
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
Kubernetes-Volume-Autoscaler - Autoscaling volumes for Kubernetes (with the help of Prometheus)
ShellCheck - ShellCheck, a static analysis tool for shell scripts
eksctl - The official CLI for Amazon EKS
bashly - Bash command line framework and CLI generator