Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move docs/examples to v1beta3 #6584

Closed
24 tasks done
nikhiljindal opened this issue Apr 8, 2015 · 27 comments
Closed
24 tasks done

Move docs/examples to v1beta3 #6584

nikhiljindal opened this issue Apr 8, 2015 · 27 comments
Assignees
Labels
area/usability kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone

Comments

@nikhiljindal
Copy link
Contributor

List of tasks based on grep "v1beta1"

@nikhiljindal
Copy link
Contributor Author

Oops, pressed enter by mistake :)
Still editing the issue description.

@nikhiljindal
Copy link
Contributor Author

The list is complete now

@nikhiljindal nikhiljindal self-assigned this Apr 8, 2015
@nikhiljindal nikhiljindal added kind/documentation Categorizes issue or PR as related to documentation. area/usability sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Apr 8, 2015
@bgrant0607 bgrant0607 mentioned this issue Apr 8, 2015
16 tasks
@bgrant0607 bgrant0607 added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 8, 2015
@dchen1107
Copy link
Member

cc/ @caesarxuchao

@bgrant0607
Copy link
Member

We should remove references to v1beta1 in the getting-started guides by removing examples of starting pods/rcs/services and linking to examples in /examples. #5799.

@bgrant0607
Copy link
Member

still v1beta1:

  • examples/guestbook-go
  • examples/storage
  • examples/glusterfs
  • examples/gce-pd
  • examples/liveness
  • contrib/git-sync

@satoshi75nakamoto
Copy link
Contributor

@bgrant0607: what's the current status of this? Do the various yaml file(s) you referenced still need to be changed?

@bgrant0607 bgrant0607 added this to the v1.0 milestone May 14, 2015
@bgrant0607
Copy link
Member

Still plenty of work to be done, yes. Search for v1beta1 in the codebase if you want to help.

@bgrant0607
Copy link
Member

And see also #8087

@satoshi75nakamoto
Copy link
Contributor

@bgrant0607: Okay sounds good. Thanks!

@caesarxuchao
Copy link
Member

Hi @preillyme, I have updated all the examples to v1beta3, though some PR are still waiting to be merged.

@satoshi75nakamoto
Copy link
Contributor

@caesarxuchao thanks for the update.

@caesarxuchao
Copy link
Member

conversion of contrib/git-sync is paused because of #8327

@bgrant0607
Copy link
Member

kubectl proxy and kubectl update also still use v1beta1 examples

cc @jlowdermilk @krousey

@bgrant0607
Copy link
Member

libvirt-coreos still uses v1beta1 @lhuard1A

@bgrant0607
Copy link
Member

@wojtek-t pkg/api/node_example.json needs to be updated to v1beta3

@bgrant0607
Copy link
Member

@wojtek-t Nevermind. The problem is that the selfLink is wrong. #6596 (comment)

@bgrant0607
Copy link
Member

#7629 should have fixed that problem, but we need to update the selfLinks of pkg/api/*_example.json files.

@bgrant0607
Copy link
Member

libvirt-coreos is in progress -- #8273

@wojtek-t
Copy link
Member

@bgrant0607 - thanks for heads up - #8909 is sent out for review

@caesarxuchao
Copy link
Member

postpone update of kubectl proxy due to #8943

Update: fixed by #8948

@bgrant0607
Copy link
Member

@caesarxuchao Postpone what, exactly?

@nikhiljindal
Copy link
Contributor Author

#5799 is, I think, the last remaining task here.
@caesarxuchao @bgrant0607 Any other remaining item?

@bgrant0607
Copy link
Member

Move everything to v1 now? :-)

I'm hoping that could be done by a shell script.

@krousey

@bgrant0607
Copy link
Member

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/usability kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

6 participants