Custom SCC assigned to wrong pods

Hi, I'm running Origin 3.7.0 and i've created a custom SCC [1] which is being referenced by different Deployments objects using serviceAccountName: foo- scc-restricted. Now the odd thing which i cannot explain is why glusterFS pods [2] which doesn't reference the new created serviceAccountName

Re: Custom SCC assigned to wrong pods

By making your SCC available to all authenticated users, it gets added to the set considered for every pod run by every service account: users: - system:serviceaccount:foo:foo-sa groups: - system:authenticated If you want to limit it to just your foo-sa service account, you should remove the

openshift-ansible candidate for origin 3.7 and 3.9

Hello, The CentOS PaaS SIG team (thanks DanyC_) has finished the build for openshift-ansible rpms for 3.7/ 3.8 & 3.9 latest tags. The rpms should already be in the -candidate repo. As the SIG is transitioning to new members, we are all working on learning the process to build the rpms and make

Re: Custom SCC assigned to wrong pods

I see the rational, thank you for quick response and knowledge. On Wed, May 23, 2018 at 10:59 PM, Jordan Liggitt wrote: > By making your SCC available to all authenticated users, it gets added to > the set considered for every pod run by every service account: > > users: >

Re: OpenShift Web Console - 3.9 - Pod / CrashLoopBackOff

2018-05-17 17:18 GMT+02:00 Charles Moulliard : > The trick / solution described there doesn t work. I tried also using the > ansible playbook of Openshift to remove the project and recreate it and the > pod is always recreated with Openshift annotation = anyuid > The reason

CentOS PaaS SIG meeting (2018-05-23

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 23 May 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- automation - Open Floor -- Ricardo Martinelli de Oliveira Senior