[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"tag-articles-gitops-1":3,"tag-formations-gitops-1":8},{"items":4,"total":5,"page":6,"size":7},[],0,1,9,{"items":9,"total":21,"page":6,"size":7},[10,41,61],{"id":11,"title":12,"slug":13,"excerpt":14,"cover_image_url":15,"for_member":16,"is_published":17,"views_count":18,"tags":19,"author":34,"created_at":39,"updated_at":40},5,"NeuVector en production : Zero Trust, fédération, cloisonnement par namespace et policy as code","scuriser-les-environnements-kubernetes-avec-suse-security-neuvector-du-dploiement-standalone-et-fdr-la-mise-en-pratique","Appliquer le Zero Trust à chaque container, sur plusieurs clusters Kubernetes : vous saurez fédérer NeuVector, faire entrer un cluster sans un clic avec Argo CD, cloisonner les équipes par namespace, bloquer au runtime et à l'admission, et scanner registries, clusters et nodes.","https:\u002F\u002Fs3-rnn.cloud.cetic-group.com\u002Fcl-0687463b-blog-techledger-media\u002Fdiagrams\u002F49f8ebc8f8d34cf4a4596f469cceb8b8.svg",false,true,1740,[20,23,27,31],{"id":21,"name":22,"slug":22},3,"kubernetes",{"id":24,"name":25,"slug":26},36,"sécurité","securite",{"id":28,"name":29,"slug":30},46,"GitOps","gitops",{"id":32,"name":33,"slug":33},24,"neuvector",{"id":35,"full_name":36,"pseudo":37,"function":38},38,"Ibrahima COULIBALY","coolibra","Cloud \u002F SRE & DevOps","2025-08-27T20:17:36.640766Z","2026-09-26T20:34:37.556240Z",{"id":42,"title":43,"slug":44,"excerpt":45,"cover_image_url":46,"for_member":16,"is_published":17,"views_count":47,"tags":48,"author":58,"created_at":59,"updated_at":60},27,"Crossplane, le platform engineering en pratique : construire l API self-service de votre plateforme","crossplane-le-platform-engineering-en-pratique-construire-l-api-self-service-de-votre-plateforme","Transformer un cluster Kubernetes en control plane qui provisionne et reconcilie l'infrastructure, puis en faire une API que les equipes produit appliquent elles-memes. Du provider a la managed resource, puis au XRD, aux composition functions et a la Configuration livree par GitOps.","https:\u002F\u002Fs3-rnn.cloud.cetic-group.com\u002Fcl-0687463b-blog-techledger-media\u002Fdiagrams\u002F6b01509ee0304b58955eb4069891e6e4.svg",60,[49,52,56,57],{"id":50,"name":51,"slug":51},49,"crossplane",{"id":53,"name":54,"slug":55},50,"platform engineering","platform-engineering",{"id":28,"name":29,"slug":30},{"id":21,"name":22,"slug":22},{"id":35,"full_name":36,"pseudo":37,"function":38},"2026-09-14T18:23:16.354159Z","2026-09-14T20:18:14.454220Z",{"id":62,"title":63,"slug":64,"excerpt":65,"cover_image_url":66,"for_member":16,"is_published":17,"views_count":67,"tags":68,"author":83,"created_at":84,"updated_at":85},23,"Helm et Kustomize, côte à côte : la même application packagée deux fois","helm-et-kustomize-cote-a-cote-la-meme-application-packagee-deux-fois","La même application packagée deux fois, avec Kustomize et avec Helm 4. Écrire un Helm chart correct, le tester, le signer et le publier, sur un dépôt HTTP comme sur un registre OCI. Puis les mettre en panne des deux façons : patches qui ne s'appliquent pas, templates qui rendent du YAML faux, releases bloquées, conflits de propriété. Chaque écart entre Helm 3 et Helm 4 est signalé.","https:\u002F\u002Fs3-rnn.cloud.cetic-group.com\u002Fcl-0687463b-blog-techledger-media\u002Fdiagrams\u002Fb1a01d715d054af3aa4f8eae61f6fe83.svg",71,[69,70,74,78,79],{"id":28,"name":29,"slug":30},{"id":71,"name":72,"slug":73},44,"Helm","helm",{"id":75,"name":76,"slug":77},45,"Kustomize","kustomize",{"id":21,"name":22,"slug":22},{"id":80,"name":81,"slug":82},47,"Packaging","packaging",{"id":35,"full_name":36,"pseudo":37,"function":38},"2026-09-06T07:47:07.764963Z","2026-09-09T19:08:42.654140Z"]