KubeCF Release v2.5.0

⚠️ WARNING: Do not deploy this version and go directly to 2.5.8, due to a secret rotation bug that will not support successful upgrades. The team is working hard to fix this, and a patch version is imminent.

The new release reflects the intensive work around Eirini and the enabling of C2C networking on KubeCF....plus several bug fixes and work behind the scenes.

Enhancement(s)

• Enable C2C networking #776
• Bump to Eirini 1.8.0 #843
• Bump to cf-deployment 13.17 #1221
• Allow tolerations to be set for the instance group pods #607
• Always use a hostpath storage class for diego cells #1241
• Include Eirini, EiriniX and Bits templates in KubeCF #1179

Bug Fix(es)

• Make Eirini apps work with our DNS #284
• Eirini is unable to pull docker apps from public registry #1304
• cf logs does not display application error #923
• Stratos console only showing 1 of 2 diego cells #407
• After helm upgrade to scale diego cell count from 3 to 4, 2 out of 3 diego-cell pods gets restarted #981
• Allow the rep to configure kernel parameters #1181
• grootfs cleanup does not work correctly #1224
• database-0 pod never getting ready #1128
• high_availability property doesn't make HA database pods #1333
• Diego cell info does not appear in Stratos #1198
• /var/vcap/data on diego-cell needs to be a separate volume with quota support #441

Known issues

• Minibroker 1.0 doesn't work on KubeCF current version due to custom apps-dns support. If you are using Minibroker 1.0, be sure to upgrade to Minibroker 1.1 before upgrading to KubeCF 2.5. More instructions on the Minibroker 1.1 release here.
• There's an issue reported where pods are being deleted but not for everyone's cluster, so the team is trying to reproduce it so it can be fixed as soon as possible. If you came across this issue please report immediately on Slack #kubecf-dev channel.

Dependencies

Name	Version	Description
cf-operator	6.1.0+0.g5451299e	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

KubeCF

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

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

KubeCF Release v2.4.0

This new version is coming with multi-stack work, loads of bumps, the buildpack updates and other enhancements and bugs fixed.

The team will continue focus on Eirini stability work, container-to-container support, fixing bugs reported by the community and other stories listed in our board.

Enhancement(s)

• implement configurable multi-stack support #1202
• detailed information for the most used fields in values.yaml #736

Bug Fix(es)

• auto creation of ingress should not include bare domain #1205
• autoscaler goes into a CLBO if we run helm upgrade to enable it #973
• support configurable cluster domain #872

Maintenance

• better startup dependency declarations #727
• bump cflinuxfs3 release to 0.203.0 #1235
• bump PXC to 5.7.30-33 #1238
• bump cf-deployment to 13.9.0, cats to 6.0.0 #1172

Dependencies

Name	Version	Description
cf-operator	5.2.0+0. g22cafc90	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

KubeCF

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

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

KubeCF Release v2.2.3

Bug Fix(es)

• fix: log rotation by bumping quarks operator to 4.5.13 #1209
• fix: allow affinity to be set for the instance group pods #606
• fix: add podAntiAffinity for the same STS pods against a node #254

Dependencies

Name	Version	Description
cf-operator	4.5.13+.gd4738712	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_release.tgz

KubeCF Release v2.3.0

WARNING: cf-operator namespace property name has changed on this version.

Enhancement(s)

• eirini-persi-broker should use default storage class when unspecified #819
• Make Eirini work with external blobstores #384

Bug Fix(es)

• ssh-proxy service was not exposed externally which made the cf ssh fail #1026
• stop using secrets in a ConfigMap #793
• bits chart resource requirements should be optional #861
• cfdot job does not work on kubecf #738
• eirini pod failed to list nodes #559
• CSR for bits should be namespaced #877
• eirini doesn't have a fully configurable registry address (including port) #794

Maintenance

• NOTES.txt added so we can access useful information from the helm command #855
• Internet-less CATS are passing #995

Dependencies

Name	Version	Description
cf-operator	5.0.0+0.gd7ac12bc	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

KubeCF

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

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

KubeCF Release v2.2.2

WARNING: only sequential upgrades are supported.

Enhancement(s)

• Add suse_default_stack feature flag #945

Bug Fix(es)

• fix: tcp-router is only enabled when routing-api is enabled.
• fix: move sample values into kubecf chart #916

