This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
Plugin changes for plumbing k8s events into TaskExecutionEvent #406
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.
TL;DR
State management and config changes required for plumbing k8s events into
TaskExecutionEvent
as part of flyteorg/flyte#3825Type
Are all requirements met?
Complete description
This change
TaskInfo.AdditionalReasons
field so that propeller can append k8s event information when handling a k8s phase update.SendObjectEvents
option to K8sPluginConfig so this feature can be opted intoTracking Issue
flyteorg/flyte#3825
Follow-up issue
N/A