#kustomize — Public Fediverse posts

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

The LPI DevOps Tools Engineer 2.0 certification expects candidates to have familiarity with #Helm, #Kustomize, #FluxCD, and #ArgoCD.

Explore exam objective 703.3: Kubernetes Package Management with Fabian Thorns and Uirá Ribeiro to learn more: https://lpi.org/tb0t

Prepare for your DevOps exam with free LPI Learning Materials!

#kubernetes #devops #gitops #cloudnative #opensource #FOSS #LPI

I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.

I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra

@launchpad023

#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem

I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.

I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra

@launchpad023

#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem

I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.

I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra

@launchpad023

#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem

I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.

I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra

@launchpad023

#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem

I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.

I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra

@launchpad023

#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem

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.

Heads down into #Kubernetes #Kustomize land. Not as easy as I assumed it to be 😳

Might be that this is due to the combo with #Flux and trying to make reusable blocks is just not so easy in this context.

Could also be that I am just on a learning journey here.

This weekend's learning activity was figuring out a good way to make k8s templates out of my YAML files. There are a number of ways to do this, including from Ansible or Helm, but after looking at Kustomize, that's the best way for me to go.

Ansible could do it by either:
a) native k8s modules in ansible
b) with YAML files, and the template function, which would just do variable substitution

Helm is extremely overkill for my use case, although I'm sure I could get it to cooperate.

Kustomize is the best mix of $inputFiles + modifications = $outputFiles per environment, and I really like how it works.

You define your top level YAML files and then tell the environments in an overlays/ directory how you want things to change. You can even have it apply a namespace to all resources in there so it's never forgotten or replace values such as ingress hostnames, which have to be unique per env anyways.

This will let me write one set of files and then push the YAML to k8s properly. I also fully intend to use this for a DR kind of situation where I need to recover everything.

All of this will fit very well into my new Gitea instance, replete with an Actions runner.

#homelab #k8s #kubernetes #kustomize #learning #neverstoplearning #technology #yaml #selfhosted

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.

#k8s #kustomize #flux #iaC

🚀 New (minor) release for #Kustomize, 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: https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize/v5.7.0

#Kubernetes @K8sArchitect #Kustomize #release #K8s

The strongest motivation for me to start developing in #golang is to help contribute to #kustomize, perhaps the most important #kubernetes 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.

Show HN: Koreo – The platform engineering toolkit for Kubernetes
https://koreo.dev/
#ycombinator #YAML #Infrastructure_as_Code #IaC #Platform_Engineering #DevOps #Kubernetes #Configuration_Management #Resource_Orchestration #Helm #Kustomize #Koreo

Show HN: Koreo – The platform engineering toolkit for Kubernetes
https://koreo.dev/
#ycombinator #YAML #Infrastructure_as_Code #IaC #Platform_Engineering #DevOps #Kubernetes #Configuration_Management #Resource_Orchestration #Helm #Kustomize #Koreo

Show HN: Koreo – The platform engineering toolkit for Kubernetes
https://koreo.dev/
#ycombinator #YAML #Infrastructure_as_Code #IaC #Platform_Engineering #DevOps #Kubernetes #Configuration_Management #Resource_Orchestration #Helm #Kustomize #Koreo

Show HN: Koreo – The platform engineering toolkit for Kubernetes
https://koreo.dev/
#ycombinator #YAML #Infrastructure_as_Code #IaC #Platform_Engineering #DevOps #Kubernetes #Configuration_Management #Resource_Orchestration #Helm #Kustomize #Koreo

I’m continuing my series on running the test suite for each PR on #Kubernetes. In the previous post, I laid the groundwork for our learning journey.

This week, I will raise the ante:

* Create and configure a #GoogleKubernetesEngine instance
* Create a Kubernetes manifest for the app, with #Kustomize for customization
* Allow the #GitHub workflow to use the #GKE instance
* Build the Docker image and store it in the GitHub Docker repo
* Finally, run the end-to-end test

https://blog.frankel.ch/pr-testing-kubernetes/2/

[Перевод] Размышления о декларативной конфигурации

Не кажется ли вам, что декларативная конфигурация и программирование инфраструктуры не так уж хороши, как их расхваливают? Я достаточно долго занимался декларативной конфигурацией в Kubernetes : размышлял о ней , работал с kubectl apply , KRM , kustomize , Google Cloud Config Sync , kpt , porch , ... В то же время параллельно развивалась декларативная автоматизация — эта работа велась в Google, где на протяжении многих лет широко использовалась декларативная конфигурация . При этом вне Google появился Terraform, и на этом лоскутном одеяле также возникло множество других инструментов. Что же такое декларативная конфигурация, в каких случаях она хороша, и как к ней подступиться?

https://habr.com/ru/companies/timeweb/articles/860844/

#timeweb_статьи_перевод #terraform #kubernetes #KRM #google #kustomize #cloud #декларативная_автоматизация #iac #typescript

One ConfigMap, one #ArgoCD Application, lots of patches and replacements, #NOFEAR. All hail the relentlessly DRY #kustomize stack.

Путь в GitOps или как мы перевели кластер Kubernetes под управление Argo CD

