Fosstodon

Brad L. :verified:Without proper IaC abstractions, K8S management is copying, pasting, and tweaking large amounts of YAML. It's a data entry job without any proper data entry controls pretending to be SRE. Kustomize + Flux is insufficient for professional K8S deployments, you need a lot better abstractions. This is a hill I will die on.<a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> <a href="https://hachyderm.io/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://hachyderm.io/tags/flux" class="mention hashtag" rel="nofollow noopener" target="_blank">#flux</a> <a href="https://hachyderm.io/tags/iaC" class="mention hashtag" rel="nofollow noopener" target="_blank">#iaC</a>

Kevin Davin🚀 New (minor) release for <a href="https://mastodon.davinkevin.fr/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a>, v5.7.0: Main evolution, we can use replacement with a static value!Another good way to replace domain in `ingress` instead of the ugly ${HOSTNAME} managed by another tool.Full changelog: <a href="https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize/v5.7.0" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize/v5.7.0</a><a href="https://mastodon.davinkevin.fr/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://learnk8s.news/@K8sArchitect" class="u-url mention" rel="nofollow noopener" target="_blank">@K8sArchitect</a> <a href="https://mastodon.davinkevin.fr/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> <a href="https://mastodon.davinkevin.fr/tags/release" class="mention hashtag" rel="nofollow noopener" target="_blank">#release</a> <a href="https://mastodon.davinkevin.fr/tags/K8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#K8s</a>

Allan :emacs:The strongest motivation for me to start developing in <a href="https://mastodon.xyz/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#golang</a> is to help contribute to <a href="https://mastodon.xyz/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a>, perhaps the most important <a href="https://mastodon.xyz/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> configuration management tool out there. A little sad for someone like myself who loves programming languages because I can only see the collaborative benefits of using Go. I really don't like it as a programming language.

:rss: Hacker NewsShow HN: Koreo – The platform engineering toolkit for Kubernetes <a href="https://koreo.dev/" rel="nofollow noopener" translate="no" target="_blank">https://koreo.dev/</a> <a href="https://rss-mstdn.studiofreesia.com/tags/ycombinator" class="mention hashtag" rel="nofollow noopener" target="_blank">#ycombinator</a> <a href="https://rss-mstdn.studiofreesia.com/tags/YAML" class="mention hashtag" rel="nofollow noopener" target="_blank">#YAML</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Infrastructure_as_Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infrastructure_as_Code</a> <a href="https://rss-mstdn.studiofreesia.com/tags/IaC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IaC</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Platform_Engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#Platform_Engineering</a> <a href="https://rss-mstdn.studiofreesia.com/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Configuration_Management" class="mention hashtag" rel="nofollow noopener" target="_blank">#Configuration_Management</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Resource_Orchestration" class="mention hashtag" rel="nofollow noopener" target="_blank">#Resource_Orchestration</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Helm</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Koreo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Koreo</a>

Nicolas Fränkel 🇺🇦🇬🇪I’m continuing my series on running the test suite for each PR on <a href="https://mastodon.top/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a>. In the previous post, I laid the groundwork for our learning journey.This week, I will raise the ante:* Create and configure a <a href="https://mastodon.top/tags/GoogleKubernetesEngine" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoogleKubernetesEngine</a> instance * Create a Kubernetes manifest for the app, with <a href="https://mastodon.top/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> for customization * Allow the <a href="https://mastodon.top/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> workflow to use the <a href="https://mastodon.top/tags/GKE" class="mention hashtag" rel="nofollow noopener" target="_blank">#GKE</a> instance * Build the Docker image and store it in the GitHub Docker repo * Finally, run the end-to-end test<a href="https://blog.frankel.ch/pr-testing-kubernetes/2/" rel="nofollow noopener" translate="no" target="_blank">https://blog.frankel.ch/pr-testing-kubernetes/2/</a>

Sten the StenSwapping <a href="https://fosstodon.org/tags/Flux2" class="mention hashtag" rel="tag">#Flux2</a> for <a href="https://fosstodon.org/tags/ArgoCD" class="mention hashtag" rel="tag">#ArgoCD</a>, <a href="https://fosstodon.org/tags/Kustomize" class="mention hashtag" rel="tag">#Kustomize</a> for <a href="https://fosstodon.org/tags/Helm" class="mention hashtag" rel="tag">#Helm</a>. I see what I'm gaining but it's rough starting more or less from knowing nothing. <a href="https://fosstodon.org/tags/kubernetes" class="mention hashtag" rel="tag">#kubernetes</a>

