https://flyte.org
Join Slack
and a quick follow-up: when passing `secret_requests` to `ContainerTask` - how this is made availabl...
# flyte-support
m
and a quick follow-up: when passing 
secret_requests
to 
ContainerTask
- how this is made available within container? I don't see 
/etc/flyte/secrets
mounted
f
ohh, it should be using the webhook
secrets webhook
actually coming soon is pod-templates
you can basically add pod features to container tasks
m
is there a doc link for secrets webhook?
f
m
Sorry, I'm still a little lost. I've used 
secret_requests
with 
ShellTask
for example, and the secrets are mounted within container. But doing the same with `ContainerTask`does not work for me. Should I be doing this differently?
f
Hmm are secrets not working for raw containers, let me check
it seems to be there, i will test it in a bit and ensure
q
Or just use a pod_template and inject secrets there as you like (so you are not bound to the flyte dir or env prefix)
f
Tbh I prefer the Flyte for. It keeps the mealiness of pods from not being exposed unnecessarily and consistent way of specifying secrets
I think this should work - @quaint-diamond-37493 did this work for you
q
Yeah, secrets work with container tasks now. But you can't e.g. completely control the injected env name or file name (if you need that)
f
Aah ya
m
how old is my version? 🙂
Copy code
Flyte Console
UI Version
1.3.4
Admin Version
1.1.46
do I need an upgrade?
q
which flytekit version are you using? IIRC this just needed changes in flytekit
m
flytekit==1.2.1
q
yeah, you need at least v1.3.0b1
m
will try upgrading today and report back
q
should also be in 1.2.4
m
excellent, thank you so much!
q
my pleasure
🙌 2
m
confirm that upgrading fixed it 🙇
166 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by