Helm's Hidden Quirks: Merging boolean values
Helm is a powerful tool for manageing Kubernetes applications. Despite its ubiquity in the kubernetes-world, there are some nuances to consider when working with boolean values—especially when merging complex objects.
Can't delete kubernetes namespace (NamespaceDeletionDiscoveryFailure)
While trying to delete a namespace on a kubernetes cluster I learned that there is a resource type apiservice :-) This post shows how to unblock deletions due orphaned apiservice definitions.
Unexpected behavior of TUN devices in Kubernetes >= 1.31.3
Sometimes, security improvements in one project can cause problems in places nobody ever expected. In this case, we had to deal with one of these improvements.
mysql - online index creation
This post shows how easy it is to alter tables (in this example index creation) online to keep your sql database uninterrupted and clients online.
Ansible - pretty print output
Sometimes you want to print more or extensive information on ansible output (in this case a terraform plan). This can easily be realised using an stdout callback.
Object attribute defaults on terraform - hello simplicity
Using terraform's object attributes defaults empowers you to create complex input values that still apply default values on a highly granular level. This post shows an example how to use this.
Configurable default values on terraform objects
Creating complex configurations requires many dimensions on the input - this post shows how to take care of default values in such a case to offer users of your code fine grained control without enforcing too much input if not required.
Terraform - applying complex default values
This post explores handling default values in Terraform. It shows merging default values with instance-specific values, using both native merge and the deepmerge module for recursive merging of nested objects. This approach ensures compact, maintainable code and seamless use of default values.
