#jsonnet — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jsonnet, aggregated by home.social.
-
While working through my #selfhosting setup and splitting it into a public and one private part, I wonder if I am still not yet deep enough into #Kustomize or if I would eventually hit a wall and end up using something closer to a programming language like #Nix or #Jsonnet to generate the #Kubernetes manifests.
-
Hey, do you operate one or multiple kubernetes clusters? Doesnt matter if just for fun, for learning, or in a professional way.
Do you use jsonnet and monitoring mixins? This thing here:
https://monitoring.mixins.dev/
If yes: How do you manage your deploy pipeline from mixin to prometheus/grafana?
If no: why not?
Boosts appreciated.
-
Колега поскаржився, що ненавидить #YAML та через це не сприймає #helm та шукаю альтернативу встановлення додадків в #Kubernetes. З реальних альтернатив є тільки #Jsonnet / #Tanka, але поріг входу значно вище, та розповсюдженість значно менша. Багато вендорів орієнтуються на дефакто стандарт додадків в Kubernetes. Так, Helm має свої мінуси та дивне форматування, синтаксис від #Go, але саме його обирає більшість.
#cloud #devops -
Reaction v2 : un régal
Tout d’abord, qu’est-ce que reaction ?
C’est un dæmon qui analyse les sorties d'un programme à la recherche de motifs répétitifs et qui prend des mesures (définition tirée du wiki de reaction).A daemon that scans program outputs for repeated patterns, and takes action.
Un exemple simple : la surveillance des logs de SSH et le blocage des adresses IP qui échouent plusieurs fois.
Oui, c’est exactement un des usages de fail2ban. Mais reaction a pour lui de grands avantages :
- il est écrit dans un langage compilé, ce qui lui permet d’avoir une moindre consommation de ressources ;
- sa syntaxe de configuration est bien plus simple à comprendre et écrire que celle de fail2ban ;
Je suis et j’utilise reaction depuis déjà quelques temps, et je suis tellement enthousiaste à propos de ce projet que j’ai passé un peu de temps pour apporter ma pierre à ce belle édifice l’année dernière 🙂
Et cette v2 alors ?
Et bien tout d’abord, il s’agit d’une réécriture en Rust, langage réputé pour sa sûreté mémoire et ses performances. Reaction était précédemment écrit en Go, qui n’est pas mauvais, mais qui semble, ici tout du moins, se faire surpasser par Rust.
Ensuite, et surtout, c’est le fait de pouvoir utiliser tout un dossier pour y mettre de la configuration qui m’enthousiasme ! En effet, comme j’automatise au maximum la configuration avec Salt, la création de zéro d’un fichier de configuration qui doit prendre en compte toutes les particularités de chaque machine est très laborieux. Et cela interdit de modifier localement le fichier de configuration, puisque cette modification pourrait se faire écraser suite à un déploiement automatisé d’une nouvelle configuration.
Désormais, plus de problème : je vais pouvoir avoir une configuration de base déployée automatiquement, avec des ajustements particuliers définis dans des fichiers particuliers (histoire de ne pas tout mélanger), et je pourrais toujours ajouter des règles sur une machine à la main si ça me chante !
Je suis en train de déployer ça chez Framasoft et plus j’avance, plus je me dis que les possibilités sont infinies 🚀Et comment ça s’utilise ?
Ah bah ça, c’est pas le but de cet article. Le plus simple est d’aller sur https://reaction.ppom.me/ pour découvrir comment utiliser reaction puis d’aller sur https://framagit.org/ppom/reaction/-/releases pour le télécharger et l’installer.
Juste un conseil : il peut être tentant de configurer reaction avec des fichiers YAML dont la syntaxe est simple et bien connue, mais Jsonnet est plus puissant, surtout grâce à ses systèmes d’import. Ça vaut vraiment le coup de prendre un peu de temps pour s’y pencher.
-
One thing that has been a game-changer for managing Kubernetes (K8s) is Jsonnet! 🛠️
I currently use Tanka, but it's not the only way to apply Jsonnet configurations. To be honest, though, it's probably the most practical one these days. Still, Tanka alone doesn’t offer as much as Jsonnet itself does. >>>
#Jsonnet #Tanka #Kubernetes #K8s #DevOps #ConfigurationManagement
-
🎉 OK, I've reanimated my Matrix homeserver with Dendrite. It works like a charm and it took me just around a half an hour to setup everything.
❤️ Once again Tanka with Jsonnet proved themselves as an invaluable tool.
👍 Also, the instructions for setting up Dendrite provided all the needed details but weren't bloated with information that made them really easy to follow.
-
🎉 OK, I've reanimated my Matrix homeserver with Dendrite. It works like a charm and it took me just around a half an hour to setup everything.
❤️ Once again Tanka with Jsonnet proved themselves as an invaluable tool.
👍 Also, the instructions for setting up Dendrite provided all the needed details but weren't bloated with information that made them really easy to follow.
-
Just learned about #jsonnet. Of course, of COURSE there is another fucking config format that I need to learn.
-
by the looks of it, the best jsonnet support is currently possible within vim
You got languageServer and syntax highlighting all for free!
🧵
-
@lawouach I see, recently I also took a look at #cuelang #dhalllang and #jsonnet but for a team that is not coming from a functional programming background with not a lot seniority, #helm still seems more appealing, even without considering the ubiquity of it. Or that was the impression that I got.
-
@lawouach I see, recently I also took a look at #cuelang #dhalllang and #jsonnet but for a team that is not coming from a functional programming background with not a lot seniority, #helm still seems more appealing, even without considering the ubiquity of it. Or that was the impression that I got.
-
@lawouach I see, recently I also took a look at #cuelang #dhalllang and #jsonnet but for a team that is not coming from a functional programming background with not a lot seniority, #helm still seems more appealing, even without considering the ubiquity of it. Or that was the impression that I got.
-
@lawouach I see, recently I also took a look at #cuelang #dhalllang and #jsonnet but for a team that is not coming from a functional programming background with not a lot seniority, #helm still seems more appealing, even without considering the ubiquity of it. Or that was the impression that I got.
-
@lawouach I see, recently I also took a look at #cuelang #dhalllang and #jsonnet but for a team that is not coming from a functional programming background with not a lot seniority, #helm still seems more appealing, even without considering the ubiquity of it. Or that was the impression that I got.
-
So, I'm using Jsonnet with Tanka for configuration of my cluster. This includes Conduit as well.
I've decided to extract the code I use to configure Conduit into a jsonnet library.
Here it is: https://codeberg.org/lig/conduit-jsonnet -
So, I've migrated from matrix.org to my own dabar.chat running Conduit.
Despite some caveats I'm happy I've done it.
Things I'm using: a VPS on Linode, k3s, Tanka for configuration, cert-manager. -
Blogged:
TIL - Adjusting Json.NET settings in Azure Durable Functions
Passing objects from a third-party library between functions required a deep-dive into the internals. #JsonNet #AzureFunctions #100DaysToOffload #TIL
https://www.synesthesia.co.uk/note/2023/06/21/adjusting-json-net-settings-in-azure-durable-functions/ -
I have to wonder why #jsonnet is so slow. It's slow enough that I can hardly see the point of using it in preference to just about any other language with built in JSON serialisation.
-
Moved my set of tiddlywikis to a new home: they sed to live on my synology but its docker management is a huge PITA so now they live in my tiny German cloud.
While at it, I added the oauth2-proxy so I don't have to deal with the basic auth popups in chrome anymore.
I've been using a mix of nix and yaml to define my k8s configuration lately (yamls for anything trivial, nix for anything computational) and I tend to like it more than #jsonnet. And, of course, anything is better than #helm.
-
But it doesn't have to be about DevOps at all. Jsonnet can help you to generate any configuration in almost any format in a slightly unusual but robust way.
#devops #kubernetes #data #language #configuration #helm #jsonnet
-
One such brilliant find is Jsonnet (https://jsonnet.org/) Its developers describe it as "A data templating language for app and tool developers." and it is.
I strongly encourage everyone who deals with a lot of dynamic configurations to give it a try. Especially, Jsonnet strives in the DevOps area. Tools like Qbec and Tanka could flip one's view on how Kubernetes deployments could work. Unless you really like Helm of cause. ->#devops #kubernetes #data #language #configuration #helm #jsonnet
-
There are a lot of different technologies out there. Some technologies are popular, well established, and seem like a safe bet. Others didn't mature yet enough to use them in production.
However, many technologies are great but haven't got enough popularity yet to be on everybody's radar. I constantly keep looking for such technologies, and sometimes I'm able to find a real gem (I'm not talking about Ruby here). ->#devops #kubernetes #data #language #configuration #helm #jsonnet
-
The list of technologies I have love hate relationship with (in no particular order):
* SQLAlchemy
* GStreamer (especially Rust bindings)
* GTK
* asyncio in Python
* Jsonnet (a recent addition) -
Didn't I mention that #Jsonnet is awesome yet?
Anyway, it is awesome.
Why building around Jasonnet is good?
One of the reasons is interoperability. I use #qbec but I can and do use k8s-libs by Grafana that were written for #tanka.
Imagine you can exchange definitions between #Ansible and #Chef.Jsonnet is new yaml for #DevOps.
-
Been having some fun with nice technologies today.
Have migrated from Bind9 to coredns as the authoritative dns server for my domains.
It runs in k3s and has beed deployed using qbec.
Noice:)
BTW, Jsonnet is really fun to use.
-
In case someone decides to write a Qbec vs Tanka review, this would be highly appreciated and I'll do my best to share it as wide as possible.
It's a shame Qbec hasn't got the recognition it deserves being in many ways superior comparing to Tanka.
#tanka #qbec #jsonnet #k8s #kubernetes #devops #grafana #splunk
