Artifact versions regularly change and new releases come out. Cloud native software changes and it can be difficult to stay on top of the changes. Notifications and webhooks when updates come out are rarely available for consumers. The Artifact Hub is different. It now provides notifications and webhooks, that you can use for programming, when new releases of packages come out.
Helm v3 uses Kubernetes Secrets as the default method to store release information in a cluster. This bucks some newer trends, but if you look at the needs and features it turns out that Secrets are a good fit. In this post you’ll learn why Helm uses Secrets by default and how you can do something similar if Secrets fit well for you.
Naming things and anti-patterns are two things that have fascinated me. So, when Marc Atwood tweeted with a name for an anti-pattern I’d personally experienced I was excited to have a name to it. Marc tweeted:
today I asked a master of naming antipatterns for a name for the practice of naming directories in an evolving project after version numbers, instead of just using the VCS. His answer: “clutternaming”.
I have a Linux workstation I regularly use and I need to develop in Go on it. So, I want an easy way to install and upgrade Go. With Go, I need to use the latest version and usually don’t want the version I would get with apt-get or the systems conservative package manager.
I’ve become accustomed to using one command to install Go and a similar command to upgrade it.
One of the really powerful new features in Helm v3 is the use of JSON Schemas. This is great for validation, documentation, and it can be used for automated form generation. We’ll take a quick look at what they are, how you can generate them (i.e. you don’t need to write the whole thing by hand), and how they can be used to generate web forms.