-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Implement v1beta3 api #1519
Comments
Another oversight: type Container should be |
Captured both in the checklist. |
Added this and related issues to milestone v0.8. Related discussion thread: https://groups.google.com/forum/#!topic/kubernetes-dev/Y3p_fPOajWg |
Should have a first chunk ready for Monday of the internal update and tests.
|
As a consequence of this change to simplify implementation, we may want to add the attributes |
The serialization round tripping testing code is woefully unprepared to handle scenarios where data that is fuzzed will be lost. In general to have certainty of when / where data is lost, we need to test that the loss is detected (internal -> lossy external -> internal loses data, then clear certain fields and try again and it should not lose data). |
@lavalamp fyi will add a predesign write up here on how to bulk convert objects across 1/2 - 3 in a not insane way. Will want your feedback |
Changes starting to occur in #1600, still very rough. |
Things I'm going to split off or farm off beforehand:
That'll reduce the total scope of the internal migration. |
v1beta3 is now available in master by enabling |
I'm willing to punt on |
Re.: Solve merging a v1beta1 PUT on an existing v1beta3 object I'm willing to call this user error for now. I'd like to get rid of v1beta1. Longer term, I like the idea of storing fields that are unrepresented in a particular API version in annotations. |
Fine with me. ----- Original Message -----
|
With #1225 merged, we can now move forward to v1beta3
Others?
The text was updated successfully, but these errors were encountered: