Thanks Slava for reply. For everyone benefit (in case others come across the same issue) it was all down to my custom scc *priority* which was *null*. Once i set it to a value higher than 0 ( default 'restricted' scc has 0) then everything works as expected.
Thanks guys ! On Tue, Jun 19, 2018 at 11:26 AM, Vyacheslav Semushin <[email protected]> wrote: > 2018-06-19 10:31 GMT+02:00 Daniel Comnea <[email protected]>: > >> >> >> On Mon, Jun 18, 2018 at 11:19 PM, Jordan Liggitt <[email protected]> >> wrote: >> >>> 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. >>> >> [DC]: that was not removed, it was added in step 2) and never removed >> however during step 4) (open shift upgrade) something happened which made >> the new pods subject to default restricted policy. >> > > If "pods started to crash", it means that they were re-created (or new > ones were added). > > Could you show us a pod definition (oc get pod <name> -o yaml? > > > -- > Slava Semushin | OpenShift >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
