Code Engineered

I have a Linux workstation I regularly use and I need to develop in Go on it.

One of the really powerful new features in Helm v3 is the use of JSON Schemas.

Graduating a CNCF project is no small feat.

Many of the cloud native and CNCF projects are based around artifacts that you can use and share.

Helm v2, the previous major version of the package manager for Kubernetes, makes calls out to the Internet when you initialize it.

Crafting the YAML to install applications on Kubernetes can be time consuming.

Operators have become a hot new pattern in use among cloud native organizations.

The Cloud Native Computing Foundation (CNCF) is having its annual Technical Oversight Committee (TOC) elections.

The Way Back Machine, part of the Internet Archive, backs up the web for us.

Drupal is a web platform, for lack of a better term, that I previously used a lot.

Today, the Helm Maintainers are proud to announce that we have successfully completed a 3rd party security audit for Helm 3.

Working with Go modules whose major version is 2 or greater is different than working version 0 or 1 and is different than doing so with the tools that came before it like dep and glide.

I’m happy to share that a new major release of github.com/Masterminds/semver, a semantic version package for Go, is here.

Go 1.13 was just released and by default is using a Google operated proxy to fetch module dependencies.

Have you ever needed to pick a log package for a Go project?

Before Go Modules and Dep there were numerous dependency managers including Glide.

No vendor, service provider, or thing supplying your organization is impervious to problems.

Over on Twitter, Greg Swift brought up an issue of the long Kubnerntes label names.

Over the years people have asked about breaking Helm up into a set of smaller tools.

Kubernetes is one of the hot technologies in cloud.

Public clouds are growing at a tremendous rate and many are moving at least some of their workloads to the public clouds.

On the Helm charts project the maintainers occasionally use the GitHub UI to make quick changes to a pull request.

When Helm moved from a CLA to a DCO it meant I needed to start adding a signoff to my commits on that project.

“Chop Wood Carry Water” is metaphor for doing the hard and non-glamorous work.

When DigitalOcean polled developers on serverless, for their June 2018 issue of currents, one of their findings was that half of developers did not have a strong understanding of serverless.

When Kustomize came into the spotlight conversations quickly moved to compare it to Helm.

While the Kubernetes Application Survey highlighted some things to be proud of, there were some major problems it highlighted as well.

At the heart of dependency management, whether we’re talking about programming languages or higher level platforms such as operating systems, is people.

What do users need from their package dependency management?

“Those who don’t know history are doomed to repeat it.” ― Edmund Burke There are many variations on this saying but the essential element is that it’s important, and I would argue useful, to know the history of something.

In my previous post I shared an example of how dependencies could break under vgo when semantic versioning rules are broken.

Note, a second post with some additional detail is available in a post titled “Go vgo: A Broken Dependency Tree”.

I’ve recently read numerous articles about bringing people back to the open web or about finding ways to grow it.

When it comes to applications, the last few years has been incredibly busy for Kubernetes.

Package management, dependency management, configuration management, and who knows how many other forms of management exist when it comes to computing systems.

Now that development for Helm version 3 has kicked off, I’m starting to hear a wide variety of opinions on what Helm should do and how it relates to what other platform package managers do.

Kubernetes development has been moving at breakneck speeds for some time.

Conflict seems to happen in open source communities.

Now that 2017 is behind us I wanted to take a look at how things went for Helm and the community charts in 2017.

For a few days I had both Frontier DSL (the new high speed kind) and Comcast Xfinity Internet running side by side.

If you’ve spent much time working with a public cloud you may have used tags or labels to organize your infrastructure.

For some time there has been a community managed set of Helm Charts to install applications into Kubernetes.

The Kubernetes community has a number of Kubernetes-isms.

Kubernetes is hard.

When charts, the packages for the Helm package manager, first started they were fairly simple.

Kubernetes configuration files are long and verbose.

Reviewing charts, the packages for Kuberentes Helm, is an often manual process.

There have been a number of recent discussion and some innovation around charts for Helm, the popular package manager for Kubernetes.

Photo by LindaInpijn Several years ago I worked on a WebDAV project.

Helm 2.0.0, the package manager for Kubernetes, was just released.