Dependencies

Name	Version	Description
cf-operator	4.5.6+.gffc6f942	Processes BOSH deployments. Maps them to kube objects

KubeCF Release v2.2.1

WARNING: only sequential upgrades are supported.

Enhancement(s)

• New sample-values.yaml with only REQUIRED values uncommented #857

Bug Fix(es)

• Using correct prefix for encryption key labels #853 (please read Upgrade Instructions below before upgrading from v2.2.0)
• Bumped nginx proxy-body-size to 64M #833
• Autoscaler now uses internal URL for cloud controller #870
• Ensure patches are applied when pods or containers unexpectedly go away #873

Dependencies

Name	Version	Description
cf-operator	4.5.6+.gffc6f942	Processes BOSH deployments. Maps them to kube objects

Upgrading from KubeCF v2.2.0

Warning: KubeCF will no longer prefix encryption key labels with the ccdb_key_label_. This has no impact on new installations, but upgrades from v2.2.0 will require matching references to the encryption key labels (pre and post-upgrade).

For example, the default values for ccdb.encryption.rotation in v2.2.0 are:

ccdb:
  encryption:
    rotation:
      # Key labels must be <= 240 characters long. Each label will be prepended with the
      # "ccdb_key_label_" value.
      key_labels:
      - encryption_key_0
      current_key_label: encryption_key_0

The key_label was transformed to ccdb_key_label_encryption_key_0 during installation, so upgrades from v2.2.0 will require the following settings in your helm values:

ccdb:
  encryption:
    rotation:
      key_labels:
      - ccdb_key_label_encryption_key_0
      current_key_label: ccdb_key_label_encryption_key_0

These matching values for key_labels and current_key_label must be kept for all subsequent upgrades. Without them, the cloud controller will not be able to decrypt its database after upgrade.

If you have manually rotated the encryption keys in KubeCF, use the key_labels value that is currently set for current_key_label during the upgrade and for subsequent upgrades.

KubeCF Release v2.2.0

WARNING: only sequential upgrades are supported.

Enhancement(s)

• Implement credentials and variables settings in values.yaml #814
• eirini extensions as a subchart #800

Bug Fix(es)

• DB seeder tries to seed the routing-api database even when routing-api is disabled #739
• database should use utf8 charset instead of latin1 #549
• eirini not showing app metrics #826
• EiriniX Persi init container requires root #782

Dependencies

Name	Version	Description
cf-operator	4.5.6+.gffc6f942	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

Upgrading from KubeCF v2.1.0

WARNING the database charset is being migrated from latin1 to utf8 in this release.

cf-operator

helm upgrade cf-operator \
  --namespace cf-operator \
  --set "global.operator.watchNamespace=kubecf" \
  cf-operator.tgz

Wait for all the cf-operator and KubeCF pods to get ready.

KubeCF

helm upgrade kubecf \
  --namespace kubecf \
  --values values.yaml \
  kubecf.tgz

Wait for all the KubeCF pods to get ready, then run the following quarks-job to migrate the database charset from latin1 to utf8:

kubectl patch qjobs database-migrate-charset \
  --namespace kubecf \
  --type merge \
  --patch '{ "spec": { "trigger": { "strategy": "now" } } }'

KubeCF Release v2.1.0

Enhancement(s)

• Eirini native support #651
• Helm dependencies rules to support component native deployment #707
• Allow user to provide inline operations #732
• User-provided ClusterRole rules for Eirini #693
• Bump SUSE buildpacks #724
• Enable tasks CATS suite by default #723

Documentation

• Add release process for major and minor versions #725

Dependencies

Name	Version	Description
cf-operator	4.4.4+0.gb984473a	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

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)

• Remove --- from routing-api ops-file. #658
• Doppler out of memory when scaled. #241

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

KubeCF Release v1.0.1

Bug fixes

• Fixes the permissions issue in autoscaler db when the pod restarts. #467
• Moved pxc image to cfcontainerization organization, like all the other images. #479
• The database-seeder job pod was not being deleted after KubeCF helm installation was removed with success. #493
• Security group setups. #485

Maintenance

• cf-operator bumped to version 3.3.0+0.gf32b521e.

Dependencies

Name	Version	Description
cf-operator	3.3.0+0.gf32b521e	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