We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REANA always mounts user secrets inside jobs even if they don't need them.
This causes an issue which can be reproduced as follows:
CERN_USER
CERN_KEYTAB
W1
W2
$ reana-client run -n W2
$ reana-client secrets-delete CERN_USER CERN_KEYTAB
$ kubectl describe pod reana-run-job-xxxxx-yyy-zz | grep Error Reason: CreateContainerConfigError Warning Failed 6m26s (x3 over 6m27s) kubelet, reana-xxxxx-node-2 Error: couldn't find key CERN_USER in Secret default/reana-secretsstore-xxxxx-yyy-zz Warning Failed 5m24s (x5 over 6m13s) kubelet, reana-xxxxx-node-2 Error: couldn't find key CERN_KEYTAB in Secret default/reana-secretsstore-xxxxx-yyy-zz
The text was updated successfully, but these errors were encountered:
No branches or pull requests
REANA always mounts user secrets inside jobs even if they don't need them.
This causes an issue which can be reproduced as follows:
CERN_USER
andCERN_KEYTAB
.W1
which usesCERN_USER
andCERN_KEYTAB
.W1
and starts working on workflowW2
.$ reana-client run -n W2
W2
doesn't depend onCERN_USER
norCERN_KEYTAB
, so the user deletes those secrets:$ reana-client secrets-delete CERN_USER CERN_KEYTAB
W2
fails under unknown circumstances.The text was updated successfully, but these errors were encountered: