Avis aux utilisateurs de #Terraform : la version 0.4 de #Burrito est disponible dès aujourd’hui 🎉Burrito, c’est un #TACoS développé en open source par @LonguetAlan. Découvrez les nouveautés de la version 0.4 et partagez-nous vos retours : https://t.co/p7vIxUZ8ED
@ArthurBusser@_StanGirard I don't think there's new security issues it's the same but in my opinion data permeability between tenants might be an harder nut to crack on LLM softwares
With @LonguetAlan we spent some time the last few months developing an open source TACoS Kubernetes Operator for @padok_m33. It's still experimental but we are spending a lot of time improving it. We'd love your feedback! https://t.co/BJd75LeZMD
Here’s why Pulumi can’t move the needle here. Pulumi is a neat concept, and a lot of people want a better interface to IaC than HCL. However, it’s a half step of progress.
Why?
@jefferai @padok_m33 @HashiCorp Like I said earlier this is achievable with a terraform module and that's ok, what I did is abstracting away the ACL and granting access to targets based on an input like this that represents the "scope" the grant will be setup on :
project/hostCatalog/hostSet.
@jefferai @padok_m33 @HashiCorp I think at some point I tried that, what I envision was something that isn't possible right now since targets are top-level entities. What I would have like to do is to give access to someone to all targets targeting hosts in a host catalog or a host set WDYT ?
@jefferai @padok_m33 @HashiCorp Also I wanted desperately to give access to multiple targets with a single ACL line based on Host Catalog or Host set, and I didn't seem to be able to do it so I ended up abstracting that part in a terraform module and generating 1 ACL per target
@jefferai @padok_m33 @HashiCorp But I think what I had the most issue with is this part : https://t.co/6rWKKvaYLS
At first I didn't see this page and could not understand why there was some ACL setup I couldn't achieve !
🚨#Discovery Alert🚨
Discovery is a series where a tech deep dive into a #technology and gives you his or her opinion on it!
@LonguetAlan, Lead SRE at Padok, deep dive into @HashiCorp's Boundary, a solution to securely access your system remotely😉
👉https://t.co/tCG1D6ed3H
On ne vous présente plus @sundayapp_ : l'app de paiement par QR code des restaurateurs 🍝
Découvrez comment les équipes @padok_m33 sont intervenues pour les aider à garantir la scalabilité de leur infrastructure 🌍
Pour obtenir le cas client 👉 https://t.co/VxTEA1qa9i
New Kubestory! If you want to know why I keep teaching Kubernetes concept to developers --->
KubeStory #004: A non-abstracted developers journey to Kubernetes.
https://t.co/nhZlMqWoix
@skaragulm@skaragulm I think you're right ! But how can we prioritize this training (which could take a lot of time and effort) over sacrificing a bit of business-oriented features delivery. My guess is this training is an investment not every company/person is ready to make :/
Comment détecter rapidement les comportements à risque sur votre cluster Kubernetes ? Ne cherchez plus : Oussama, SecOps chez Padok, vous parle de Falco !
👉https://t.co/OWiDNaX781
#Kubernetes#security#Falco
ArgoCD Image Updater updates your container versions for you!
Sacha, SRE at Padok, explains how to configure it, and lists the advantages and drawbacks of this new tool.
👉 https://t.co/jWFmM9MHa0
#ArgoCD#imageupdater#GitOps#devOps#Helm