-
Notifications
You must be signed in to change notification settings - Fork 931
New issue
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
Allow vm security.shared
#14413
Allow vm security.shared
#14413
Conversation
Signed-off-by: Wesley Hershberger <[email protected]>
Heads up @mionaalex - the "Documentation" label was applied to this issue. |
Signed-off-by: Wesley Hershberger <[email protected]>
Signed-off-by: Wesley Hershberger <[email protected]>
564957e
to
71c1756
Compare
Hrm, im not sure why that is needed, because that |
Also interesting that you mention container volumes here, im not opposed to this at all, but this might introduce additional complexities wrt to idmapping, so might be a "phase 2" feature, as the primary driver for the feature you're working on is to add support for attaching VM root volumes to another VM for recovery/export/import. |
I totally
As we found while I was working on cluster member limits, making decisions based on the running state of instances is prone to races. We should require We can put this on hold until I've put together a spec. |
Lets close this for now. |
This is a preparatory change for attaching
virtual-machine
andtype volumes to instances.container
security.shared
will be required for in order to attachvirtual-machine
volumes to other VMs.Also a few bits I noticed in the docs.