v4.16.0
Added
-
clusterIdentifier
configuration can now be used to manually control the replacement behavior of a provider resource. (#3068) -
Pod errors now include the pod's last termination state, as well as the pod's termination message if available. (#3091)
The pod's termination message can be helpful in
CrashLoopBackOff
situations but will only be reported if it was correctly configured.By default, the pod's termination message is read from
/dev/termination-log
. This location can be configured withterminationMessagePath
.Use
terminationMessagePolicy: FallbackToLogsOnError
to use the pod's logs as its termination message. -
Documentation is now generated for all languages supported by overlay types. (#3107)
Fixed
- Updated logic to accurately detect if a resource is a Patch variant. (#3102)
- Added Java as a supported language for
CustomResource
overlays. (#3120) - Status messages reported during updates are now more accurately scoped to the affected resource. (#3128)
PersistentVolumeClaims
with a bind mode ofWaitForFirstConsumer
will no longer hang indefinitely. (#3130)- [java] Fixed an issue where child resources could not be registered by Chart v4. (#3119)