This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
persisting k8s plugin state between evaluations #540
Merged
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
Persisting k8s plugin state by embedding it in the overall state stored for all k8s plugins. The exporting the
PluginStateReader
function through thePluginContext
so that k8s plugin writers can retrieve plugin state the same way they do in other plugins, just that persistend (ie.PluginStateWriter
) is performed underneath.Type
Are all requirements met?
Complete description
^^^
Tracking Issue
fixes flyteorg/flyte#3440
Follow-up issue
NA