Arthur Lutz (Zenika)☸️ À la recherche d'alternatives à Kustomize ou Helm, je tombe sur <a href="https://kubes.guru/" rel="nofollow noopener" translate="no" target="_blank">https://kubes.guru/</a> Vous connaissez ?Voici un comparatif (orienté) qui fait la promotion de kubes <a href="https://blog.boltops.com/2020/11/05/kustomize-vs-helm-vs-kubes-kubernetes-deploy-tools/" rel="nofollow noopener" translate="no" target="_blank">https://blog.boltops.com/2020/11/05/kustomize-vs-helm-vs-kubes-kubernetes-deploy-tools/</a>Intéressé notamment par la partie "Layering" <a href="https://kubes.guru/docs/layering/" rel="nofollow noopener" translate="no" target="_blank">https://kubes.guru/docs/layering/</a><a href="https://pouet.chapril.org/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://pouet.chapril.org/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://pouet.chapril.org/tags/helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#helm</a>

xyhhx 🔻 (plz hire me)for those among us who prefer kustomize, i made the kyverno community policies available as such<a href="https://github.com/xyhhx/kyverno-policies-kustomize" rel="nofollow noopener" translate="no" target="_blank">https://github.com/xyhhx/kyverno-policies-kustomize</a><a href="https://nso.group/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://nso.group/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> <a href="https://nso.group/tags/kyverno" class="mention hashtag" rel="nofollow noopener" target="_blank">#kyverno</a> <a href="https://nso.group/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a>

xyhhx 🔻 (plz hire me)there's owncloud ocis, but they only offer a helm chart and that helm chart isn't even published.i could write a kustomization i guess but it seems like it'd be a super huge pain<a href="https://github.com/owncloud/ocis" rel="nofollow noopener" translate="no" target="_blank">https://github.com/owncloud/ocis</a><a href="https://nso.group/tags/ownCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#ownCloud</a> <a href="https://nso.group/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://nso.group/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://nso.group/tags/selfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfHosted</a>

Habr[Перевод] Размышления о декларативной конфигурацииНе кажется ли вам, что декларативная конфигурация и программирование инфраструктуры не так уж хороши, как их расхваливают? Я достаточно долго занимался декларативной конфигурацией в Kubernetes : размышлял о ней , работал с kubectl apply , KRM , kustomize , Google Cloud Config Sync , kpt , porch , ... В то же время параллельно развивалась декларативная автоматизация — эта работа велась в Google, где на протяжении многих лет широко использовалась декларативная конфигурация . При этом вне Google появился Terraform, и на этом лоскутном одеяле также возникло множество других инструментов. Что же такое декларативная конфигурация, в каких случаях она хороша, и как к ней подступиться?<a href="https://habr.com/ru/companies/timeweb/articles/860844/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/companies/timeweb/articles/860844/</a><a href="https://zhub.link/tags/timeweb_%D1%81%D1%82%D0%B0%D1%82%D1%8C%D0%B8_%D0%BF%D0%B5%D1%80%D0%B5%D0%B2%D0%BE%D0%B4" class="mention hashtag" rel="nofollow noopener" target="_blank">#timeweb_статьи_перевод</a> <a href="https://zhub.link/tags/terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#terraform</a> <a href="https://zhub.link/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://zhub.link/tags/KRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#KRM</a> <a href="https://zhub.link/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://zhub.link/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://zhub.link/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://zhub.link/tags/%D0%B4%D0%B5%D0%BA%D0%BB%D0%B0%D1%80%D0%B0%D1%82%D0%B8%D0%B2%D0%BD%D0%B0%D1%8F_%D0%B0%D0%B2%D1%82%D0%BE%D0%BC%D0%B0%D1%82%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8F" class="mention hashtag" rel="nofollow noopener" target="_blank">#декларативная_автоматизация</a> <a href="https://zhub.link/tags/iac" class="mention hashtag" rel="nofollow noopener" target="_blank">#iac</a> <a href="https://zhub.link/tags/typescript" class="mention hashtag" rel="nofollow noopener" target="_blank">#typescript</a>

