#540 persisting k8s plugin state between evaluations Pull request opened by hamersaw TL;DR Persisting k8s plugin state by embedding it in the overall state stored for all k8s plugins. The exporting the

PluginStateReader

function through the

PluginContext

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 ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☑︎ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue fixes flyteorg/flyte#3440 Follow-up issue NA flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks