Bernard Greyling
07/10/2020, 8:47 AMcpu: 100m & memory: 128Mi
is mentioned but not explained. What is the reasoning behind this limit?
2. We've successfully setup/authenticated a k8s runner and scheduled both s3 and docker runs.
After a custom image pull error on k8s the k8s-prefect agent seems to be in a feedback loop announcing that it can see flows : Found 2 flow run(s) to submit for execution.
But not executing them. Note - I did manually terminate the k8s job via kubectl. Not sure if this messed up the prefect-cloud state
EDIT - Before this feedback loop state, we managed to run both s3 and docker runs with the vanilla examplesJenny
07/10/2020, 1:07 PMnicholas
07/10/2020, 1:20 PMBernard Greyling
07/10/2020, 1:28 PMflow.environment = LocalEnvironment(
metadata={
"image": "registry_url/org/repo:tag"
},
labels=['s3-flow-storage']
)
@Jenny The feedback loop persisted until I deleted the Project with all flows from cloud and creating a new one.
This is fine for now as we are still getting to know the ecosystem. But seems problematic for mission critical deployments.
Is there some internal state management with prefect cloud that might help understand the loop?nicholas
07/10/2020, 1:32 PMBernard Greyling
07/10/2020, 1:33 PMBernard Greyling
07/10/2020, 2:45 PMnicholas
07/10/2020, 2:45 PM