Hi, I just updated flyte-core from 1.6.2 to 1.7.0 ...
# flyte-deployment
f
Hi, I just updated flyte-core from 1.6.2 to 1.7.0 via helm. But flyteagent fails to start because the flyteagent serviceaccount was not created.
s
@Kevin Su
k
are you trying to deploy it on eks?
cc @Prafulla Mahindrakar
p
Hey @Kevin Su, it seems we are missing the serviceaccount in you agent charts PR https://github.com/flyteorg/flyte/pull/3454/files#diff-e3d30827769df90d84af9cb7138149a276c47693ef3440cc0e59165622b6b642 This references the usage of the sa https://github.com/flyteorg/flyte/pull/3454/files#diff-e3d30827769df90d84af9cb7138149a276c47693ef3440cc0e59165622b6b642R40 But couldn’t find kind: ServiceAccount object .
f
@Kevin Su no, on prem k3s cluster
k
@Felix Ruess we just added service account to the helm chart. https://github.com/flyteorg/flyte/pull/3788
btw, we’re adding more agents such as sensor, sagemaker to flyte. What other agents would you like to see in Flyte?
f
Thanks, I don't need the agent right now (just noticed because it is enabled by default), but I could test if the service account creation works. Just not sure how to do that as long as the helm chart is not released.
a
Hey! It happens to me as well, can’t find any fix for this bug - (GKE cluster)
f
If you don't need flytagent, you can disable it in your values.yaml for now
a
yeah thanks. I did it, but still..
f
yeah... looks like it is fixed in flyte, but not released into the helm repo
105 Views