KubeCF Release v2.7.1

Enhancement(s)

• Added support for a generic fog provider to allow usage of an external blobstore. #1531
• Implemented ability to pull kubecf or other images from a private registry requiring authentication. #1421
• Removed the cc-deployment-updater to fix upgrade issues. #1637
• Removed sample_values.yaml since values are now placed elsewhere. #1626

Bug Fix(es)

• cf-operator bump to 7.0.6 that contains several bug fixes
• Bumped garden-runc to 1.19.17. #1641
• Patched CAPI 1.98.0 to include YAML from CAPI 1.101.0 to address CVE-2020-5423. #1639
• PXC now picks up new database root password. #1355
• Credhub now prevented from consuming the postgres bosh-link from auto-scaler postgres, ensuring that pods don't unnecessarily rotate. #1651
• NOTES.txt now adaptive to correctly report HA changes in underlying CF manifest to show diego cell count accurately. #1593
• Check for HA as part of estimating max app count. #1591
• Moved tcp-router healthcheck port to avoid clash on port 80. #1526
• Updated ingress.yaml to allow the pod selector to match the scheduler pod, allowing ssh-proxy-public service to work with load balancers. #1517

Dependencies

Name	Version	Description
cf-operator	7.0.6+0.g2d07254	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.singleNamespace.name=kubecf" \
  cf-operator.tgz \
 --wait

KubeCF

Install KubeCF after setting the needed properties in your values.yaml.

helm install kubecf \
  --namespace kubecf \
  --values values.yaml \
  kubecf_release.tgz