joshi-kamitsukasa

I have difficulty in making a psp because kube-psp-advisor sets required fields as loose policy automatically. Therefore I want to set default psp firstly for only fsGroup, runAsUser, seLinux, supplementalGroups....

>I don't think that's the case. The default settings follow the psp default value. To me, your use case is having a customized default settings. That makes sense.

>I originally thought this was about a customized default settings will take the priority over the suggested one. My prototype uses the default psp when it can't suggest fields. Please...

>If a constraint is more loose in the customized default psp, do you plan to stick with the original one suggested by psp-advisor? Yes. In my case, I basically want...

If a manifest read by psp-advisor has no volume field, psp-advisor set psp customized default psp. If a manifest read by psp-advisor has one or more volume field, psp-advisor set...