You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully deployed NemoClaw into my Kubernetes cluster with OpenRouter inference and multiple agents, all responding and functioning as expected.
I have rebuilt the sandbox with kubectl and awscliv2 included, but I'm unclear on the best approach for passing short-lived credentials into it. The workspace container authenticates with AWS/EKS via IRSA and a ServiceAccount token, but it's not obvious how these credentials can be forwarded to or consumed by the agents securely.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi NemoClaw team,
I have successfully deployed NemoClaw into my Kubernetes cluster with OpenRouter inference and multiple agents, all responding and functioning as expected.
I have rebuilt the sandbox with
kubectlandawscliv2included, but I'm unclear on the best approach for passing short-lived credentials into it. The workspace container authenticates with AWS/EKS via IRSA and a ServiceAccount token, but it's not obvious how these credentials can be forwarded to or consumed by the agents securely.Beta Was this translation helpful? Give feedback.
All reactions