Kubernetes 1.16 - yadda ake haɓakawa ba tare da karya komai ba

A yau, Satumba 18, an saki sigar Kubernetes na gaba - 1.16. Kamar koyaushe, yawancin haɓakawa da sabbin samfura suna jiran mu. Amma ina so in ja hankalin ku zuwa sassan Fayil ɗin Ayyukan da ake buƙata CHANJI-1.16.md. Waɗannan sassan suna buga canje-canje waɗanda zasu iya karya aikace-aikacenku, kayan aikin kula da gungu, ko buƙatar canje-canje ga fayilolin daidaitawa.

Gabaɗaya, suna buƙatar sa hannun hannu...

Bari mu fara nan da nan tare da canji wanda zai fi dacewa ya shafi duk wanda ya daɗe yana aiki tare da kubernetes. API ɗin Kubernetes baya goyan bayan sigar API ɗin albarkatun gado.

Idan wanda bai sani ba ko ya manta...An nuna sigar API na albarkatun a cikin bayyanuwa, a cikin filin apiVersion: apps/v1

Wato:

Nau'in albarkatu
tsohon sigar
Abin da ya kamata a maye gurbinsu da

Duk albarkatun
apps/v1beta1
apps/v1beta2
apps/v1

tura abubuwa
daemonset
kwafi
tsawo/v1beta1
apps/v1

manufofin hanyar sadarwa
kari/v1beta1
sadarwar.k8s.io/v1

manufofin tsaro
kari/v1beta1
manufofin/v1beta1

Ina kuma so in jawo hankalin ku zuwa ga gaskiyar cewa abubuwa iri Ingress kuma ya canza apiVersion a kan networking.k8s.io/v1beta1. Tsohuwar ma'ana extensions/v1beta1 har yanzu ana goyan bayan, amma akwai kyakkyawan dalili don sabunta wannan sigar a cikin bayyanar a lokaci guda.

Akwai sauye-sauye da yawa a cikin alamun tsarin daban-daban (Lambobin Node) waɗanda aka shigar akan nodes.

An haramta Kubelet daga saita alamun sabani (a da ana iya saita su ta hanyar maɓallin ƙaddamarwa. kubelet --node-labels), sun bar wannan jerin kawai halatta:

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/*

Labels beta.kubernetes.io/metadata-proxy-ready, beta.kubernetes.io/metadata-proxy-ready da beta.kubernetes.io/kube-proxy-ds-ready ba a ƙara su zuwa sababbin nodes ba, kuma ƙarin ƙarin abubuwa daban-daban sun fara amfani da lakabi daban-daban azaman masu zaɓin kumburi:

Bangare
Tsohuwar lakabi
Lakabin na yanzu

kube-proxy
beta.kubernetes.io/kube-proxy-ds-ready
node.kubernetes.io/kube-proxy-ds-ready

ip-mask-wakili
beta.kubernetes.io/masq-agent-ds-ready
node.kubernetes.io/masq-agent-ds-ready

metadata-proxy
beta.kubernetes.io/metadata-proxy-ready
cloud.google.com/metadata-proxy-ready

kubeadm yanzu yana cire farkon kublet sanyi fayil a bayansa bootstrap-kubelet.conf. Idan kayan aikin ku suna samun dama ga wannan fayil ɗin, sannan canza zuwa amfani kubelet.conf, wanda ke adana saitunan shiga na yanzu.

Cadvisor baya bayar da awo pod_name и container_nameidan kun yi amfani da su a cikin Prometheus, je zuwa awo pod и container daidai da.

An cire maɓallan tare da umarnin layi:

Bangare
Maɓallin ja da baya

hyperkube
--make-symlink

kube-proxy
--kwantenan albarkatu

Mai tsara jadawalin ya fara amfani da sigar v1beta1 na Event API. Idan kuna amfani da kayan aikin ɓangare na uku don hulɗa tare da API Event, canza zuwa sabon sigar.

Lokaci na ban dariya. A lokacin shirye-shiryen saki 1.16, an yi canje-canje masu zuwa:

• cire annotation scheduler.alpha.kubernetes.io/critical-pod a cikin sigar v1.16.0-alpha.1
• ya mayar da bayanin scheduler.alpha.kubernetes.io/critical-pod a cikin sigar v1.16.0-alpha.2
• cire annotation scheduler.alpha.kubernetes.io/critical-pod a cikin v1.16.0-beta.1

Yi amfani da filin spec.priorityClassName don nuna mahimmancin fasfo.

source: www.habr.com