v2.11.17
Changelog
Added
--no-short-circuit-wait
flag (defaults to false) to many app commands which allows commands to terminate without waiting only if they are operating on an app that is in the stopped state.Changed
increased concurrency of app and route reconcilers to improve performance.
Risks and mitigations
The --no-short-circuit-wait
flag is defaulted on and is expected to improve the performance of common kf workflows by automatically skipping unnecessary waiting. If you notice problems, test your commands with --no-short-circuit-wait=false
to disable the new behavior.
Increased concurrency of app and route reconcilers is expected to improve performance at the cost of higher load on the Kubernetes control plane as well as Kf's processes. If experiencing performance problems allocate more resources to Kubernetes.
Compatibility
- It's safe to use this version of the Kf CLI with the previous server version; it should start decreasing wait times.
- It's safe to use the previous version of the Kf CLI with this server version.
- It's safe to roll back this server version to the previous version of Kf.
Known issues
- Some commands may show an incorrect text string describing why they're not waiting for the resource to be reconciled on the Kf server e.g. showing "Creating autoscaling rule for App "foo" in Space "bar" asynchronously because app is stopped" when the app is started, but instead the autoscaling isn't enabled yet.
Dependencies
Dependency | Version |
---|---|
Tekton | v0.32.1 |
ASM | 1.15.3-asm.6+config2 |
Config Connector | 1.66.0 |