Advanced Kubernetes Development Tool

Tako is a Kubernetes development tool designed to enhance and automate the local app development lifecycle. It extends docker compose conversion functionality, offering multiple output formats, integrated external tooling, and a clear environment definition.

Quick start

Tako is an advanced development tool that enhances the conversion of docker compose to Kubernetes manifests, with intuitive configuration and additional control parameters. It introduces the concept of “environment”, automatically generating and applying configuration files for each named setting during manifest rendering. Tako supports multiple conversion formats, presently offering native Kubernetes manifests, with plans to include formats like Kustomize and OAM. By integrating with external tools, tracking source files, and ensuring alignment with Kubernetes API changes, Tako streamlines local development on Kubernetes, reducing repetitive tasks and promoting best practices.

Star us on GitHub Get started

Versatile

Intuitive

Efficient

Versatile

Tako supports multiple conversion formats and is designed with a broad vision to incorporate further output formats like Kustomize, OAM, and more. This versatility makes it an adaptable tool that can meet a variety of Kubernetes development needs.

Intuitive

With its easy-to-follow configuration convention, automated application of environment-specific configuration files, and automatic presetting of sensible defaults, Tako simplifies the Kubernetes development process, making it more accessible and efficient.

Efficient

Tako’s integration with external tools, tracking and analysis of source compose files, and minimized repetition in the development workflow contribute to a streamlined and efficient local development lifecycle on Kubernetes.

Versatile

Intuitive

Efficient

Run the following command within your project directory:

This identifies the default docker-compose.yaml and (if present) docker-compose.override.yaml files in your project directory. They will be used as the source of truth for your application deployment in Kubernetes.

Also, it creates an implicit sandbox dev environment and its Compose override file.

Here’s another example. It uses an alternate docker-compose file with stage & prod environments:

It makes use of:

-f flag, to specify an alternate filename
-e flags, to specify different deployment environments

Creating the files below in your project directory:

Here’s what happened. Tako has:

Inferred the configuration details already present in your compose Kubernetes deployment sources.
Assigned sensible defaults for any config it couldn’t infer.
Created Compose overrides files for the dev, prod and stage environments.

That’s it, your Tako project is now ready!

From now on it can:

Detect edits in your source compose file.
Apply any related config changes to your compose environment overrides.
Generate deployment manifests.

You can now customise your deployment targets by altering values in the relevant Compose environment override file.