Don’t repeat YAML in Kubernetes applications

Sick of repeating your configurations in multiple environments? Us too.

Interested in learning more?

We are looking for a select few early adopters/design partners.

1 + 11 =

The Problem:

The ease of container-based deployment has made it common practice to run an application in a variety of environments. At Yipee.io, we run our own application in production, staging, and development environments, from public clouds to developer laptops. This ability to easily replicate a significant application is extremely powerful; however, it also introduces the problem of maintaining several closely related but non-identical application configurations. When a change is made to the shared part of an application, how is it propagated to the different offshoots? Copy and paste is certainly not the answer.  Textual patches, as found in Helm or Kustomize, are helpful, but can be fragile if the shared part of an application changes in any significant way.

The Solution:

At Yipee.io, we believe the solution to this problem likely involves using concepts introduced by Helm and Kustomize together and packaged with a flexible and approachable GUI.  

Additionally, we believe APIs are necessary to integrate with your CI/CD processes and that all the configuration must be treated as code. Treating as code enables process like Gitflow to be utilized to ensure best practices are followed to ensure success.

Features include:

Visual diff / 3-way merge

Automatic change propagation

Conflict detection/notification

To learn more about keeping your Kubernetes applications dry, check out  DRY Kubernetes by Jerry Jackson.

Interested in learning more?

We are looking for a select few early adopters/design partners.

8 + 14 =