3 ms·
Pkl was one of the best internal tools at Apple, and it’s so good to see it finally getting open sourced. My team migrated several kloc k8s configuration to pk
by jaseemabid 3y ago
Pkl was one of the best internal tools at Apple, and it’s so good to see it finally getting open sourced.
My team migrated several kloc k8s configuration to pkl with great success. Internally we used to write alert definitions in pkl and it would generate configuration for 2 different monitoring tools, a pretty static documentation site and link it all together nicely.
Would gladly recommend this to anyone and I’m excited to be able to use this again.
- filleokus 3y agoWas about to ask if you had k8s api models available internally, and that someone should create some tool to generate that from the spec. But turns out it already exists in the open! https://github.com/apple/pkl-k8s-examples https://github.com/apple/pkl-k8s-examples
- crabique 3y agoWhy yes, I would like to see more of those in my k8s, so glad we finally have the technology https://github.com/apple/pkl-k8s-examples/blob/96ba7d415a85cfbf5b6ef396ca4d1592e8451e02/pkl/advanced/deployments.pkl#L46-L55 https://github.com/apple/pkl-k8s-examples/blob/96ba7d415a85c...
- physicles 3y agoComing from yaml+kustomize, all those curly braces are a tough sell. It looks like they roughly double the number of lines in the file.
- fzeindl 3y agoWhile I learned to accept YAML it messes up editor usage. It is so sensitive that basic text editing like copy and paste, tab, in/decreasing indent never quite do what I expect in IntelliJ. I paste parts of yaml into another yaml and it ends up somewhere unpredictable.
- manmal 3y agoCurly braces are great at ensuring correctness though, as goto fail; has shown.
- dev_0 3y ago[dead]