|Smoke tests on Diego|
|Smoke tests on Eirini|
|Acceptance Tests on Diego|
|Acceptance Tests on Eirini|
The Community documentation website is available here.
Contributing to KubeCF development
See the Guide to Contribution.
To work with
kubecf, a variety of supporting tools are required.
|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
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,
At the time of this writing these were:
|Helm||2.16.1||2.(latest_minor) and 3 should work|
Note however: As
kubecf is updated these versions may change
from commit to commit. The table above is therefore
Always check the contents of
def.bzl for the authoritative
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:
|k9s||Curses-based UI over kubectl||https://github.com/derailed/k9s|
|stern||Multi-pod log tailing||https://github.com/wercker/stern|
Last, but not least, more documentation on how to work with
kubecf is found in the Guide to Contribution.
|S3 Bucket with helm charts*||https://kubecf.s3.amazonaws.com/index.html|
|Cloud Foundry Operator||https://github.com/cloudfoundry-incubator/cf-operator/|
|CF Operator Charts||https://cf-operators.s3.amazonaws.com/helm-charts/index.html|
* The bundle file includes the operator chart