TSM at WorkOne ConfigMap, one <a href="https://noc.social/tags/ArgoCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArgoCD</a> Application, lots of patches and replacements, <a href="https://noc.social/tags/NOFEAR" class="mention hashtag" rel="nofollow noopener" target="_blank">#NOFEAR</a>. All hail the relentlessly DRY <a href="https://noc.social/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> stack.

HabrПуть в GitOps или как мы перевели кластер Kubernetes под управление Argo CDВсем привет! Если вы работаете с Kubernetes, то, скорее всего, используете kubectl, kustomize или Helm для развёртывания сервисов в кластере. Про последнюю утилиту я уже писал статью — можно посмотреть тут . Тогда я рассказал о своём опыте внедрения этого инструмента для собственных нагрузок и сравнил подходы kubectl apply и helm install. Управление конфигурацией в Kubernetes может осуществляться с помощью различных инструментов. Помимо Helm, можно использовать просто YAML-манифесты или же kustomize. Для каждого из этих инструментов предусмотрена своя команда. В данной статье мы рассмотрим подход GitOps для K8s-кластеров и применим такой инструмент, как Argo CD.<a href="https://habr.com/ru/articles/842934/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/842934/</a><a href="https://zhub.link/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://zhub.link/tags/argocd" class="mention hashtag" rel="nofollow noopener" target="_blank">#argocd</a> <a href="https://zhub.link/tags/gitops" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitops</a> <a href="https://zhub.link/tags/helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#helm</a> <a href="https://zhub.link/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://zhub.link/tags/yaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#yaml</a> <a href="https://zhub.link/tags/iac" class="mention hashtag" rel="nofollow noopener" target="_blank">#iac</a> <a href="https://zhub.link/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://zhub.link/tags/infrastructureasacode" class="mention hashtag" rel="nofollow noopener" target="_blank">#infrastructureasacode</a>

gyptazyOh, dear! <a href="https://gyptazy.ch/snac?t=harvester" class="mention hashtag" rel="nofollow noopener" target="_blank">#Harvester</a> with a different <a href="https://gyptazy.ch/snac?t=csi" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSI</a> with <a href="https://gyptazy.ch/snac?t=trident" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trident</a> on <a href="https://gyptazy.ch/snac?t=nfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#NFS</a> would be really awesome. Finally managing the whole cluster farm(s) in a 100% <a href="https://gyptazy.ch/snac?t=gitops" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitOps</a> approach with <a href="https://gyptazy.ch/snac?t=argocd" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArgoCD</a>, <a href="https://gyptazy.ch/snac?t=kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> and <a href="https://gyptazy.ch/snac?t=argoworkflows" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArgoWorkflows</a>. Booting the host nodes diskless from an iSCSI target with read-only OS. Unfortunately, it seems like I need to wait until March 2025 with release 1.5…

SheogorathDeployed and documented my paperless setup over the past few days:<a href="https://gitops-docs.s3.shivering-isles.com/apps/paperless.html" rel="nofollow noopener" translate="no" target="_blank">https://gitops-docs.s3.shivering-isles.com/apps/paperless.html</a>It's still in the early stages so no automation for scanning on alike, but the direction feels good.<a href="https://microblog.shivering-isles.com/tags/paperless" class="mention hashtag" rel="nofollow noopener" target="_blank">#paperless</a> <a href="https://microblog.shivering-isles.com/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://microblog.shivering-isles.com/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://microblog.shivering-isles.com/tags/GitOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitOps</a>

seani love how every google search for what i think should be a basic feature in <a href="https://noc.social/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> leads to 6 diff github issues all asking for the same feature while accusing the project maintainers of being architect astronauts. who knew <a href="https://noc.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> was so wild!

drmorrFor those of you following along at home, SimKube now supports Kustomize! No more janky NodeJS required to create your YAML.<a href="https://github.com/acrlabs/simkube" rel="nofollow noopener" translate="no" target="_blank">https://github.com/acrlabs/simkube</a><a href="https://hachyderm.io/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> <a href="https://hachyderm.io/tags/simkube" class="mention hashtag" rel="nofollow noopener" target="_blank">#simkube</a> <a href="https://hachyderm.io/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a>

