This repository has been archived by the owner on Nov 19, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #35
Breaking changes
Over the 1.6 release cycle Kubernetes switched the ever present
v1.ObjectMeta
to its own API group. A non-breaking change to adopt this would require rewrites of all 1.6 proto files, so this client will do the same breaking change as the official client and switch the import path. Users should update code to refer to the new package.As an example, the README snippet changed from:
to:
API group changes
What about alpha API groups only in 1.5?
As Kubernetes deprecates alpha APIs, the official client removes support for them. That means if you use an API group that was alpha in 1.5 and updated to beta in 1.6 (for example, RBAC or certificates), you can't compile a program with the official client that works on both versions.
This client preserves all API groups from all versions of Kubernetes, but wont do the translation for you. To support multiple Kubernetes versions, users should detect the version of the API server, then use the group associated with that version.