This is not a bad idea to do in admission control as part of the namespace existence check.
Can you elaborate a little more what you are trying to build around the feature to see if there is anything else that would be required? I am not sure it should be an annotation versus a field in metadata, i.e. metadata.namespaceUid or something similar. Thanks, On Wednesday, March 2, 2016, Mateus Caruccio <[email protected]> wrote: > Is there any way to tie resources (pod, pvc, secrets, bc, etc) to it's > belonging namespace without looking for namespace's lifetime? > > Today I can do it by watching and recording the create and delete events > for a namespace, then associate any resources to that namespace, but it > doesn't seams to be the best approach. Namespaces can be destroyed and > recreated by a different user with same name. > > I'm looking for something like automatically adding an annotation > containing namespace's uid to all resources created inside it (some sort of > primary key), as soon as the resource is created. > > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com - Eliminamos a Gravidade >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
