dhall-kubernetes
ytt
dhall-kubernetes | ytt | |
---|---|---|
9 | 14 | |
609 | 1,589 | |
0.3% | 1.2% | |
4.2 | 7.0 | |
4 months ago | 12 days ago | |
Dhall | 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.
dhall-kubernetes
-
DSLs Are a Waste of Time
I hate yaml with a passion. It marginally better than xml for reading (wins huge on comment syntax) and worse for everything else. It makes zero sense we somehow ended up with it as standard configuration serialization format.
Note yaml is not a DSL. It's a tree serialization format! Everything interesting is happening after it is parsed. Extreme examples point to e.g. github actions conditions.
Anyway, back on topic - maybe not prolog for CDK, but still quite interesting: Dhall-kubernetes - https://github.com/dhall-lang/dhall-kubernetes
-
Why is Kubernetes adoption so hard?
At this point, if it’s painful enough, why isn’t compiling-to-yml tools more popular?
Example: https://github.com/dhall-lang/dhall-kubernetes
Haven’t used dhall myself but I’d definitely prefer a DSL on top of yaml.
-
Nyarna: A structured data authoring language in the spirit of LaTeX, implemented in Zig
Dhall provides https://github.com/dhall-lang/dhall-kubernetes which is exactly this: statically type-checked kubernetes config generation.
-
The Dhall Configuration Language
Dhall is my favorite configuration language that I never get around to using.
I manage DNS in Terraform, and since every Terraform provider uses different objects definitions, and every object definition is rather verbose, Dhall would be a way to specify my own DRY types and leave the provider-specific details in one place. Adding new DNS entries and moving several domains between providers would be a matter of changing fewer lines.
Dhall also has Kubernetes bindings:
https://github.com/dhall-lang/dhall-kubernetes
Although I'm tempted to just stick to Helm here, even though it's less type-safe.
-
Why helm doesn't use a general purpose programming language for defining resources?
Not Helm directly, but does something like Dhall fit your question? https://github.com/dhall-lang/dhall-kubernetes
-
Dhall configuration language as another way to write manifests for Kubernetes
Have you heard about Dhall? It’s a programming language used for generating configuration files for a variety of purposes. One of them is to replace old and limited formats such as JSON and YAML. It is DRYable, secure, and even suitable for creating K8s manifests. The latter option isn’t something for anyone: you have to learn a new language and deal with its peculiarities, but it might be really helpful when you have tons of YAML configs. I’ve recently made a short intro to Dhall for K8s in this review.
-
Terraform 1.0 Release
Best thing is Dhall that I am aware of. Same situation, working as a consultant, forced to use broken things.
https://github.com/dhall-lang/dhall-kubernetes
-
Write Gitlab CI Pipelines in Python Code
Lets look at a specific example. Take Kubernetes: everything is yaml, with complete schemas, all the way down. From your perspective this is configuration utopia, right? Meanwhile back in reality k8s is the poster child of "yaml hell". From the day it was released, people took one look at it, gave it a giant NOPE and instantly spawned half a dozen templating languages. The most popular of these is helm, which has a terrible, no good, very bad design: full of potential injection attacks from purely textual string substitution, manually specified indentation to embed parameterized blocks, virtually no intermediate validation, no way to validate unused features, etc etc
Compare to dhall which publishes a complete set of dhall-k8s schema mappings which enables you to factor out any design you want down to as few configuration variables as you like, while validating the configuration generators themselves at design time. https://github.com/dhall-lang/dhall-kubernetes#more-modular-...
-
INTERCAL, YAML, And Other Horrible Programming Languages
The solution I like is Dhall. They even have a Kubernetes solution that will catch a lot of issues at compile-time, before you try to apply it to Kubernetes. At earthly we aren't actually using it though. Our Kubernetes guru found it to be a bit slow but I am hopeful it or something like it will be the future.
ytt
-
10 Ways for Kubernetes Declarative Configuration Management
YTT - YTT is a templating tool that understands YAML structure. It helps you easily configure complex software via reusable templates and user provided values using the Starlark language.
-
Alternatives to Helm/Kustomize for complex Kubernetes Deployments
Adding https://carvel.dev/ytt/ to the list. I was happy using this tool as IMO it mixes good things from Helm and Kustomize, however the syntax is ugly and repelling my colleagues to have a closer look.
-
The YAML Document from Hell
> Templating yaml is a terrible, terrible idea
I've had a good time using ytt: https://carvel.dev/ytt/. It implements language-aware templating, which is IMO the only reasonable way to do it.
-
Creating Kubernetes Templates
`ytt` is part of the Carvel toolchain. https://carvel.dev/ytt/
-
Dealing with YAML overload
I agree with you on `you will want to see just plain texts instead of a bunch of templating token with hidden logic.` Which is why I think https://carvel.dev/ytt/ would be great. We could generate these templates in pipelines, or we could just make it easier to maintain what we have.
-
How to handle the lifecycle of multiple COTS
For more advanced configuration management you might be interested in ytt ( https://carvel.dev/ytt/ ) which is a "yaml-aware" templating tool. it lets you do "patches" via an overlay mechanism to add or remove specific yaml blocks, and it also lets you use a simplified python dialect for more complicated logic. With ytt you would put your DNS IP into a "data values" file and then run ytt to render it into the configs before handing them off to the deployment tool. e.g. `ytt -f | kubectl apply`
-
The Dhall Configuration Language
I said this above as well: ytt (https://carvel.dev/ytt/) lets you embed starlark into valid yaml, among other cute tricks for managing biz-logic in configs.
-
ArgoCD Instance per kubernetes cluster? (staging and prod)
Manifests are generated with ytt (https://carvel.dev/ytt/).
- Dynamically creating yaml manifests?
-
YAML and Configuration Files
This is why you should consider https://carvel.dev/ytt/
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
kustomize - Customization of kubernetes YAML configurations
nvim-lspconfig - Quickstart configs for Nvim LSP
cue - CUE has moved to https://github.com/cue-lang/cue
starlark - Starlark Language
tanka - Flexible, reusable and concise configuration for Kubernetes
NUKE - 🏗 The AKEless Build System for C#/.NET
strictyaml - Type-safe YAML parser and validator.
vim-lsp - async language server protocol plugin for vim and neovim
hull - The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows
yaml-rust - A pure rust YAML implementation.