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" } } }'