Skip to content
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.

More policies to consider #29

Open
alban opened this issue Dec 11, 2018 · 2 comments
Open

More policies to consider #29

alban opened this issue Dec 11, 2018 · 2 comments

Comments

@alban
Copy link
Contributor

alban commented Dec 11, 2018

Some policies to consider:

  • no (Cluster)RoleBinding on a 'default' service account
  • no (Cluster)RoleBinding for cluster-admin
  • no ConfigMap containing strings like aws_secret_access_key=
@marwinski
Copy link
Contributor

Some comments / ideas from my side:

(1) Above sounds like a good idea which might complement my other idea (see separate ticket)
(2) I don't fully understand. Do you want to prevent this in general or just for service accounts? It appears to make a lot of sense for the latter but not for users / groups. It would also break a lot of admittedly bad behaviour - so it would probably be quite good to do that :-)
(3) I believe we should not try to restrict what people put into config maps...

@alban
Copy link
Contributor Author

alban commented Dec 17, 2018

re (2): I was thinking of service accounts indeed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants