cloudfoundry/kind-deployment

Deploying Cloud Foundry on a local kind cluster

Hosted by Cloud Foundry Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

cloudfoundry/kind-deployment has 30+ stars and 10+ forks on GitHub, is written in Go Template, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 46 minutes ago
Added to GitGenius on October 15th, 2026
Created on January 27th, 2026
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 31 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 24.4 days
90th percentile: 185.8 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 85 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 2

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

kind-deployment is a tool for deploying Cloud Foundry on a local Kubernetes cluster using kind.

The tool addresses the need for developers to run a full Cloud Foundry environment locally without expensive infrastructure. It uses kind, a lightweight Kubernetes distribution, combined with Helm charts to provision Cloud Foundry components. The deployment process is orchestrated through make commands and docker-compose, allowing rapid setup and teardown of complete environments suitable for prototyping and testing.

Developers should choose this tool when they need a local Cloud Foundry instance for development and testing workflows. It works well for teams evaluating Cloud Foundry, building applications that will run on it, or testing platform extensions. The tool supports both Docker and Podman as container runtimes. Optional components like bosh-dns, credhub, loggregator, and routing services can be excluded via environment variables to reduce resource consumption, and custom Helm values can be supplied through additional configuration files to tailor deployments to specific needs. PostgreSQL configuration is also customizable through values files.

The project provides a GitHub Action that automates Cloud Foundry provisioning within CI/CD workflows, exporting generated credentials for use in subsequent workflow steps. The tool requires Docker or Podman, docker-compose or podman-compose, and make to be installed locally. On Windows, make must be installed separately. The README emphasizes that Podman users must configure it as a Docker alias for the project to function correctly.

Development activity shows consistent maintenance with regular updates to dependencies and configuration. The project receives ongoing refinement of its deployment automation and documentation. Contributors actively address issues and incorporate improvements to the setup process and Helm chart integrations.