KubeCF Release v2.0.0
WARNING: this major version introduces some changes required to consume Eirini as a native component
by forcing the usage of kubecf name throughout the deployment resources (pod, namespace, ...)
and so, upgrading from 1.x to 2.x will not be possible!
More technical details can be found on #477
Enhacement(s)
- Bump the cf-operator to 4.3.1.
- Add support for AWS S3 external blobstore. #608
- Add PVC for Diego cell ephemeral disks. #489 that fixes #441
- Move the log-cache jobs out of the doppler instance group. #619 that fixes #241
Bugfix(es)
Maintenance
- Bump of several buildpacks.
- Bump cf-deployment 12.36. #638
- List of all images used by KubeCF. #571
- Add template mechanism to concourse pipeline so any contributor can deploy on their own resources. #538
- Add CI pool mechanism that improves the utilization of the resources available. #565
Dependencies
Name | Version | Description |
---|---|---|
cf-operator | 4.3.1+0.g157049a1 | Processes BOSH deployments. Maps them to kube objects |
Quick Fresh Installation
These are the basic guidelines to deploy KubeCF in a development environment. For more detailed information check here.
Before starting the deployment phase, make sure that the values.yaml file contains all the needed properties with valid values. For more information about the available properties check here.
Download the release bundle artifact extract the content to a local folder.
cf-operator
helm install cf-operator \
--namespace cf-operator \
--set "global.operator.watchNamespace=kubecf" \
cf-operator.tgz
KubeCF
Install KubeCF after setting the needed properties in your values.yaml
.
helm install kubecf \
--namespace kubecf \
--values values.yaml \
kubecf.tgz