Using Nickel for declarative Kubernetes in production #1498
Replies: 2 comments
-
Hi @gkleen, that sounds both like an exciting and ambitious pipeline! Feel free to ask any question, or report any issue you have during your experimentation. In particular, I hope the Nickel LSP provides you with some value - if not (completion doesn't work, etc.), reports would greatly help us improve Nickel 🙂 |
Beta Was this translation helpful? Give feedback.
-
There has been some movement on this and not everything worked out as planned. Experience with nickel was quite good and it's staged to go into production soon. I'm explaining how it's integrated below. We're following the advice of nickel-lang.org and providing
|
Beta Was this translation helpful? Give feedback.
-
I'm currently doing contract work with @savau (uniworx.de).
We're standing up lots of infrastructure quite rapidly and would like to use the large amount of leverage fully declarative configuration of… everything gives us wrt. to sysadmin/developer time.
In particular I've done some work on truly declaratively defining the desired state of our (currently one node, but growing) kubernetes cluster here fully integrated into our NixOS machine config flake (so no traditional GitOps).
Highlights wrt. to the pain we're having with that include stuff like line 81 and the manually generated
.patch
files we're applying to the helm charts upstream (e.g. gitlab) provides (large.tar.gz
encoded as base64 in a yaml string, anyone?).After some private communication with @vkleen I'm now intending to:
nickel doc
, currently)PostStart
ofkubelet.service
) run the python script to generate an ephemeral json fileKUBECTL_APPLYSET=true kubectl apply --prune --applyset=nixos
Beta Was this translation helpful? Give feedback.
All reactions