Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
bioinformatics-computational-biology
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
shameless-promotion
linkedin-flyte
random
deployment
hacktoberfest-2023
flyte-github
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#ask-the-community
Title
# ask-the-community
y
Yee
11/09/2022, 11:08 PM
@Louis DiNatale
you might also want to check out the k8s events
they should have messages around eviction and such.
also someone else internally that saw this recently said to check the autoscaler logs actually, not the scheduler.
haytham pointed us to this annotation
https://github.com/flyteorg/flyteplugins/blob/d95b86b4ba9e6fcab18b3ea834047c4248cf314a/go/tasks/pluginmachinery/flytek8s/config/config.go#L33
but it should already be set unless you’re overriding it?
l
Louis DiNatale
11/10/2022, 12:05 AM
Ya I believe we have the annotation right. The autoscaler logs make perfect sense, thank you.
Post