Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
clusterIdentifier
configuration can now be used to manually control the replacement behavior of a provider resource. (AddclusterIdentifier
configuration to control provider lifecycle #3068)Pod errors now include the pod's last termination state, as well as the pod's termination message if available. (Upgrade cloud-ready-checks #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. (Define Supported Languages for Overlay Resources #3107)
Fixed
CustomResource
overlays. (Add java as supported language for CustomResource overlays #3120)affected resource. (Fix pod info reporting #3128)
PersistentVolumeClaims
with a bind mode ofWaitForFirstConsumer
will nolonger hang indefinitely. (Fix endless PVC await #3130)