A BOSH release for Kubernetes. Formerly named kubo.
- Slack: #cfcr on https://slack.cloudfoundry.org
- Pivotal Tracker: https://www.pivotaltracker.com/n/projects/2093412
We are no longer supporting the following documentation for deploying BOSH and CFCR
The deploy_bosh
and deploy_k8s
scripts in the kubo-deployment repository are now deprecated.
- A BOSH Director configured with UAA, Credhub, and BOSH DNS.
- kubo-release
- kubo-deployment
- Cloud Config with
vm_typesnamedminimal,small, andsmall-highmem(See cf-deployment for reference)networknameddefault- There are three availability zones
azs, and they are namedz1,z2,z3 - note: the cloud-config properties can be customized by applying ops-files. See
manifests/ops-filesfor some examples
- Upload the appropriate stemcell to the director. You can determine the version and type of the stemcell with
bosh int ~/workspace/kubo-deployment/manifests/cfcr.yml --path /stemcells - Copy the link to the latest version of kubo-release tarball and upload it to the director
- Deploy
If you have a BOSH Lite environment, run
cd kubo-deployment bosh deploy -d cfcr manifests/cfcr.yml \ -o manifests/ops-files/misc/single-master.ymlcd kubo-deployment bosh deploy -d cfcr manifests/cfcr.yml \ -o manifests/ops-files/misc/single-master.yml \ -o manifests/ops-files/iaas/virtualbox/bosh-lite.yml - Add kubernetes system components
bosh -d cfcr run-errand apply-specs - Run the following to confirm the cluster is operational
bosh -d cfcr run-errand smoke-tests
- Login to the Credhub Server that stores the cluster's credentials:
credhub login - Find the IP address of one master node by running
bosh -d cfcr vms - Configure the
kubeconfigfor yourkubectlclient:cd kubo-deployment ./bin/set_kubeconfig <DIRECTOR_NAME>/cfcr https://<master_node_IP_address>:8443