This repository has been archived by the owner on Feb 14, 2023. It is now read-only.
v0.5.0
Notable changes since the last v0.4.0 release
🎉 🎉 We are excited to have SAP Cloud Platform Cloud Foundry team [1] contribute a complete end to end feature - external database support - to cf-for-k8s. The feature will allow Platform engineers to use cf-for-k8s with a highly available external database service.
The cf-for-k8s team is thankful for the contribution from SAP and are looking forward to future contributions of similar impactful features.
[1] SAP Team: @c0d1ngm0nk3y , @Haegi, @jkbschmid, @kramerul, @phil9909, @modulo11, @loewenstein, @lucaschimweg
New Features / Bug fixes
- 🌟 Platform engineers can now configure an external hosted Postgres database service. The platform checks for the presence of an external DB configuration. If one is available, it drops the internal Postgres DB else install the DB on the cluster alongside CF. See how to configure an external DB @ docs/platform_operators/external-databases.md
- App developers can now see application crash events in the output of
cf events APP_NAME. - Platform engineers can expect sensitive information such as UAA client passwords, UAA admin passwords in UAA are stored and consumed via native Kubernetes Secrets.
- Resolved an issue where apps under the system domain did not get SSL (Issue #238).
- Resolved the missing CAPI's database encryption key secret [1].
Configuration changes
This section highlights changes made to the config/values.yml configuration that may impact your upgrades [1]
| Change type | Changes | Highlights |
|---|---|---|
| REMOVED | cf_db.enabled |
Explicit flag is not needed. The platform checks for the presence of an external DB configuration. If one is available, it drops the internal Postgres DB else install the DB on the cluster alongside CF |
| RENAMED | app.repository => app. repository_prefix |
See #249 |
| RENAMED | kpack_watcher_client_secret => cf_api_controllers_client_secret kpack_watcher_secret_name => cf_api_controllers_secret_name |
CAPI repository re-organization |
| NEW, OPTIONAL | database_encryption_key_secret_name, encryption_key |
Add missing CAPI's database encryption key secret |
| NEW, OPTIONAL | kpack_watcher_client_secret, cc_username_lookup_client_secret |
Use separate UAA client secret names |
| NEW, OPTIONAL | ca_cert |
Enables TLS cert for external database |
| NEW, OPTIONAL | cf_blobstore_key_secret_name, database_password_secret_name, kpack_watcher_secret_name, cloud_controller_username_lookup_secret_name, encryption_key_passphrase_secret_name |
Create actual Secrets resources and provide configuration for the secret names |
[1] cf-for-k8s does NOT support upgrades for alpha releases. Our goal is to move towards stable upgrades and highlighting changes to the configuration is a step towards that direction.
Release Updates
We are only tracking published releases
| Release | Old Version | New Version |
|---|---|---|
| Eirini | 1.6.0 |
1.7.0 |
| UAA | v74.21.0 |
v74.23.0 |
| metric-proxy | 0.2.0 |
Integration updates
- Built a long-running environment to validate and measure cf-for-k8s upgradability and availability over time.
- Use PRs as a single point of entry to validate all contributions to cf-for-k8s.
What we are working on next
- Define a clear versioning contract between the Platform engineers, cf-for-k8s, and contributing projects. Our goal is to submit the proposal to the community in a week or so after this release.
- Incorporate CATS tests into cf-for-k8s workflows.
- Collaborate with Credhub team to integrate Quarks server-side password generation. With Quarks, Platform engineers will no longer be required to provide passwords (or run bosh-cli based script to generate passwords) and rely on Quarks to generate them in the K8s cluster. It is similar to the functionality available today in cf-deployment with Credhub integration.
- Identify and document app structural differences required by Paketo Buildpacks to detect and build the image.
- Move roadmap to github projects and use milestones to plan future releases. Our hope is that github projects/milestones will create transparency with the community and make it easier for contributors to participate and contribute to cf-for-k8s.
Have a question, reach out to us
Our slack channels
Interested in contributing?
- The easiest way to get involved is to start attending the SIG meetings, join the #cf-for-k8s slack channel, and subscribe to the [email protected] mailing list.
- You can also start by improving the docs. Install cf-for-k8s using the deploy docs and if you notice issues or discrepancies in the docs, you can submit a PR.