Rook: OSD daemonset should be able to run unprivileged
The OSD containers should be able to run unprivileged in the following scenarios:
- The admin has already provisioned the storage devices on a node (for bluestore)
- Directories will be used for filestore
The default seems like it should be to run unprivileged. If the admin wants Rook to do the provisioning of the devices he could override it with a flag and run privileged.
ceph-rados
travisn
All 2 comments
related to #82
bassam
on 14 Feb 2017
The privileged portion of the pods could be carried out by an Init Container.
It seems like separating storage initialization/verification from OSD startup could be a smart thing to do. At least in the case of Init Containers the OSD container wouldn't start without the initial formatting/verification returning success.
bzub
on 13 Mar 2017
👍4
Was this page helpful?
0 / 5 - 0 ratings
Related issues
gustavomr
路
4Comments
kdoustar
路
3Comments
Negashev
路
4Comments
aocheretnoy
路
5Comments
billimek
路
3Comments
Most helpful comment
The privileged portion of the pods could be carried out by an Init Container.
It seems like separating storage initialization/verification from OSD startup could be a smart thing to do. At least in the case of Init Containers the OSD container wouldn't start without the initial formatting/verification returning success.