[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Custom SCC assigned to wrong pods



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 <vsemushi redhat com> wrote:
2018-06-19 10:31 GMT+02:00 Daniel Comnea <comnea dani gmail com>:


On Mon, Jun 18, 2018 at 11:19 PM, Jordan Liggitt <jliggitt redhat com> 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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]