Clayton Coleman

@bparees @mfojtik @legionus @miminar @dmage some discussions started last week about how we can mitigate downtime of external registries (like registry.access.redhat.com), as well as optimize access to content. This contains...

We need to figure out how to allow label and annotation update on projects for project admins that is "safe". May be whitelist of allowed things to change.

At a minimum description and display, and _maybe_ labels, that's all. On Sep 1, 2015, at 1:43 PM, David Eads [email protected] wrote: We need to figure out how to allow...

It's probably going to be an admin decision. We will have to enable labels for end users as soon as they have more than a few projects. I think we...

Actually - I'm starting to think that annotations and labels a users set on project should be namespaced in the namespace object: user sets label "foo=bar" and annotation "biz=baz", they...

Unfortunately this requires us to define either a reserved namespace for labels the user can set, or vice versa, and is not necessarily safe from a backwards compatibility security perspective....

The container image builder creates has to have something to hold it open. All RUN commands are from exec. I did a docker run equivalent and it worked for me....

/sig instrumentation /sig node /sig scheduling

I don't think we'll make implementable and merged by Tuesday, so should be targeted for 1.20

Yes, this is target alpha for 1.20 assuming we can close the remaining questions in the KEP