Всем привет! Если вы работаете с Kubernetes, то, скорее всего, используете kubectl, kustomize или Helm для развёртывания сервисов в кластере. Про последнюю утилиту я уже писал статью — можно посмотреть тут . Тогда я рассказал о своём опыте внедрения этого инструмента для собственных нагрузок и сравнил подходы kubectl apply и helm install. Управление конфигурацией в Kubernetes может осуществляться с помощью различных инструментов. Помимо Helm, можно использовать просто YAML-манифесты или же kustomize. Для каждого из этих инструментов предусмотрена своя команда. В данной статье мы рассмотрим подход GitOps для K8s-кластеров и применим такой инструмент, как Argo CD.

https://habr.com/ru/articles/842934/

#kubernetes #argocd #gitops #helm #kustomize #yaml #iac #devops #infrastructureasacode

Deployed and documented my paperless setup over the past few days:

https://gitops-docs.s3.shivering-isles.com/apps/paperless.html

It's still in the early stages so no automation for scanning on alike, but the direction feels good.

#paperless #kubernetes #kustomize #GitOps

i love how every google search for what i think should be a basic feature in #kustomize leads to 6 diff github issues all asking for the same feature while accusing the project maintainers of being architect astronauts. who knew #devops was so wild!

🚀 @fluxcd & `HelmRelease`: A powerful combo, but can be even better!

A guide explores #kustomize for a more streamlined, auditable GitOps workflow. 🕵️

https://link.davinkevin.fr/flux-and-helmrelease

#FluxCD #Kustomize #Helm #DevOps @kubernetesio

https://dev.to/thenjdevopsguy/getting-started-with-kustomize-for-kubernetes-32nh - #Kustomize is built-in to #kubectl. Override vars in #k8s yaml files. Maybe easier than .env files or sed. Nice walkthrough https://www.linkedin.com/in/michaellevan/.

Spend the afternoon refactoring my #immich 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 :)

https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/blob/3d9c54bbac1be4125f8c62de90cd2e1c830afd42/apps/base/immich/README.md

Now the question becomes: Should this go upstream? Is it too redundant to the existing helm chart?

I'll ponder on that a little.

#Kubernetes #kustomize #k8s

Is #appOfApps the right pattern for you? Read the new blog post and find out. 🔗https://op1.st/is-app-of-apps-the-right-pattern | #operatefirst #gitops #operations @argoproj #kustomize #kubernetes

I hope tomorrow’s #cutover of two #UAT environments to the #cloud go so smoothly that we can genuinely call it #RinseAndRepeat. (Hey #Ansible, you’re on deck!)

Maybe we’ll even have enough time to get that #kubernetes #cluster from a #deprecated version to something more recent and reasonable. I would hate for all my #kustomize #shenanigans to go to waste!

Everything will go perfectly swimmingly, until #MurphysLaw decides to show up. #GirdYourLoins folks, it could get weird.

I spent my weekend with #argocd, #eks, #codepipeline, #kustomize and all things #gitops to prepare a demo for a client. I feel worn out... But happy! Automation will always be my true passion 💚 #devops #aws :aws_logo:

Thinking about #kustomize that would excel in #declarative programming and overlays vs Helm...

What about using general purpose functional programming? Using a YAML type provider in #fsharp can provide strong typing for YAML configuration files, making it easier to work with YAML data in a more type-safe manner. It would be more familiar to me than #cuelang.

Well, the combination of #golang and #cuelang appears to be the most common choice.

You know something is #hinky when the #operator you installed in the #kubernetes cluster to make #rbac easier is in a #racecondition against fairly ordinary #kustomize stacks that manage service accounts in namespaces where business workloads will actually run. Because arbitrarily changing service account tokens is exactly what I want to #debug on my first day back from a long break. 🙃 It’s important work for the cluster, but it doesn’t feel like progress.

Thinking about #kustomize that would excel in #declarative programming and overlays vs Helm...

What about using general purpose functional programming? Using a YAML type provider in #fsharp can provide strong typing for YAML configuration files, making it easier to work with YAML data in a more type-safe manner. It would be more familiar to me than #cuelang.

Well, the combination of #golang and #cuelang appears to be the most common choice.

Thinking about #kustomize that would excel in #declarative programming and overlays vs Helm...

What about using general purpose functional programming? Using a YAML type provider in #fsharp can provide strong typing for YAML configuration files, making it easier to work with YAML data in a more type-safe manner. It would be more familiar to me than #cuelang.

Well, the combination of #golang and #cuelang appears to be the most common choice.

Thinking about #kustomize that would excel in #declarative programming and overlays vs Helm...

What about using general purpose functional programming? Using a YAML type provider in #fsharp can provide strong typing for YAML configuration files, making it easier to work with YAML data in a more type-safe manner. It would be more familiar to me than #cuelang.

Well, the combination of #golang and #cuelang appears to be the most common choice.

Thinking about #kustomize that would excel in #declarative programming and overlays vs Helm...

What about using general purpose functional programming? Using a YAML type provider in #fsharp can provide strong typing for YAML configuration files, making it easier to work with YAML data in a more type-safe manner. It would be more familiar to me than #cuelang.

Well, the combination of #golang and #cuelang appears to be the most common choice.