Being able to prefix the apiserver with a path is useful to some folks. The tradeoff being that general url generation gets much more difficult. In addition, in the real world URLs tend to drift (hosts, paths) so persisting "real urls" requires a fair amount of planning for the future to allow migrations.

The primary use case for prefixing the base path is to run two installations on the same server, or to fit into a root domain (mycompany.com/kubernetes/api) that has an existing proxy or load balancing infrastructure, or because the chosen prefix "api" is not preferred.

On Sep 29, 2014, at 1:45 PM, Dawn Chen notifications@github.com wrote:

PR 1475 assumes there is a fixed path prefixes in the apiserver and client, so that it can retrieve version like this:

var versionFromSelfLink = regexp.MustCompile("/api/([^/]*)/")
...
version := versionFromSelfLink.FindStringSubmatch(jsonBase.SelfLink())

But above assumption is not valid today, we should do something to enforce such assumption, or find another way to retrieve version.

@smarterclayton

—
Reply to this email directly or view it on GitHub.

I think that regexp is compatible with prefixes, no? Does it need to change?

Our prefix is /osapi/, which is think triggered this

Oh, well, that's unfortunate. Hrm.

We definitely shouldn't hardcode the api prefix here.

Isn't there a better way than parsing selfLink?

Or maybe we should just represent object references using relative URLs?

I think this is prerequisite for #2098.

I dont see https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/api/ref.go using that regex anymore. It is extracting the version from ObjectReference.
API prefix is not harcoded anywhere in that function or file.