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
This task is similar to #2655
Currently manila csi nodeserver takes credentials from the node-publish-secret-* and node-stage-secret-* secrets. In k8s setups, where CSI controller resides in the admin control plane cluster, and the nodeserver resides in the actual workload cluster, having secrets required for the nodeserver is a security risk.
What you expected to happen:
nodeserver should not have an access to openstack secrets, all the operations (such as getting export locations and setting access rights) , which require credentials, can be done on the controller side.
How to reproduce it:
n/a
Anything else we need to know?:
currently node's kubelet gets secret's data from the reference and combines CSI requests with secrets, which is then forwarded to a nodecontroller:
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
This task is similar to #2655
Currently manila csi nodeserver takes credentials from the
node-publish-secret-*
andnode-stage-secret-*
secrets. In k8s setups, where CSI controller resides in the admin control plane cluster, and the nodeserver resides in the actual workload cluster, having secrets required for the nodeserver is a security risk.What you expected to happen:
nodeserver should not have an access to openstack secrets, all the operations (such as getting export locations and setting access rights) , which require credentials, can be done on the controller side.
How to reproduce it:
n/a
Anything else we need to know?:
currently node's kubelet gets secret's data from the reference and combines CSI requests with secrets, which is then forwarded to a nodecontroller:
Environment:
The text was updated successfully, but these errors were encountered: