github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 01:06:27 +00:00
Code Issues Projects Releases Wiki Activity

fix mistakes in api changes

Browse Source 
Signed-off-by: Xianglin Gao <xlgao@zju.edu.cn>
This commit is contained in:
Xianglin Gao 2016-08-11 11:14:09 +08:00
parent 87f71a1ad0
commit 492a88f01d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/devel/api_changes.md
View File

@ -493,7 +493,7 @@ hack/update-generated-protobuf.sh
The vast majority of objects will not need any consideration when converting The vast majority of objects will not need any consideration when converting
to protobuf, but be aware that if you depend on a Golang type in the standard to protobuf, but be aware that if you depend on a Golang type in the standard
library there may be additional work requried, although in practice we typically library there may be additional work required, although in practice we typically
use our own equivalents for JSON serialization. The `pkg/api/serialization_test.go` use our own equivalents for JSON serialization. The `pkg/api/serialization_test.go`
will verify that your protobuf serialization preserves all fields - be sure to will verify that your protobuf serialization preserves all fields - be sure to
run it several times to ensure there are no incompletely calculated fields. run it several times to ensure there are no incompletely calculated fields.
@ -752,7 +752,7 @@ The latter requires that all objects in the same API group as `Frobber` to be
replicated in the new version, `v6alpha2`. This also requires user to use a new replicated in the new version, `v6alpha2`. This also requires user to use a new
client which uses the other version. Therefore, this is not a preferred option. client which uses the other version. Therefore, this is not a preferred option.
A releated issue is how a cluster manager can roll back from a new version A related issue is how a cluster manager can roll back from a new version
with a new feature, that is already being used by users. See with a new feature, that is already being used by users. See
https://github.com/kubernetes/kubernetes/issues/4855. https://github.com/kubernetes/kubernetes/issues/4855.