The bosh-deployment repository serves as a reference collection of BOSH manifests for deploying and configuring BOSH Directors across multiple infrastructure platforms. Maintained by the Cloud Foundry project, this repository provides developer-friendly starting configurations that are actively consumed from the master branch, with development work conducted against the develop branch before automatic promotion following test validation.
The repository functions as a comprehensive deployment toolkit supporting numerous cloud platforms and infrastructure providers. Users can deploy BOSH Directors on local machines using BOSH Lite, or across major cloud providers including Alibaba Cloud, AWS, Azure, OpenStack, vSphere, vCloud, SoftLayer, and Google Compute Platform. The manifests accommodate various access patterns, allowing operators to secure their Directors through VPN connections, jumpbox configurations, or public IP exposure, with detailed documentation provided for each deployment scenario.
The core operational structure relies on a modular ops files system that allows users to compose deployments by combining base configurations with platform-specific and feature-specific overlays. The base bosh.yml manifest works in conjunction with CPI-specific configurations for each supported platform, cloud-config files for infrastructure abstraction, and optional feature files for capabilities like UAA integration, CredHub deployment, syslog forwarding, and DNS functionality. Additional ops files enable BOSH Lite configuration, jumpbox user setup, HTTP proxy configuration, and NTP server customization. The repository also includes runtime configuration files that apply IaaS-agnostic settings across all deployments, such as DNS resolution, BOSH Process Manager installation, and syslog forwarding agents.
The repository's contributor network overlaps with other significant Cloud Foundry projects including the main bosh repository, Concourse CI, and extends to external projects like Ollama, suggesting its role as a foundational component in broader deployment ecosystems.
The repository addresses specific technical requirements and compatibility concerns for operators. A notable notice addresses BOSH DNS versions prior to 1.28, which require certificate regeneration due to Go 1.15 TLS requirements mandating SAN fields in addition to CN fields. The manifests default to Noble stemcells but provide Jammy stemcell alternatives through dedicated ops files. An automated update process keeps the repository current, with a CI pipeline automatically updating bosh-deployment on the develop branch whenever new releases of BOSH, UAA, CredHub, or various CPIs are published, followed by smoke testing to validate create-env functionality before promotion to master.
The repository emphasizes practical deployment patterns through its test suite, which demonstrates example usage of different ops file combinations. Runtime configuration examples show how operators can extend deployments with additional capabilities beyond the base Director installation, including DNS support for VM name resolution, process management, and monitoring agent installation. This modular approach enables operators to build customized Director deployments matching their specific infrastructure and operational requirements while maintaining consistency with Cloud Foundry best practices.
