hull
tanka
hull | tanka | |
---|---|---|
13 | 25 | |
151 | 2,236 | |
0.0% | 2.1% | |
7.8 | 8.3 | |
13 days ago | 10 days ago | |
Python | Go | |
Apache License 2.0 | 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.
hull
-
When to start adopting helm?
If you are just starting out and decide to go with writing your own Helm Charts I'd like to suggest our HULL Helm Library Chart for that purpose.
-
Getting Started with Helm
With HULL we have proposed an alternative yet Helm based solution a year ago which that tries to do it upside down by first giving you a documented Kubernetes API style full access to each objects configuration. Only on top of that it provides you further advanced options to (re)introduce abstraction into the mix - only if you need them and they actually improve your configuration. Everything takes place in the values.yaml so there is no digging around in the templates folder and everything is in view.
-
HULL Tutorial 01: Introducing HULL, the Helm Universal Layer Library
The HULL library Helm chart provides a single common interface to specifying Kubernetes objects within Helm Charts. The interface itself is based on the Kubernetes API schema itself which is integrated as a JSON schema in the HULL chart. Since all objects are defined directly in the values.yaml under the hull key there is no need to create and maintain custom template files when creating objects with HULL, everything happens in the values.yaml.
-
HULL Tutorial 02: Setting up a Helm Chart based on HULL
Good, now proceed by creating a new empty HULL based Helm chart. The steps are documented here but you will create it from scratch here to understand what is needed.
-
HULL Tutorial 03: Integrating ConfigMaps and Secrets
As a reminder, the goal of this tutorial series is to demonstrate how to build Helm charts based on the HULL library chart by recreating the functionality of the original kubernetes-dashboard Helm chart with a HULL based chart from scratch. When you have followed the previous part of this tutorial on setting up a HULL base chart you have created a for now unconfigured Helm chart named kubernetes-dashboard-hull in the 02_setup subfolder of your working directory (we assume that's ~/kubernetes-dashboard-hull here). You can alternatively download the current chart state here and continue from there. Also you should have checked out and extracted the kubernetes-dashboard Helm chart to kubernetes-dashboard in your working directory because examining it will be frequently required.
-
HULL Tutorial 07: Configuring Advanced Objects
the ability to specify any CustomResource as a customresource object instance. For CustomResources you additionally need to specify the kind and apiVersion besides the free form spec of your object.
-
Why is Helm considered best practice?
We have built a Helm Library chart named HULL, it provides amongst other features full access to all defined objects and their properties at creation and deployment time. Think of it as an API to specify Kubernetes objects directly in a Helm charts values.yaml. If there is some functionality you want to add or use in a particular scenario you can just configure it and the Kubernetes objects are as you actually want them to be - every aspect can always be tuned at deploy time if needed without you having to get back to the chart creator via PRs, hack the chart or similar methods. All doable with Helm and the HULL library chart, no other tooling required!
-
Grafana Labs' Tanka is Awesome.
We actually proposed an alternative way to solve the problem if you are Helm with our Helm library chart HULL.
-
Does anybody else find Helm charts pretty useless?
It may be worthwhile to look at the recently added examles, these are more advanced chart values.yamls from products we are deploying this way. You can see it can be pretty concise to define your applications structure with HULL in comparison.
-
values.schema.json ignored for values referenced in configmaps? (Helm 3)
Downsides to this is that you would have to write out the full content of your config in the values.yaml and cannot use the templating capabilities any further. Within the values.yaml no templating is allowed (unless you base your chart on this library chart we have created ;) which may be a more advanced topic if you just got started)
tanka
-
Why the fuck are we templating YAML? (2019)
I would recommend implementing a similar API to Grafana Tanka: https://tanka.dev
When you "synthesise", the returned value should be an array or an object.
1. If it's an object, check if it has an `apiVersion` and `kind` key. If it does, yield that as a kubernetes object and do not recurse.
-
What Is Wrong with TOML?
Maybe you'd like jsonnet: https://jsonnet.org/
I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).
Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/
A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet
-
Show HN: Keep – GitHub Actions for your monitoring tools
- validation is often impractical (at least identifying exactly where the error is… I’m looking at you Helm!)
Unrelated to OP, but you can leverage Tanka to extend helm charts with functionality not provided by upstream.
https://tanka.dev/
-
Alternatives to Helm?
Although jsonette might be considered more complex Tanka is a great alternative for k8s config management.
- Helm makes it overly complex, or is it just me?
-
The YAML Document from Hell
At Grafana Labs we're using jsonnet at scale, while being a powerful functional language it is also excellent for rendering JSON/YAML config. We have developed Tanka[0] to work with Kubernetes, for other purposes I can recommend this course[1] (authored by me).
[0] https://tanka.dev/
[1] https://jsonnet-libs.github.io/jsonnet-training-course/
-
Should i migrate from Kustomize to Helm?
If you're hitting the limits of Kustomize, maybe look at Tanka as well.
-
Is it possible to wrap Kustomize yaml with jinja2?
Yes, try Tanka.
-
Using Docker – Compose in Development and Production
yes. basically. and this is a path that multiple people are trying to solve. e.g. AWS CDK8s, https://tanka.dev/, etc
Compose would be awesome.
-
Google Kubernetes clusters config checker tool
http://tanka.dev
(Note I work for Grafana Labs who fund Tanka and use it for all production config)
What are some alternatives?
ytt - YAML templating tool that works on YAML structure instead of text
helm-charts - Prometheus community Helm charts
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
kustomize - Customization of kubernetes YAML configurations
kapitan - Generic templated configuration management for Kubernetes, Terraform and other things
charts - HAProxy Ingress helm charts
charts - Helm Charts for Chatwoot
kpt - Automate Kubernetes Configuration Editing
agent - This is the entrypoint repository for the Superblocks Agent Platform
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