Align GroupName in pkg/apis

[k82cn]

Is this a BUG REPORT or FEATURE REQUEST?:
enhancement/cleanup

/kind bug
/sig api-machinery

What happened:
In pkg/apis, there're 3 types of GroupName: xxx, xxx.k8s.io, xxx.kubernetes.io. Should we align them to xxx.k8s.io?

@kubernetes/sig-api-machinery-misc

[sttts]

These determine the HTTP path. So we cannot fix our broken naming easily.

[k82cn]

yes. Agree that's complex; I try to create a PR today; but I found lots of code are using text, e.g. "apps".

[sttts]

It break the api, that's the bigger problem.

[deads2k]

I think we should align them (we chose k8s.io) and it can be done by double registering for some period of time.

[k82cn]

I think this's not urgent issue. If we agree to do that, I may contribute after 1.8.

cc/ @smarterclayton

[lavalamp]

We cannot fix this for existing APIs easily. We mandate *.k8s.io for new APIs.

[k82cn]

ok; so we can close this issue I think :).

…

---- Da (Klaus), Ma (马达) | PMP® | Software Architect, IBM Cloud private Development IBM Spectrum Computing, IBM System +86-10-8245 4084 | klaus1982.cn@gmail.com | http://k82.me

On Fri, Jul 14, 2017 at 5:06 AM, Daniel Smith ***@***.***> wrote: We cannot fix this for existing APIs easily. We mandate *.k8s.io for new APIs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48527 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARRLLddI5VJe00wkcwUZ2ufDjYw4mptaks5sNobsgaJpZM4OPFHc> .

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale