由于公司采用的是1.10.13版本，所以详细看下该版本下的版本发布情况1.10大版本变更说明:
windows-386就是i386windows-amd64amd64，又称“x86-64”或“x64”，是一种64位元的电脑处理器架构。它是建基于现有32位元的x86架构，由amd公司所开发，应用AMD64指令集的自家产品有Athlon64、Athlon64FX、Athlon64X2、Turion64、Opteron及最新的Sempron处理器我们可以看到包中有一个kubernetes-1.10.13\kubernetes\hack\lib\util.sh这个文件的代码可以清晰的看到支持的平台和cpu架构情况
kube::util::host_platform(){localhost_oslocalhost_archcase"$(uname-s)"inDarwin)host_os=darwin;;Linux)host_os=linux;;*)kube::log::error"UnsupportedhostOS.MustbeLinuxorMacOSX."exit1;;esac
case"$(uname-m)"inx86_64*)host_arch=amd64;;i86_64*)host_arch=amd64;;amd64*)host_arch=amd64;;aarch64*)##AArch64是一种ARMv8架构host_arch=arm64;;arm64*)host_arch=arm64;;arm*)host_arch=arm;;i86*)host_arch=x86;;s390x*)host_arch=s390x;;ppc64le*)host_arch=ppc64le;;*)kube::log::error"Unsupportedhostarch.Mustbex86_64,386,arm,arm64,s390xorppc64le."exit1;;esacecho"${host_os}/${host_arch}"}
/bin目录下包含的以下文件apiextensions-apiserver独立的二进制方式cloud-controller-managercloud-controller-manager.docker_tagcloud-controller-manager.tarhyperkube集成版本kube-aggregator独立的二进制版本kube-aggregator.docker_tagkube-aggregator.tarkube-apiserver独立的二进制版本kube-apiserver.docker_tagkube-apiserver.tar(docker镜像版本)kube-controller-manager独立的二进制版本kube-controller-manager.docker_tagkube-controller-manager.tar(docker镜像版本)kube-proxy独立的二进制版本kube-proxy.docker_tagkube-proxy.tar(docker镜像版本)kube-scheduler独立的二进制版本kube-scheduler.docker_tagkube-scheduler.tar(docker镜像版本)kubeadmkubectl独立的二进制版本kubelet独立的二进制版本mounter所以发布的组件有三种形式集成方式、独立的二进制方式、docker镜像方式
包含的客户端二进制程序kube-proxy(node节点部署必须)kubectl(master部署必须，node可有，可无)kubelet（node节点部署必须）kubeadm
ThisreleasecontinuestoenablemoreexistingfeaturesonWindows,includingcontainerCPUresources,imagefilesystemstats,andflexvolumes.ItalsoaddsWindowsservicecontrolmanagersupportandexperimentalsupportforHyper-Visolationofsingle-containerpods.
SIG-OpenStackupdatedtheOpenStackprovidertousenewerAPIs,consolidatedcommunitycodeintoonerepository,engagedwiththeCloudProviderWorkingGrouptohaveaconsistentplanformovingprovidercodeintoindividualrepositories,improvedtestingofprovidercode,andstrengthenedtieswiththeOpenStackdevelopercommunity.
KubeProxyConfigurationBefore:
apiVersion:kubeproxy.config.k8s.io/v1alpha1kind:KubeProxyConfiguration**featureGates:"SupportIPVSProxyMode=true"**KubeProxyConfigurationAfter:
apiVersion:kubeproxy.config.k8s.io/v1alpha1kind:KubeProxyConfiguration**featureGates:****SupportIPVSProxyMode:true**Ifyourclusterwasinstalledbykubeadm,youshouldeditthefeatureGatesfieldinthekubeadm-configConfigMap.Youcandothisusingkubectl-nkube-systemeditcmkubeadm-configbeforeupgrading.Forexample:
kubeadm-configBefore:
apiVersion:v1kind:ConfigMapmetadata:name:kubeadm-configdata:MasterConfiguration:|kubeProxy:config:featureGates:"SupportIPVSProxyMode=true"kubeadm-configAfter:
apiVersion:v1kind:ConfigMapmetadata:name:kubeadm-configdata:MasterConfiguration:|kubeProxy:config:featureGates:SupportIPVSProxyMode:trueIfnofeatureGateswasspecifiedinkubeadm-config,justchangefeatureGates:""tofeatureGates:{}.