Namuhla, ngoSepthemba 18, kukhishwe inguqulo elandelayo ye-Kubernetes - 1.16. Njengenjwayelo, ukuthuthukiswa okuningi nemikhiqizo emisha kusilindile. Kodwa ngingathanda ukudonsela ukunaka kwakho ezigabeni zefayela ezidingekayo
Ngokuvamile, badinga ukungenelela okwenziwa ngesandla...
Ake siqale ngokushesha ngoshintsho olungase luthinte wonke umuntu osebenze ne-kubernetes isikhathi eside ngokwanele. I-Kubernetes API ayisasekeli izinguqulo ze-API yensiza yefa.
Uma kukhona obengazi noma akhohlwe...Inguqulo ye-API yesisetshenziswa ikhonjiswe ku-manifest, kunkambu apiVersion: apps/v1
Okuthiwa:
Uhlobo lwensiza
inguqulo endala
Yini okufanele ishintshwe
Zonke izinsiza
izinhlelo zokusebenza/v1beta1
izinhlelo zokusebenza/v1beta2
izinhlelo zokusebenza/v1
ukuthunyelwa
idaemonset
ukuphindaphinda
isandiso/v1beta1
izinhlelo zokusebenza/v1
izinqubomgomo zenethiwekhi
izandiso/v1beta1
networking.k8s.io/v1
izinqubomgomo ze-podsecurity
izandiso/v1beta1
inqubomgomo/v1beta1
Ngingathanda futhi ukudonsela ukunaka kwakho eqinisweni lokuthi izinto zohlobo Ingress
nayo ishintshile apiVersion
on networking.k8s.io/v1beta1
. Incazelo endala extensions/v1beta1
isasekelwa, kodwa kunesizathu esihle sokubuyekeza le nguqulo kuma-manifest ngesikhathi esifanayo.
Kukhona izinguquko eziningi kumalebula esistimu ahlukahlukene (amalebula we-Node) afakwe kuma-node.
U-Kubelet wayenqatshelwe ukusetha amalebula angafanele (ngaphambilini ayengasethwa ngokhiye bokuqalisa kubelet --node-labels
), bashiya lolu hlu kuphela
kubernetes.io/hostname
kubernetes.io/instance-type
kubernetes.io/os
kubernetes.io/arch
beta.kubernetes.io/instance-type
beta.kubernetes.io/os
beta.kubernetes.io/arch
failure-domain.beta.kubernetes.io/zone
failure-domain.beta.kubernetes.io/region
failure-domain.kubernetes.io/zone
failure-domain.kubernetes.io/region
[*.]kubelet.kubernetes.io/*
[*.]node.kubernetes.io/*
Amalebula beta.kubernetes.io/metadata-proxy-ready
, beta.kubernetes.io/metadata-proxy-ready kanye ne-beta.kubernetes.io/kube-proxy-ds-ready azisangezwa kumanodi amasha, futhi izingxenye ezengeziwe ezengeziwe seziqalile ukusebenzisa amalebula ahluke kancane njengezikhethi zamanodi:
Isakhi
Ilebula endala
Ilebula yamanje
kube-ummeleli
beta.kubernetes.io/kube-proxy-ds-ready
node.kubernetes.io/kube-proxy-ds-ready
i-ip-mask-ejenti
beta.kubernetes.io/masq-agent-ds-ready
node.kubernetes.io/masq-agent-ds-ready
ummeleli wemethadatha
beta.kubernetes.io/metadata-proxy-ready
cloud.google.com/metadata-proxy-ready
I-kubeadm manje isusa ifayela lokuqala lokucushwa kwe-kublet ngemuva kwayo bootstrap-kubelet.conf
. Uma amathuluzi akho abefinyelela leli fayela, shintshela ekusebenziseni kubelet.conf
, egcina izilungiselelo zamanje zokufinyelela.
I-Cadvisor ayisanikezeli ngamamethrikhi pod_name
ΠΈ container_name
uma uzisebenzisile ku-Prometheus, hamba kumamethrikhi pod
ΠΈ container
ngokulandelana.
Kukhishwe okhiye ngomyalo womugqa:
Isakhi
Ukhiye ohoxisiwe
hyperkube
--make-symlink
kube-ummeleli
--isitsha-somthombo
Isihleli siqale ukusebenzisa inguqulo ye-v1beta1 ye-API Yomcimbi. Uma usebenzisa amathuluzi enkampani yangaphandle ukuze uhlanganyele ne-API Yomcimbi, shintshela enguqulweni yakamuva.
Isikhashana sokuhlekisa. Ngesikhathi kulungiselelwa ukukhululwa 1.16, kwenziwa izinguquko ezilandelayo:
- isuse isichasiselo
scheduler.alpha.kubernetes.io/critical-pod
kunguqulo v1.16.0-alpha.1 - ibuyise isichasiselo
scheduler.alpha.kubernetes.io/critical-pod
kunguqulo v1.16.0-alpha.2 - isuse isichasiselo
scheduler.alpha.kubernetes.io/critical-pod
kunguqulo v1.16.0-beta.1
Sebenzisa inkambu spec.priorityClassName
ukukhombisa ukubaluleka kwephodi.
Source: www.habr.com