cloudfoundry/cf-deployment

The canonical open source deployment manifest for Cloud Foundry

Hosted by Cloud Foundry Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

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

Summary Information

Updated 24 minutes ago
Added to GitGenius on October 12th, 2026
Created on August 13th, 2015
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 315
Total Stargazers: 317 (+0)
Total Subscribers: 100 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.3 days
Mean response time: 26.6 days
90th percentile: 149.1 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 518 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

cf-deployment is a BOSH deployment manifest that provides the canonical open source configuration for deploying Cloud Foundry Application Runtime.

The tool addresses the challenge of deploying Cloud Foundry consistently and securely by providing a single, authoritative manifest that operators can use with BOSH. Rather than requiring operators to construct deployment configurations from scratch, cf-deployment offers a pre-built manifest that encodes best practices and security-first defaults. It relies on individual component releases coordinated through BOSH, leveraging newer BOSH director features to manage the complexity of a multi-component platform deployment.

The manifest is designed for operators deploying Cloud Foundry who want a secure, readable baseline configuration. It prioritizes human readability by including only necessary configuration, enables TLS on all supporting jobs, uses CredHub for credential generation rather than storing defaults, and deploys across two availability zones for redundancy. The tool assumes external load balancing and includes Diego as the default container scheduler. It handles platform persistence through singleton database instances and blob storage, with guidance provided in the deployment documentation. Operators in development or test environments can skip TLS validation for convenience, while production deployments can enforce strict validation through provided operations files.

The project maintains active development with regular updates to support evolving Cloud Foundry components and BOSH capabilities. The codebase includes comprehensive deployment guidance separated into dedicated documentation, reflecting ongoing refinement of the deployment process. The project has established semantic versioning practices documented in detail, indicating mature release management. Contributions are welcomed through a defined process, and the project includes continuous integration infrastructure to validate deployments.