osadm registry --create puts it in the current project

[sosiouxme]

I'm not certain if this is a bug or feature, but I'm leaning toward bug.

If you switch projects before creating a registry with osadm registry, it goes into that project, not default.

I may be wrong, but I don't think you can actually use a registry that's in a project. If I'm wrong and builds/deploys in a project can just start using it as a registry, it's still very surprising and confusing and should probably require the admin to be explicit that they want it in the project.

[liggitt]

the registry always goes in a namespace... question is which one

[ncdc]

We expect it in default

[liggitt]

I don't like assuming it is in the default namespace. What depends on that?

[derekwaynecarr]

It's possible we may not have rights to default in future deployment topologies. Prefer it to be configurable as well.

[ncdc]

@liggitt https://github.com/openshift/origin/blob/master/pkg/cmd/server/origin/master.go#L156-L161

[liggitt]

When did that go in? We shouldn't be getting that from an environment variable, that should be part of config. While were at it, so should the namespace we expect the registry service to be in, right?

[ncdc]

@liggitt that's been in there for a long time

[liggitt]

Related: #2581