Hi All 
 
We had a discussion on this last week . I want to make sure we are all aware of our plans to address custom profiles .
 
Based on my understanding in the 3.x time frame we allowed customers to customize the default scheduler . In 4.7 we introduced the concept of scheduler profile , which is well tested and validated by our team and removed customer ability to customize the scheduler . Since then we have had customers reach out to us asking to give them the ability to either tweek current profiles or build new profiles . Now the challenge is that the openshift control plane is complex and there are interdependent components. Also if something goes wrong with the scheduler it can bring down the control plane that's why we have pre build scheduler profiles .
Now with the GA of secondary scheduler . We have the ability to protect control plane components and have customers deploy their own scheduler for their workload . Using the same concept we have decided to use the operator to give customers a way to modify and deploy profiles and deploy as a new scheduler image  
I have asked @Jan Chaloupka to write a KCS article on . ( why KCS why not openshift doc or blog :  because this an unsupported work around )

1. How to modify existing profiles . Package it into a new scheduler image and deploy it as secondary scheduler
2. How to build new profiles . Package it into a new scheduler image and deploy it as secondary scheduler

From a supportability point of view . Customers will be responsible to build , deploy and support that scheduler . We are open to provide support exceptions for some tweaks that we know or tested to work
 
Long term solution : @Ravi Gudimetla will propose upstream ability to deploy separate profiles per namespace . This will reduce customer burden to re package and deploy profiles as scheuler images . they can just use whatever profile they want in their own name space and we won't let them touch the openshift namespace. 
 
Let me know if you have any questions