#kustomize — Public Fediverse posts

⚙️ HELM vs. KUSTOMIZE

Mamy tu jakichś adminów #Kubernetes? 👀
#Helm czy #Kustomize? Dwa podejścia, różne preferencje. Czego używacie? A może macie własne sposoby na zarządzanie konfiguracją?

Przy okazji przypominamy o trwającym #CFP na #JesieńLinuksowa! Szukamy prelekcji i warsztatów o #DevOps (i nie tylko)!

⏰ Zgłoszenia do 16 sierpnia!
👉 Zgłoś propozycję: https://jesien.org/2026/c4p

📍 Gdzie? Hotel Kolna, Kraków
📅 Kiedy? 23–25 października 2026

#Linux #OpenSource #SysAdmin

⚙️ HELM vs. KUSTOMIZE

Mamy tu jakichś adminów #Kubernetes? 👀
#Helm czy #Kustomize? Dwa podejścia, różne preferencje. Czego używacie? A może macie własne sposoby na zarządzanie konfiguracją?

Przy okazji przypominamy o trwającym #CFP na #JesieńLinuksowa! Szukamy prelekcji i warsztatów o #DevOps (i nie tylko)!

⏰ Zgłoszenia do 16 sierpnia!
👉 Zgłoś propozycję: https://jesien.org/2026/c4p

📍 Gdzie? Hotel Kolna, Kraków
📅 Kiedy? 23–25 października 2026

#Linux #OpenSource #SysAdmin

⚙️ HELM vs. KUSTOMIZE

Mamy tu jakichś adminów #Kubernetes? 👀
#Helm czy #Kustomize? Dwa podejścia, różne preferencje. Czego używacie? A może macie własne sposoby na zarządzanie konfiguracją?

Przy okazji przypominamy o trwającym #CFP na #JesieńLinuksowa! Szukamy prelekcji i warsztatów o #DevOps (i nie tylko)!

⏰ Zgłoszenia do 16 sierpnia!
👉 Zgłoś propozycję: https://jesien.org/2026/c4p

📍 Gdzie? Hotel Kolna, Kraków
📅 Kiedy? 23–25 października 2026

#Linux #OpenSource #SysAdmin

⚙️ HELM vs. KUSTOMIZE

Mamy tu jakichś adminów #Kubernetes? 👀
#Helm czy #Kustomize? Dwa podejścia, różne preferencje. Czego używacie? A może macie własne sposoby na zarządzanie konfiguracją?

Przy okazji przypominamy o trwającym #CFP na #JesieńLinuksowa! Szukamy prelekcji i warsztatów o #DevOps (i nie tylko)!

⏰ Zgłoszenia do 16 sierpnia!
👉 Zgłoś propozycję: https://jesien.org/2026/c4p

📍 Gdzie? Hotel Kolna, Kraków
📅 Kiedy? 23–25 października 2026

#Linux #OpenSource #SysAdmin

⚙️ HELM vs. KUSTOMIZE

Mamy tu jakichś adminów #Kubernetes? 👀
#Helm czy #Kustomize? Dwa podejścia, różne preferencje. Czego używacie? A może macie własne sposoby na zarządzanie konfiguracją?

Przy okazji przypominamy o trwającym #CFP na #JesieńLinuksowa! Szukamy prelekcji i warsztatów o #DevOps (i nie tylko)!

⏰ Zgłoszenia do 16 sierpnia!
👉 Zgłoś propozycję: https://jesien.org/2026/c4p

📍 Gdzie? Hotel Kolna, Kraków
📅 Kiedy? 23–25 października 2026

#Linux #OpenSource #SysAdmin

[Перевод] Лучшие практики по Kubernetes. Жаль, я не знала о них раньше

Недавно попался очень внятный материал от Pulumi про ключевые Kubernetes‑практики, которые начинаешь ценить, к сожалению, только после первых инцидентов и неприятных сюрпризов. Решила перевести для себя и коллег, а заодно положить на Хабр, добавив к переводу своих мыслей. В материале — ключевые практики для 2026 года: задавать requests и limits для каждого контейнера, изолировать нагрузки через namespaces и NetworkPolicy, автоматизировать health checks и еще много всего. Приглашаю под кат.

https://habr.com/ru/companies/cloud_ru/articles/1060100/

#kubernetes #gitopsпрактики #rbac #prometheus #helm #kustomize #pulumi #sbom #finops #kyverno

[Перевод] Лучшие практики по Kubernetes. Жаль, я не знала о них раньше

Недавно попался очень внятный материал от Pulumi про ключевые Kubernetes‑практики, которые начинаешь ценить, к сожалению, только после первых инцидентов и неприятных сюрпризов. Решила перевести для себя и коллег, а заодно положить на Хабр, добавив к переводу своих мыслей. В материале — ключевые практики для 2026 года: задавать requests и limits для каждого контейнера, изолировать нагрузки через namespaces и NetworkPolicy, автоматизировать health checks и еще много всего. Приглашаю под кат.

https://habr.com/ru/companies/cloud_ru/articles/1060100/

#kubernetes #gitopsпрактики #rbac #prometheus #helm #kustomize #pulumi #sbom #finops #kyverno

[Перевод] Лучшие практики по Kubernetes. Жаль, я не знала о них раньше

Недавно попался очень внятный материал от Pulumi про ключевые Kubernetes‑практики, которые начинаешь ценить, к сожалению, только после первых инцидентов и неприятных сюрпризов. Решила перевести для себя и коллег, а заодно положить на Хабр, добавив к переводу своих мыслей. В материале — ключевые практики для 2026 года: задавать requests и limits для каждого контейнера, изолировать нагрузки через namespaces и NetworkPolicy, автоматизировать health checks и еще много всего. Приглашаю под кат.

https://habr.com/ru/companies/cloud_ru/articles/1060100/

#kubernetes #gitopsпрактики #rbac #prometheus #helm #kustomize #pulumi #sbom #finops #kyverno

Streamline your GitOps with Flux Kustomize patches. This snippet shows how overlays for dev, staging, and production modify a common base using patchesStrategicMerge or patchesJson6902. Kubernetes v1.21+, Flux v2.x. #fluxcd #kustomize #gitops

https://www.valtersit.com/vault/using-flux-kustomize-patches-for-environment-overlays-c6b7cf/

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

First steps with #kluctl to experiment with it as a higher level wrapper around my #kustomize work.

I like the diff a lot.

First steps with #kluctl to experiment with it as a higher level wrapper around my #kustomize work.

I like the diff a lot.

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

My impression about #Kustomize is that reading the examples is more important than trying to read the information out of the documentation.

Had a few cases where I struggled because I accidentally worked against the tool. One was the name suffix generation of config maps and not knowing that one can configure custom name fields.

My impression about #Kustomize is that reading the examples is more important than trying to read the information out of the documentation.

Had a few cases where I struggled because I accidentally worked against the tool. One was the name suffix generation of config maps and not knowing that one can configure custom name fields.

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.

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.

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.

🤔 If I want to patch a patch, then it seems I better put this into a file instead of having it embedded.

#kustomize #kubernetes

🤔 If I want to patch a patch, then it seems I better put this into a file instead of having it embedded.

#kustomize #kubernetes

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.

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.

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.

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.

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

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

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

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

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

pushd overlays/dev
kustomize edit set image ...
popd
kustomize build ...

wait, what? is this the way-to-go with #kustomize?

https://github.com/kubernetes-sigs/kustomize/issues/2803

pushd overlays/dev
kustomize edit set image ...
popd
kustomize build ...

wait, what? is this the way-to-go with #kustomize?

https://github.com/kubernetes-sigs/kustomize/issues/2803

Is #kustomize alive? What are the reasons I should prefer it over #helm?

🏷️ #k8s #kubernetes

Is #kustomize alive? What are the reasons I should prefer it over #helm?

🏷️ #k8s #kubernetes

🚀 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

🚀 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

🚀 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

🚀 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

🚀 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.

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.

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.

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.

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/

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/

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/

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/