Spinning docker containers from cluster admin but as service account process

This is the email discussion we had with Michael Fieman from IBM.

Hi Sandeep, David

First, the RFE 140136: Symphony with SELinux had been fully completed and had been delivered to
the Fix Center with URL for your download available at:
http://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/Other+software/IBM+Spectrum+Conductor+with+Spark&release=All&platform=All&function=fixId&fixids=sc-2.4.1-build550947-jpmc%3Aplatform_cust_ac_key&includeSupersedes=0

Then for the additional requirement to limit Docker client user to Cluster Administrator OS user we are proposing the following enhanced solution:
1. We will implement additional (optional) environment parameter to be set per Application profile with Boolean value which will enable running that application's sims as Cluster Administrator OS user (e.g. egoadmin)
2. Note that enabling this environment parameter and switching its sims to run as egoadmin will work only for Symphony applications which has SOAM services configured to run services in Docker containers -attempt to set the flag for non-Dockerized application profile will results in failing startup of its services. That will give you flexibility to mix Dockerized and non-Dockerized applications, but it will limit any Dockerized application to have all its service types to use Docker containers only.
3. While the environment parameter can be turn on per application by its Application admin user but it will not create any security hole because in case of disabling the parameter for Dockerized application because then its sim's will be still launched as consumer execution user so its Docker controller won't be able to connect to Docker (as it socket will be restricted only to egoadmin).
4. We also think that current ability for Application admin to set in Docker section of Application profile containerUser to any OS user (as described in https://www.ibm.com/support/knowledgecenter/SSZUMP_7.3.0/reference_sym/app_profile_docker_fileref.html) may result in weakening overall security, so we propose to have a second additional (optional) cluster-wide parameter (set in sd.xml) which will enable ignoring the containerUser value set in any application profile and setting containerUser (i.e. running user inside Docker container) to the application's consumer OS execution user.

We propose to deliver this new requirement functionality in a separate patch intended to be installed on top the already delivered RFE implementation.
We estimated the development and QA will take two weeks complete for that new patch delivery.
Please let us know if the solution is acceptable, and any comments and question you may have.