Peter BittnerWhy Helm, Kustomize and Kubernetes Operators may not be the last word in wisdom. <a href="https://mastodon.social/tags/helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#helm</a> <a href="https://mastodon.social/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://mastodon.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://mastodon.social/tags/operators" class="mention hashtag" rel="nofollow noopener" target="_blank">#operators</a> <a href="https://mastodon.social/tags/deployment" class="mention hashtag" rel="nofollow noopener" target="_blank">#deployment</a> <a href="https://mastodon.social/tags/operations" class="mention hashtag" rel="nofollow noopener" target="_blank">#operations</a> <a href="https://mastodon.social/tags/automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#automation</a> <a href="https://mastodon.social/tags/juju" class="mention hashtag" rel="nofollow noopener" target="_blank">#juju</a> <a href="https://mastodon.social/tags/charms" class="mention hashtag" rel="nofollow noopener" target="_blank">#charms</a> <a href="https://juju.is/blog/beyond-helm-and-kustomize-the-future-of-kubernetes-apps" rel="nofollow noopener" translate="no" target="_blank">https://juju.is/blog/beyond-helm-and-kustomize-the-future-of-kubernetes-apps</a>

Kevin Davin🚀 <a href="https://bird.makeup/users/fluxcd" class="u-url mention" rel="nofollow noopener" target="_blank">@fluxcd</a> & `HelmRelease`: A powerful combo, but can be even better!A guide explores <a href="https://mastodon.davinkevin.fr/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> for a more streamlined, auditable GitOps workflow. 🕵️<a href="https://link.davinkevin.fr/flux-and-helmrelease" rel="nofollow noopener" translate="no" target="_blank">https://link.davinkevin.fr/flux-and-helmrelease</a><a href="https://mastodon.davinkevin.fr/tags/FluxCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FluxCD</a> <a href="https://mastodon.davinkevin.fr/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> <a href="https://mastodon.davinkevin.fr/tags/Helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Helm</a> <a href="https://mastodon.davinkevin.fr/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://bird.makeup/users/kubernetesio" class="u-url mention" rel="nofollow noopener" target="_blank">@kubernetesio</a>

robrich<a href="https://dev.to/thenjdevopsguy/getting-started-with-kustomize-for-kubernetes-32nh" rel="nofollow noopener" translate="no" target="_blank">https://dev.to/thenjdevopsguy/getting-started-with-kustomize-for-kubernetes-32nh</a> - <a href="https://hachyderm.io/tags/Kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kustomize</a> is built-in to <a href="https://hachyderm.io/tags/kubectl" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubectl</a>. Override vars in <a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> yaml files. Maybe easier than .env files or sed. Nice walkthrough <a href="https://www.linkedin.com/in/michaellevan/" rel="nofollow noopener" translate="no" target="_blank">https://www.linkedin.com/in/michaellevan/</a>.

SheogorathSpend the afternoon refactoring my <a href="https://microblog.shivering-isles.com/tags/immich" class="mention hashtag" rel="nofollow noopener" target="_blank">#immich</a> deployment. Went from the "app-template"-based upstream helm chart to an own, kustomize-based setup.I optimized it a bit, so it's usable for anyone. You just have to take care of implementing your own redis and postgres component if they don't match mine :)<a href="https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/blob/3d9c54bbac1be4125f8c62de90cd2e1c830afd42/apps/base/immich/README.md" rel="nofollow noopener" translate="no" target="_blank">https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/blob/3d9c54bbac1be4125f8c62de90cd2e1c830afd42/apps/base/immich/README.md</a>Now the question becomes: Should this go upstream? Is it too redundant to the existing helm chart?I'll ponder on that a little.<a href="https://microblog.shivering-isles.com/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://microblog.shivering-isles.com/tags/kustomize" class="mention hashtag" rel="nofollow noopener" target="_blank">#kustomize</a> <a href="https://microblog.shivering-isles.com/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a>

Recent searches

Search options

Administered by:

Server stats:

#kustomize