03For developers and teams

BKE

Bridge Kubernetes Engineering

From your own GitHub code to running services.

BKE, Bridge Kubernetes Engineering, is developer infrastructure that takes code you own on GitHub and turns it into running services, with less operational work in between.

In development
BKE conceptA sequence from a code repository, through a build, to a group of running services.
  1. Your code on GitHub
  2. Built and deployed
  3. Running services
Illustrative concept

What it’s for

Deploying and running software should not need a platform team. BKE grew out of the founder’s own need for hosting that is manageable and keeps costs down.

It aims to make deployment and day-to-day operations simpler for developers and small teams.

Try the concept

Merge a small change and follow it from GitHub to a running app.

A sample repository and a simulated pipeline, running only in your browser. Nothing is merged, built or deployed, and the app shown is a sample.

Sample repository harbor-team/harbor-web

Refresh the home page for 1.4.0 #42

Pull request · 1 file changed

src/release.ts
export const release = {  version: '1.3.0',  version: '1.4.0',  headline: 'Welcome to Harbor',  headline: 'Harbor, refreshed',  accent: 'slate',  accent: 'gold',};

Ready to merge

Sample app previewSimulated
harbor.example

Harbor

Welcome to Harbor

The community site of a fictional token project.

Version ⁦1.3.0⁩

  1. 1Waiting

    Repository

    Your code, on GitHub, owned by you.

    • 2Waiting

      Build

      The code is built and packaged into a container.

      • 3Waiting

        Deploy

        The container is scheduled onto a Kubernetes cluster.

        • 4Waiting

          Running service

          Your service is up, with operations kept simple.

          Where it runs

          3 of 3 ready

          Routeharbor.example
          Serviceharbor-web
          Node node-a
          • 1.3.0Ready
          • 1.3.0Ready
          Node node-b
          • 1.3.0Ready

          The service sends traffic only to pods that are ready, so the old version keeps serving until the new one can take over.

          The merge on GitHub starts the build. BKE builds and tests the code and packages it as a container image. Kubernetes then runs that image, and replaces old pods only once new ones are ready.

          Where it stands

          In development

          BKE is in development.