Redeploying the application creates new pods.
Since you removed the part of your custom scc that allowed it to apply to your pods, those new pods were once again subject to the restricted policy.
Reviving the thread on the custom scc with another question if you don't mind:
After i removed the
from my custom scc i went ahead and done the following:
1) Created Foo project
2) Created my custom scc (which i shared in my previous email)
3) Deployed the app pods
4) Upgraded Openshift to 3.6.1 – pods started to crash due to having the default restricted scc instead of the custom scc previously assigned.
The docs says very clear that only the default scc will be reset to initial state and so i was expecting the POD to pick up the custom scc even if they get bounced during upgrade.
Any thoughts ?