cf-operator enables the deployment of BOSH Releases, especially Cloud Foundry, to Kubernetes.
It's implemented as a k8s operator, an active controller component which acts upon custom k8s resources.
The cf-operator can be installed via helm. Make sure you have a running Kubernetes cluster and that tiller is reachable.
Use this if you've never installed the operator before
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.3.0%2B1.g551e559.tgz
Use this if the custom resources have already been created by a previous CF Operator installation
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.3.0%2B1.g551e559.tgz --set "customResources.enableInstallation=false"
For more information about the cf-operator helm chart and how to configure it, please refer to deploy/helm/cf-operator/README.md
With a running cf-operator pod, you can try one of the files (see docs/examples/bosh-deployment/boshdeployment-with-custom-variable.yaml ), as follows:
kubectl -n cf-operator-test create -f docs/examples/bosh-deployment/boshdeployment-with-custom-variable.yaml
The above will spam two pods in your cf-operator-test namespace, running the BOSH nats release.
You can access the cf-operator logs by following the operator pod's output:
kubectl logs -f -n cf-operator cf-operator
Or look at the k8s event log:
kubectl get events -n cf-operator --watch
For more information about the operator development, see docs/development.md
For more information about testing, see docs/testing.md
For more information about building the operator from source, see docs/building.md
Content type
Image
Digest
Size
100.8 MB
Last updated
about 7 years ago
docker pull rkoster/cf-operator