-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Remove v1beta1 and v1beta2 api from the codebase, docs, and gh_pages #8087
Comments
Delete LegacyHostIP |
Stop running v1beta1 tests on shippable/travis |
@nikhiljindal has a change in progress for this-- he needed it for the upgrade script. |
/subscribe |
@dchen1107 Was going to generate a new container VM image with v1beta3 support, which was required before we can start deleting v1beta1. |
This change should not remove the legacy scope behavior. It can remove the tests and any Kube specific stuff, but we need to leave legacy in for a bit longer. |
@smarterclayton What do you mean by "legacy scope"? |
The pkg/apiserver and pkg/api/meta concepts for RESTScopeNamespaceLegacy and the support in api_installer.go for the legacy paths. We'll need those for a few more weeks in OpenShift. ----- Original Message -----
|
There are still 150 references to v1beta1: I suggest dividing them up among multiple people. Possible categories:
|
I will first work on
On Wed, May 13, 2015 at 12:02 AM, Brian Grant notifications@github.com
Regards, |
I will take a look at /cluster |
@nikhiljindal We already cut one image: container-vm-v20150505 which includes kubernetes 0.16.2 and docker 1.6.0. Next one can include kubernetes 0.17.X and docker 1.6.2. So that we have two image releases include both APIs. You can drop v1beta1 now. cc/ @zmerlynn |
We also need to eliminate minions from the API: #8240 |
GUI: #8304 |
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/client/record/event_test.go#L76
The above is v1beta1/2 syntax, not v1beta3/v1. Other lines in that file need to similarly be updated. |
Not sure if this is related to the sporadic test failures I see on travis or not. |
I'll take a look on this. |
I don't think this will cause any damage, these strings are not parsed. I will send a PR to fix them anyway. |
Ugh, we're still exposing minions in the API: |
Milestone? |
This was 1.0. Added 1.0 milestone again, but reduced priority. We should allow outstanding PRs related to this to go in, but should look for higher-priority things to spend effort on. |
v1beta1 and 2 have been long gone. Closing the issue. |
As part of migrating everything to an official v1 api, we should remove the earlier versions from the code base and documentation on kubernetes.io
As part of this, I'm going to remove all the v1beta1 and v1beta2 specific code and test cases. I'm also going to update the scripts to stop generating swagger specs for them.
@bgrant0607 @nikhiljindal, any other tasks that I most likely missed?
The text was updated successfully, but these errors were encountered: