hi there, I'm registering workflows with `flyte-cl...
# announcements
a
hi there, I'm registering workflows with
flyte-cli register-files ... --kubernetes-service-account=<SERVICE_ACCOUNT>
but when I look at the running pods they all use default serviceAccount. I have this in .config also:
Copy code
[auth]
kubernetes_service_account=<SERVICE_ACCOUNT>
am I missing something?
y
hey - so we’ve been steadily moving away from
flyte-cli
in fact, see the release notes we published for flytekit earlier today: https://github.com/flyteorg/flytekit/releases/tag/v0.30.0 under the “Removal of legacy API” section
can you try using flytectl?
Copy code
flytectl -c ~/.flyte/your_config.yaml register files /Users/user/_pb_output/* -p flytesnacks -d development --version some_version --k8sServiceAccount my_svc --outputLocationPrefix "<s3://my-s3-bucket/raw-data>"
something like that.
flytectl also supports the registering of
.tgz
files, so you can do
register files --archive some.tgz
a
yeah, i know that flyte-cli is deprecated, and moving to flytectl is on the plan but upgrading will take some time... At this time I'm just trying to fix some issue that requires tasks to run under a non default kube service account
y
wrt your original question though, no, there isn’t anything wrong with that. that should work.
what version of flytekit are you on?
a
Flyte CLI! Version: 0.24.0
y
and you’re sure you’re launching the correct launch plan?
a
i'm just launching a version of the workflow and it looks right
y
can you confirm with the admin api?
something like that.
in the spec, you should see the auth_role that got picked up.
message has been deleted
a
any way I can check the launch plan in the console?
and where do I find the spec?
y
can you fill in the url above?
you’ll need to replace everything ofc
a
i'm not sure i understand the pattern there
y
the host, delete the port, the project/domain/launch_plan_name/version
launch_plan_name is typically just the workflow name
👍 1
message has been deleted
like when you hit “Launch”, the string in that box
a
i guess my url is incorrect... i get this
Copy code
upstream connect error or disconnect/reset before headers. reset reason: remote reset
y
a
same
y
@Miggy help…
a
@Miggy’s oof 🙂
y
i feel like there was something weird about how the networking was done
but i don’t remember the specifics
a
1 sec, i'll get the correct url from the console
ok. now I got something
it shows correct kubernetes_service_account
y
so the launch plan spec shows the svc account you want, but when you go and launch it, the pods don’t have it?
a
yes
so i checked pods for the most recent execution and they do have correct service account
looks like it's a problem with the launch plan. The one that had empty auth section created execution with default service account, and one that didn't have auth section worked as expected
y
could you try with the version of flytekit that works?
a
just to close the thread here, the issue has been fixed by migrating to flytectl
🖖 1
111 Views