More than seven🔒 SSL Verified

Table of Contents

• ↓ Formalisation of a pattern we’ve seen for multi-toolchain installers
• ↓ Commoditization of the packaging part of the infrastructure-as-code stack
• ↓ What has this got to do with Kubernetes?
• ↓ Why you might care?
• ↓ The importance of agreement
• ↓ Knative Build and Docker Build
• ↓ Top Alternatives to morethanseven.net

6-Month Traffic Trend Estimate

Official Contact & Profiles

Visual representation extracted from morethanseven.net

Content Snippets from morethanseven.net

"Writing about code. Occasional other topics. Made by @garethr."

"We announced Cloud Native Application Bundles (CNAB) at DockerCon EU and Microsoft Connect just last week, and I spent a bunch of time talking to folks and anwsering questions about it at KubeCon too. As I’m heading home I thought it would be good to write down a few thoughts about what CNAB is. As I see it CNAB is two things:"

"The explosion of APIs for infrastructure services has led to a corresponding explosion of tools to help you manage and orchestrate them. From API clients for individual projects (countless Kubernetes configuration management tools) to cloud-provider specific tools (CloudFormation templates, ARM templates) to high-level DSLs (Ansible, Terraform). Throw in the configuration complexity clock (so we have Pulumi in Typescript, Terraform with it’s own HCL DSL, too much YAML everywhere) and we have a lot of tool options. I posit this choice is a good thing, and that we’re never going to see everyone agree on one approach or another. One pattern that has emerged is packaging API clients as Docker images. lachlanevenson/k8s-kubectl has seen 5 million pulls, there are CloudFormation images on Hub that have millions of pulls, the official Terraform image has more than 10 million pulls. There are also lots of projects like terraform-ansible-docker which use multiple tools at the same time. CNAB is a formalisation of these patterns."

"There is a now familiar pattern when it comes to infrastructure-as-code tools, namely the introduction of a package format and some form of registry. Puppet and the Forge. Chef and the Supermarket. Ansible and Ansible Galaxy. Terraform and the Module Registry. Everyone basically creates a tar file with some metadata. Not all projects have done this, but most would probably benefit from doing so. Compose files, ARM templates, CloudFormation templates; all are shared predominantly as source artefacts which are copy-and-pasted around."

Key Topics & Focus Areas for morethanseven.net:

Formalisation of a pattern we’ve seen for multi-toolchain installers

Commoditization of the packaging part of the infrastructure-as-code stack

What has this got to do with Kubernetes?

Why you might care?

The importance of agreement

Knative Build and Docker Build