Skip to content
Cloud Foundry on Kubernetes
Shell Starlark Ruby Smarty Python
Branch: master
Clone or download

Latest commit

viovanov Merge pull request #550 from cloudfoundry-incubator/bump_suse-nodejs-…

Bump suse-nodejs-buildpack release to
Latest commit b6ea055 Mar 30, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.concourse Bump Catapult version Mar 30, 2020
.github Add line break Jan 31, 2020
bosh/releases Replace cf-mysql with a pxc cluster using the pxc helm chart Feb 17, 2020
deploy Merge pull request #550 from cloudfoundry-incubator/bump_suse-nodejs-… Mar 30, 2020
dev feat: cf_operator: allow values overrides Mar 10, 2020
doc Merge branch 'master' into f0rmiga/router-certificates Mar 7, 2020
rules fix: add missing comment docs on the Bazel rules Mar 30, 2020
testing Consume KUBECF_INSTALL_NAME when triggering the rotation job Mar 17, 2020
.adr-dir Use Architecture Decision Records to make and persist decisions Nov 11, 2019
.bazelrc feat: workspace_status custom command Jan 23, 2020
.gitignore Move pipeline to yaml and use values from config.yaml [Fixes #442] Mar 20, 2020
.gitmodules Removed cf-operator as submodule Oct 17, 2019
BUILD.bazel Merge remote-tracking branch 'origin/master' into f0rmiga/automatic-v… Jan 30, 2020 add pull requests contributions Mar 25, 2020
LICENSE Update LICENSE Feb 27, 2020
NOTICE Create NOTICE Feb 27, 2020 Add link to badges project Mar 23, 2020
WORKSPACE feat: clean up build files Feb 4, 2020 Change contact details from SUSE to the CloudFoundry ones Feb 10, 2020
def.bzl feat: added bosh-cli binary dependency Mar 30, 2020
workspace_status.rb feat: workspace_status custom command Jan 23, 2020


Build step State
Linting lint
Building build
Smoke tests on Diego smoke-diego
Smoke tests on Eirini smoke-eirini
Acceptance Tests on Diego acceptance-diego
Acceptance Tests on Eirini acceptance-diego

Instructions on how to setup these badges


KubeCF is a distribution of Cloud Foundry Application Runtime (CFAR) for Kubernetes. It works with the cf-operator from Project Quarks to deploy and manage releases built from cf-deployment.


The Community documentation website is available here.

Contributing to KubeCF development

See the Guide to Contribution.

System requirements

To work with kubecf, a variety of supporting tools are required. These are:

Tool Notes
k8s The platform to run KubeCF.
minikube Provider for local k8s clusters.
kind Provider for local k8s clusters.
kubectl Client to talk to k8s clusters.
Helm Handling helm charts.
cf-operator Processes BOSH deployments. Maps them to kube objects.
cf-deployment The CF release at the core of kubecf.

As most of the developers use the Bazel build system coming with the kubecf repository, they implicitly use the versions for the tools set down in Bazel's main project configuration file, def.bzl.

At the time of this writing these were:

Tool Version Notes
Kubernetes 1.15.6
minikube 1.6.2
kind 0.6.0
kubectl 1.15.6
Helm 2.16.1 2.(latest_minor) and 3 should work
CF Operator 2.0.0-0.g0142d1e9
cf-deployment 12.18.0

Note however: As kubecf is updated these versions may change from commit to commit. The table above is therefore not authoritative.

Always check the contents of def.bzl for the authoritative answer.

Note further: Just because the build system provides targets to conveniently bring up a local k8s cluster using minikube or kind, this does not preclude the use of other k8s cluster providers, local or in the cloud.

Besides the required tools noted above, other tools used by developers are:

Tool Notes Location
k9s Curses-based UI over kubectl
stern Multi-pod log tailing

Last, but not least, more documentation on how to work with kubecf is found in the Guide to Contribution.

Useful Information

What Where
Concourse Pipeline
S3 Bucket with helm charts*
Cloud Foundry Operator
CF Operator Charts

* The bundle file includes the operator chart

You can’t perform that action at this time.