Go based implementation of the profiles custom resource?

[jlewi]

Currently the profiles custom controller is implemented using metacontroller with the sync function implemented in jsonnet.

Should we switch to a go based implementation? I think the primary reason for switching to go would be that it has a much higher ceiling; i.e. if we want to do more complicated things either; we won't find ourselves limited by jsonnet. It should also be easier to write unittests.

@kkasravi WDYT

[kkasravi]

yes, Profiles is a good choice because we may need to look up the user as part of creating the Profile to see if the user is in the set of people that can create a Profile. Right now we don't have this concept - any valid IAM user or ServiceAccount will work. Also we could probably reduce the 2 controllers we have (profiles-controller, permissions-controller) to just one.

[lluunn]

Agree that we just need one controller, profile, and it will create the namespace+role+rolebinding.

@kkasravi I can take on this you haven't started?