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
It would be desirable to be able to limit image remotes per project similarly to how we can already limit containers, cpu, etc. Being able to limit the image remotes by the project would allow for better security in terms of what users can launch in specific projects. If I have a project that all the images are supposed to be NIST compliant, I would like to force everyone on a server to use a specific remote when in that project to ensure that the images are what are deemed "complaint" on our side.
Required information
Issue description
It would be desirable to be able to limit image remotes per project similarly to how we can already limit containers, cpu, etc. Being able to limit the image remotes by the project would allow for better security in terms of what users can launch in specific projects. If I have a project that all the images are supposed to be NIST compliant, I would like to force everyone on a server to use a specific remote when in that project to ensure that the images are what are deemed "complaint" on our side.
It would also be nice if project image remote limits could be exposed through the api so then it would be able to assist this lxd-ui request of additional remotes in the ui
The text was updated successfully, but these errors were encountered: