docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

API issues edited

This commit is contained in:
ddeyo 2018-09-26 09:19:18 -07:00
parent 4af13dfb6b
commit b0ee74361a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ee/ucp/release-notes.md
View File

@ -38,7 +38,7 @@ upgrade your installation to the latest release.
* These changes are automatically updated for taints. Tolerations for these taints must be updated manually. Specifically, you must: * These changes are automatically updated for taints. Tolerations for these taints must be updated manually. Specifically, you must:
* Change node.alpha.kubernetes.io/notReady to node.kubernetes.io/not-ready * Change node.alpha.kubernetes.io/notReady to node.kubernetes.io/not-ready
* Change node.alpha.kubernetes.io/unreachable to node.kubernetes.io/unreachable * Change node.alpha.kubernetes.io/unreachable to node.kubernetes.io/unreachable
* JSON configuration files (i.e. JSON files that you use with `kubectl create -f pod.json`) that contain fields with incorrect casing will no longer be valid. You must correct these files before upgrading. When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 and the API server will once again be enforcing the correct case. During this time, the `kubectl` tool continued to enforce case-sensitive keys, so users that strictly manage resources with kubectl will be unaffected by this change. * JSON configuration used with `kubectl create -f pod.json` containing fields with incorrect casing are no longer valid. You must correct these files before upgrading. When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 so the API server will again enforce correct casing. During this time, the `kubectl` tool continued to enforce case-sensitive keys, so users that strictly manage resources with kubectl will be unaffected by this change.
* If you have a pod with a subpath volume PVC, there’s a chance that after the upgrade, it will conflict with some other pod; see https://github.com/kubernetes/kubernetes/pull/61373. It’s not clear if this issue will just prevent those pods from starting or if the whole cluster will fail. * If you have a pod with a subpath volume PVC, there’s a chance that after the upgrade, it will conflict with some other pod; see https://github.com/kubernetes/kubernetes/pull/61373. It’s not clear if this issue will just prevent those pods from starting or if the whole cluster will fail.
# Version 3.0 # Version 3.0