You're developing services on Kubernetes. Are you frustrated by:

  • a (frequently broken) shared dev environment because everyone is using it to test code?
  • Waiting for your CD pipeline to finish building and deploying so you can just run one test?
  • Depending on someone else to write your Kubernetes manifest (or trying to figure out how to write a bunch of YAML yourself)?
Introducing Forge. With Forge, you:

  • Define your application in a service.yaml file. This file specifies all of your application dependencies, as well as any runtime configuration for your services.
  • Run forge deploy which will create and run all your services in Kubernetes.
(If you've used Docker Compose, think of Forge as Kubernetes-native Docker Compose.)

  • Develop/test in your own isolated environment Deploy your service(s) the same way, every time, into minikube or any other Kubernetes cluster.
  • Kubernetes-native Forge uses standard Kubernetes manifest files, so you can use any Kubernetes feature. (Or, use optional Jinja2 templating.)
  • Works with 1 service, or 1000 services The Forge model supports organizations with a handful of dependent services, or 1000s of services.
  • Build, deploy, and test your service without committing Stop waiting on your CD pipeline to test a small change. Just do this all locally.
  • Zero infrastructure required Forge runs locally, anywhere. It integrates with your CI system, or just runs on your laptop.

How it works:
Forge builds services based on Docker and Kubernetes. With Forge, a user specifies the deployment configuration for a service in a YAML file. Forge uses this metadata along with the source code to build a Docker image and the necessary Kubernetes deployment data to create a runnable service. For more information, see how Forge works.

Get started in a few minutes:
  1. Install Forge.
  2. forge setup
  3. git clone
  4. forge deploy

Forge is sponsored by Project Blackbird, helping you deploy microservices on Kubernetes in AWS