Skip to content
Cloud Foundry on Kubernetes
Shell Starlark Ruby Smarty Python
Branch: master
Clone or download
Latest commit 63cbfb9 Feb 18, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.concourse Bump catapult version in post_publish pipeline Feb 3, 2020
.github Add line break Jan 31, 2020
.gitlab fix: reverted target names back to apply Feb 7, 2020
bosh/releases adding patch and pre-start jobs for all buildpacks Jan 16, 2020
deploy Merge branch 'master' into f0rmiga/helm-3 Feb 18, 2020
dev fix: reverted target names back to apply Feb 7, 2020
doc fix: reverted target names back to apply Feb 7, 2020
rules fix: use Process.{spawn,wait} as per review Feb 7, 2020
testing Merge remote-tracking branch 'origin/master' into aduffeck/cf-deploym… Dec 5, 2019
.adr-dir Use Architecture Decision Records to make and persist decisions Nov 11, 2019
.bazelrc feat: workspace_status custom command Jan 23, 2020
.gitignore Split pipeline jobs and integrated with Starlark Dec 13, 2019
.gitlab-ci.yml fix: CI output files Jan 30, 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
CONTRIBUTING.md add code of conduct violations email and fix some typos Nov 4, 2019
LICENSE Intermediary commit for the move from scf to kubecf Oct 17, 2019
README.md Simplified language around helm. Jan 29, 2020
WORKSPACE feat: clean up build files Feb 4, 2020
code-of-conduct.md add code of conduct violations email and fix some typos Nov 4, 2019
def.bzl Merge branch 'master' into ak-remove-drone-ci Feb 18, 2020
workspace_status.rb feat: workspace_status custom command Jan 23, 2020

README.md

pipeline status

KubeCF

Cloud Foundry built for Kubernetes (formerly SUSE/scf v3 branch). It makes use of the Cloud Foundry Operator, which is incubating under Project Quarks.

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 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.

Useful Information

What Where
GitLab Pipeline https://gitlab.com/susecf/kubecf/pipelines
S3 Bucket with helm charts https://scf-v3.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
You can’t perform that action at this time.