{"id":30272,"date":"2019-10-31T21:34:36","date_gmt":"2019-10-31T18:34:36","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv\/"},"modified":"2019-10-31T21:34:36","modified_gmt":"2019-10-31T18:34:36","slug":"kubernetes-1-14-obzor-osnovnyh-novshestv","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv","title":{"rendered":"Kubernetes 1.14: pregled glavnih noviteta","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Kubernetes 1.14: pregled glavnih noviteta\" src=\"\/wp-content\/uploads\/2019\/03\/8fb5be29668f55ec42d31eb47200b639.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nOve no\u0107i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/sig-release\/tree\/master\/releases\/release-1.14#timeline\">odr\u017eat \u0107e se<\/a><\/noindex> novi izdanja Kubernetes \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/sig-release\/tree\/master\/releases\/release-1.14\">1.14<\/a><\/noindex>. Prema tradiciji na\u0161eg bloga, predstavit \u0107emo klju\u010dne promjene u novoj verziji ovog izvrsnog Open Source proizvoda.<\/p>\n<p>Informacije kori\u0161tene za pripremu ovog materijala uzete su iz <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/spreadsheets\/u\/1\/d\/116X6E-lmDJG5UZPlqDAFw8hN9vS6SNY4qRNZ9fKtsMU\/edit#gid=0\">tablica pra\u0107enja pobolj\u0161anja Kubernetes-a<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/blob\/release-1.14\/CHANGELOG-1.14.md\">CHANGELOG-1.14<\/a><\/noindex> i odgovaraju\u0107ih issues, pull requests, Kubernetes Enhancement Proposals (KEP).<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Zapo\u010det \u0107emo s va\u017enim uvodom od SIG cluster-lifecycle: <b>dinami\u010dki visok dostupni klasteri<\/b> Kubernetes (a ako budemo precizniji, onda self-hosted HA deployments) sada <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/357\">mogu se kreirati<\/a><\/noindex> pomo\u0107u poznatih (u kontekstu klastera s jednim \u010dvorom) komandi <code>kubeadm<\/code> (<code>init<\/code> i <code>join<\/code>). Ukratko, za to:<\/p>\n<ul>\n<li> korisni\u010dki certifikati klastera se premje\u0161taju u tajne;<\/li>\n<li> za omogu\u0107avanje upotrebe klastera etcd unutar K8s klastera (tj. osloba\u0111anje od vanjske ovisnosti) uklju\u010den je <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/coreos\/etcd-operator\">etcd-operator<\/a><\/noindex>;<\/li>\n<li> dokumentiraju se preporu\u010dene postavke za vanjski optere\u0107iva\u010d, koji osigurava visoku dostupnost (u budu\u0107nosti se planira mogu\u0107nost osloba\u0111anja i od ove ovisnosti, ali ne u ovoj fazi).<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes 1.14: pregled glavnih noviteta\" src=\"\/wp-content\/uploads\/2019\/03\/0e82b7e8db1ad117dc87f68fa4669431.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Arhitektura HA klastera Kubernetes, stvorena s kubeadm<\/i><\/p>\n<p>Detalje o implementaciji mo\u017eete prona\u0107i u <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/document\/d\/1P3oUJ_kdaRSTlGONujadGBpYegjn4RjBNZLHZ4zU7lI\/edit#\">design proposal<\/a><\/noindex>. Ova funkcionalnost je zaista dugo \u010dekana: alpha verzija se o\u010dekivala jo\u0161 u K8s 1.9, ali je stigla tek sada.<\/p>\n<h2>API<\/h2>\n<p>\nKomanda <code>apply<\/code> i uop\u0107e <b>dekorativno upravljanje objektima<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/555\">premje\u0161teni<\/a><\/noindex> iz <code>kubectl<\/code> u apiserver. Samo programeri kratko obja\u0161njavaju svoje rje\u0161enje time da <code>kubectl apply<\/code> \u2014 temeljni dio rada s konfiguracijama u Kubernetesu, me\u0111utim, 'je puna gre\u0161aka i te\u0161ko se popravlja', zbog \u010dega se ova funkcionalnost mora dovesti u normalno stanje i premjestiti u control plane. Jednostavni i o\u010diti primjeri postoje\u0107ih problema danas:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes 1.14: pregled glavnih noviteta\" src=\"\/wp-content\/uploads\/2019\/03\/379b0d830491bbb0e7ac3c3ccfff71c4.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDetalii o implementaciji \u2014 u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/blob\/master\/keps\/sig-api-machinery\/0006-apply.md\">KEP<\/a><\/noindex>. Trenutna spremnost \u2014 alpha verzija (napredak do beta verzije planiran je za sljede\u0107e izdanje Kubernetes).<\/p>\n<p>U alpha verziji postalo je dostupno <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/692\">mogu\u0107nost<\/a><\/noindex> kori\u0161tenje sheme OpenAPI v3 za <b>kreiranje i objavljivanje OpenAPI dokumentacije za CustomResources<\/b> (CR), kori\u0161tenih za validaciju (na strani poslu\u017eitelja) korisni\u010dki definiranih resursa K8s (CustomResourceDefinition, CRD). Objavljivanje OpenAPI za CRD omogu\u0107ava klijentima (na primjer, <code>kubectl<\/code>) da izvr\u0161e validaciju na svojoj strani (u okviru <code>kubectl create<\/code> i <code>kubectl apply<\/code>) i pru\u017eaju dokumentaciju o shemi (<code>kubectl explain<\/code>). Detalji \u2014 u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/blob\/master\/keps\/sig-api-machinery\/00xx-publish-crd-openapi.md\">KEP<\/a><\/noindex>.<\/p>\n<p>Dosada\u0161nji logovi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74837\">sada se otvaraju<\/a><\/noindex> s oznakom <code>O_APPEND<\/code> (a ne <code>O_TRUNC<\/code>) \u0432\u043e \u0438\u0437\u0431\u0435\u0436\u0430\u043d\u0438\u0435 \u043f\u043e\u0442\u0435\u0440\u0438 \u043b\u043e\u0433\u043e\u0432 \u0432 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0441\u0438\u0442\u0443\u0430\u0446\u0438\u044f\u0445 \u0438 \u0434\u043b\u044f \u0443\u0434\u043e\u0431\u0441\u0442\u0432\u0430 truncate&#8217;\u0430 \u043b\u043e\u0433\u043e\u0432 \u0432\u043d\u0435\u0448\u043d\u0438\u043c\u0438 \u0443\u0442\u0438\u043b\u0438\u0442\u0430\u043c\u0438 \u0434\u043b\u044f \u0440\u043e\u0442\u0430\u0446\u0438\u0438.<\/p>\n<p>Tako\u0111er, u kontekstu Kubernetes API-a valja napomenuti da u <code>PodSandbox<\/code> i <code>PodSandboxStatus<\/code> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73833\">dodano je<\/a><\/noindex> polje <code>runtime_handler<\/code> za pra\u0107enje informacija o <code>RuntimeClass<\/code> \u0432 pod&#8217;\u0435 (\u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0435 \u043e \u043d\u0451\u043c \u0447\u0438\u0442\u0430\u0439\u0442\u0435 \u0432 \u0442\u0435\u043a\u0441\u0442\u0435 \u043f\u0440\u043e <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/424331\/\">izdanju Kubernetes 1.12<\/a><\/noindex>, gdje je ova klasa prvi put predstavljena kao alfa-verzija), a u Admission Webhooks <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74998\">implementirano je<\/a><\/noindex> mogu\u0107nost odre\u0111ivanja koje verzije <code>AdmissionReview<\/code> podr\u017eavaju. Kona\u010dno, u pravilima Admission Webhooks sada <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74477\">mo\u017eete ograni\u010diti<\/a><\/noindex> \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u044b \u0438\u0445 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f namespace&#8217;\u0430\u043c\u0438 \u0438 \u0440\u0430\u043c\u043a\u0430\u043c\u0438 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430.<\/p>\n<h2>Skladi\u0161ta<\/h2>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/storage\/volumes\/#local\"><code><b>PersistentLocalVolumes<\/b><\/code><\/a><\/noindex>, koja su imala status beta-verzije od izdanja <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/353114\/\">K8s 1.10<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74769\">proklamirana su<\/a><\/noindex> stabilnima (GA): ova funkcionalnost vi\u0161e se ne isklju\u010duje i bit \u0107e uklonjena u Kubernetes 1.17.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/559\">Mogu\u0107nost<\/a><\/noindex> kori\u0161tenja varijabli okru\u017eenja poznatog kao <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/inject-data-application\/downward-api-volume-expose-pod-information\/#capabilities-of-the-downward-api\">Downward API<\/a><\/noindex> (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0438\u043c\u0435\u043d\u0438 pod&#8217;\u0430) \u0434\u043b\u044f \u043d\u0430\u0437\u0432\u0430\u043d\u0438\u0439 \u0434\u0438\u0440\u0435\u043a\u0442\u043e\u0440\u0438\u0439, \u043c\u043e\u043d\u0442\u0438\u0440\u0443\u0435\u043c\u044b\u0445 \u043a\u0430\u043a <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/storage\/volumes\/#using-subpath\"><code>subPath<\/code><\/a><\/noindex>, do\u017eivjela je razvoj \u2014 u obliku novog polja <code>subPathExpr<\/code>, uz pomo\u0107 kojeg se sada odre\u0111uje potrebno ime direktorija. Ova funkcionalnost prvi put je predstavljena u Kubernetes 1.11, no i za 1.14 ostala je u statusu alfa-verzije.<\/p>\n<p>Kao i u prethodnom izdanju Kubernetes, predstavljene su zna\u010dajne promjene za aktivno razvijaju\u0107i CSI (Container Storage Interface):<\/p>\n<h3>CSI<\/h3>\n<p>\npostala je dostupna (u okviru alfa-verzije) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/556\">podr\u0161ka<\/a><\/noindex> <b>promjene veli\u010dine za CSI-volume<\/b>. Za njezino kori\u0161tenje potrebno je uklju\u010diti feature gate pod nazivom <code>ExpandCSIVolumes<\/code>, kao i podr\u0161ku za ovu operaciju u odre\u0111enom CSI-drivers.<\/p>\n<p>Jo\u0161 jedna funkcionalnost za CSI u alfa-verziji \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/596\">mogu\u0107nost<\/a><\/noindex> \u0441\u0441\u044b\u043b\u0430\u0442\u044c\u0441\u044f \u043d\u0430\u043f\u0440\u044f\u043c\u0443\u044e (\u0442.\u0435. \u0431\u0435\u0437 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f PV\/PVC) \u043d\u0430 CSI-\u0442\u043e\u043c\u044b \u0432 \u0440\u0430\u043c\u043a\u0430\u0445 \u0441\u043f\u0435\u0446\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 pod&#8217;\u043e\u0432. \u042d\u0442\u043e <b>ukida ograni\u010denje kori\u0161tenja CSI-a samo za daljinska skladi\u0161ta podataka<\/b>, otvaraju\u0107i im vrata u svijet <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes-csi.github.io\/docs\/ephemeral-local-volumes.html\">local ephemeral volumes<\/a><\/noindex>. Za kori\u0161tenje (<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/vladimirvivien\/kubernetes.github.io\/blob\/b78107abfdb2b5877973b84062d93cdf98ef1b9c\/content\/en\/docs\/concepts\/storage\/volumes.md#csi-ephemeral-volumes\">primjer iz dokumentacije<\/a><\/noindex>) potrebno je uklju\u010diti <code>CSIInlineVolume<\/code> feature gate.<\/p>\n<p>Napredak je primije\u0107en i u 'unutra\u0161njosti' Kubernetes-a vezane uz CSI, koje nisu toliko vidljive krajnjim korisnicima (sistemskim administratorima)\u2026 U ovom trenutku, programeri su prisiljeni odr\u017eavati dvije verzije svakog skladi\u0161nog plugina: jednu \u2014 'na stari na\u010din', unutar k\u00f4dne baze K8s (in-tree), a drugu \u2014 u okviru novog CSI <i>(vi\u0161e o njemu mo\u017eete pro\u010ditati, na primjer, u <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/424211\/\">ovdje<\/a><\/noindex>)<\/i>. Ovo uzrokuje razumne neugodnosti koje je potrebno rije\u0161iti dok se CSI stabilizira kao takav. Nije mogu\u0107e jednostavno uzeti i proglasiti zastarjelim (deprecated) API interne (in-tree) plugine zbog <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/reference\/using-api\/deprecation-policy\/#deprecating-parts-of-the-api\">odgovaraju\u0107e politike Kubernetes-a<\/a><\/noindex>.<\/p>\n<p>Sve je to dovelo do toga da su alfa-verzije dostigle <b><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/625\">proces migracije<\/a><\/noindex> interne kodove plugina<\/b>, koji se provode kao in-tree u CSI pluginima, \u010dime \u0107e briga programera biti svedena na odr\u017eavanje jedne verzije njihovih plugina, a kompatibilnost sa starim API-ima \u0107e biti o\u010duvana i mo\u0107i \u0107e se proglasiti zastarjelim prema standardnom scenariju. O\u010dekuje se da \u0107e do sljede\u0107eg izdanja Kubernetes-a (1.15) biti izvr\u0161ena migracija svih plugina dobavlja\u010da oblaka, implementacija \u0107e dobiti beta-status i bit \u0107e aktivirana u K8s instalacijama prema zadanim postavkama. Detalje potra\u017eite u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/community\/blob\/master\/contributors\/design-proposals\/storage\/csi-migration.md\">design proposal<\/a><\/noindex>. Posljedica ove migracije tako\u0111er je bila <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74544\">odustajanje<\/a><\/noindex> od ograni\u010denja za volumene definirane specifi\u010dnim dobavlja\u010dima oblaka (AWS, Azure, GCE, Cinder).<\/p>\n<p>Osim toga, podr\u0161ka za blok ure\u0111aje s CSI (<code>CSIBlockVolume<\/code>) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74909\">je preba\u010dena<\/a><\/noindex> u beta-verziju.<\/p>\n<h2>\u010cvorovi \/ Kubelet<\/h2>\n<p>\nPredstavljena je alfa-verzija <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/727\">novog endpoint-a<\/a><\/noindex> u Kubelet-u, namijenjenog za <b>davanje metrika o osnovnim resursima<\/b>. Uop\u0107e, ako je ranije Kubelet dobivao statistiku kori\u0161tenja kontejnera iz cAdvisor-a, sada ti podaci dolaze iz izvr\u0161ne okoline kontejnera putem CRI (Container Runtime Interface), no o\u010duvana je kompatibilnost za rad sa starim verzijama Dockera. Ranije prikupljena statistika u Kubelet-u davana je putem REST API-a, a sada se koristi endpoint koji se nalazi na adresi <code>\/metrics\/resource\/v1alpha1<\/code>. Dugoro\u010dna strategija programera <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/issues\/68522\">sastoji se<\/a><\/noindex> u tome da minimizira skup metrika koje Kubelet pru\u017ea. <i>Usput, sami ti metrik <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/pull\/726\">sada nazivaju<\/a><\/noindex> ne \u201ecore metrics\u201d, ve\u0107 \u201eresource metrics\u201d, i opisuju ih kao \u201efirst-class resources, such as cpu, and memory\u201d.<\/i><\/p>\n<p>Zanimljiv detalj: unato\u010d o\u010diglednoj prednosti u performansama gRPC endpoint-a u odnosu na razli\u010dite slu\u010dajeve kori\u0161tenja Prometheus formata <i>(\u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442 \u043e\u0434\u043d\u043e\u0433\u043e \u0438\u0437 benchmark&#8217;\u043e\u0432 \u0441\u043c. \u043d\u0438\u0436\u0435)<\/i>, autori su preferirali tekstualni format Prometheus zbog jasne dominacije ovog sustava pra\u0107enja u zajednici.<\/p>\n<blockquote><p><i>\u00abgRPC nije kompatibilan s glavnim sustavima nadzora. Endpoint \u0107e biti koristan samo za isporuku metrika u Metrics Server ili komponente nadzora koje se izravno integriraju s njim. Kada se koristi ke\u0161iranje u Metrics Serveru, performanse tekstualnog formata Prometheus <b>dovoljno su dobre<\/b> za nas da preferiramo Prometheus umjesto gRPC, s obzirom na \u0161iroku rasprostranjenost Prometheusa u zajednici. Kada format OpenMetrics postane stabilniji, mo\u0107i \u0107emo pribli\u017eiti performanse gRPC pomo\u0107u formata temeljenog na proto.\u00bb<\/i><\/p><\/blockquote>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes 1.14: pregled glavnih noviteta\" src=\"\/wp-content\/uploads\/2019\/03\/ad7e45b61fc4676a2df3c2d33d5688b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>\u041e\u0434\u0438\u043d \u0438\u0437 \u0441\u0440\u0430\u0432\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0445 \u0442\u0435\u0441\u0442\u043e\u0432 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0444\u043e\u0440\u043c\u0430\u0442\u043e\u0432 gRPC \u0438 Prometheus \u0432 \u043d\u043e\u0432\u043e\u043c endpoint&#8217;\u0435 Kubelet \u0434\u043b\u044f \u043c\u0435\u0442\u0440\u0438\u043a. \u0411\u043e\u043b\u044c\u0448\u0435 \u0433\u0440\u0430\u0444\u0438\u043a\u043e\u0432 \u0438 \u0434\u0440\u0443\u0433\u0438\u0435 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0439\u0442\u0438 \u0432 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/blob\/master\/keps\/sig-node\/kubelet-resource-metrics-endpoint.md\">KEP<\/a><\/noindex>.<\/i><\/p>\n<p>Me\u0111u ostalim promjenama:<\/p>\n<ul>\n<li> Kubelet sada (jednom) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73802\">poku\u0161ava zaustaviti<\/a><\/noindex> kontejneri u nepoznatom stanju (unknown) prije operacija ponovnog pokretanja i brisanja.<\/li>\n<li> Kada koristite <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/podpreset\/\"><code>PodPresets<\/code><\/a><\/noindex> sada se init-kontejneru <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/71479\">dodaje<\/a><\/noindex> ista informacija kao i obi\u010dnom kontejneru.<\/li>\n<li> Kubelet <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73659\">po\u010deo koristiti<\/a><\/noindex> <code>usageNanoCores<\/code> iz CRI statisti\u010dkog pru\u017eatelja, a za \u010dvorove i kontejnere u Windowsu <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74788\">dodana<\/a><\/noindex> mre\u017ena statistika.<\/li>\n<li> Informacije o operativnom sustavu i arhitekturi sada se zapisuju u oznake <code>kubernetes.io\/os<\/code> i <code>kubernetes.io\/arch<\/code> objekata Node (prevedeno iz bete u GA).<\/li>\n<li> \u0412\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0443\u043a\u0430\u0437\u0430\u043d\u0438\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u043d\u043e\u0439 \u0433\u0440\u0443\u043f\u043f\u044b \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0434\u043b\u044f \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u0432 pod&#8217;\u0435 (<code>RunAsGroup<\/code>, uvedena je u <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/415349\/\">K8s 1.11<\/a><\/noindex>) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73007\">napredovala<\/a><\/noindex> do beta verzije (uklju\u010dena prema zadanim postavkama).<\/li>\n<li> du i find, kori\u0161teni u cAdvisoru, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74675\">zamijenjeni<\/a><\/noindex> Go implementacijama.<\/li>\n<\/ul>\n<p><\/p>\n<h2>CLI<\/h2>\n<p>\nU cli-runtime i kubectl <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74140\">dodana je<\/a><\/noindex> ozna\u010davanje -k za integraciju s <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\"><b>kustomize<\/b><\/a><\/noindex> (usput, njegov razvoj se sada vodi u zasebnom repozitoriju), tj. za obradu dodatnih YAML datoteka iz specijalnih direktorija kustomization (detalji o njihovom kori\u0161tenju vidi u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/blob\/master\/keps\/sig-cli\/kustomize-file-processing-integration.md\">KEP<\/a><\/noindex>):<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes 1.14: pregled glavnih noviteta\" src=\"\/wp-content\/uploads\/2019\/03\/e38550cfb642d81237aad4d87b9b3386.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Primjer jednostavnog kori\u0161tenja datoteke <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/glossary.md#kustomization\">kustomization<\/a><\/noindex> (mogu\u0107e je i slo\u017eenije kori\u0161tenje kustomize unutar <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/glossary.md#overlay\">overlays<\/a><\/noindex>)<\/i><\/p>\n<p>Osim toga:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/71651\">Dodana<\/a><\/noindex> nova naredba <code>kubectl create cronjob<\/code>, naziv koji govori sam za sebe.<\/li>\n<li> U <code>kubectl logs<\/code> sada je mogu\u0107e <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/67573\">kombinirati<\/a><\/noindex> oznake <code>-f<\/code> (<code>--follow<\/code> za streaming logova) i <code>-l<\/code> (<code>--selector<\/code> za label query).<\/li>\n<li> kubectl <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/72641\">nau\u010dili smo<\/a><\/noindex> kopirati datoteke, odabrane pomo\u0107u wild card.<\/li>\n<li> U timu <code>kubectl wait<\/code> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/70599\">dodali su<\/a><\/noindex> oznake <code>--all<\/code> za odabir svih resursa u prostoru imena odre\u0111enog tipa resursa.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Druge<\/h2>\n<p>\nStabilni (GA) status dobili su sljede\u0107e mogu\u0107nosti:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/pod-lifecycle\/#pod-readiness-gate\"><code>ReadinessGate<\/code><\/a><\/noindex>, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c\u044b\u0439 \u0432 \u0441\u043f\u0435\u0446\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 pod&#8217;\u0430 \u0434\u043b\u044f \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u0434\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0445 \u0443\u0441\u043b\u043e\u0432\u0438\u0439, \u0443\u0447\u0438\u0442\u044b\u0432\u0430\u0435\u043c\u044b\u0445 \u0432 \u0433\u043e\u0442\u043e\u0432\u043d\u043e\u0441\u0442\u0438 pod&#8217;\u0430;<\/li>\n<li> Podr\u0161ka za velike stranice (feature gate pod nazivom <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/tasks\/manage-hugepages\/scheduling-hugepages\/\"><code>HugePages<\/code><\/a><\/noindex>);<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/services-networking\/dns-pod-service\/#pod-s-dns-config\">CustomPodDNS<\/a><\/noindex>;<\/li>\n<li> PriorityClass API, <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/configuration\/pod-priority-preemption\/\">Prioritet pod-a &amp; Preemptivnost<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\nOstale promjene predstavljene u Kubernetes 1.14:<\/p>\n<ul>\n<li> RBAC politika prema zadanim postavkama vi\u0161e ne daje pristup API-ju <code>discovery<\/code> i <code>access-review<\/code> korisnicima bez autentifikacije <i>(unauthenticated)<\/i>.<\/li>\n<li> Slu\u017ebena podr\u0161ka za CoreDNS <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/69940\">osigurana<\/a><\/noindex> samo za Linux, stoga, prilikom kori\u0161tenja kubeadm za njegovo (CoreDNS) postavljanje u klasteru, \u010dvorovi moraju raditi samo u Linuxu (za ovo ograni\u010denje koriste se nodeSelectors).<\/li>\n<li> Defaultna konfiguracija CoreDNS sada <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73267\">koristi<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/coredns.io\/plugins\/forward\/\">forward plugin<\/a><\/noindex> umjesto proxy. Osim toga, u CoreDNS <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74137\">dodana<\/a><\/noindex> readinessProbe, \u043f\u0440\u0435\u0434\u043e\u0442\u0432\u0440\u0430\u0449\u0430\u044e\u0449\u0430\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0443 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043d\u0430 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0435 (\u043d\u0435 \u0433\u043e\u0442\u043e\u0432\u044b\u0435 \u043a \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u044e) pod&#8217;\u044b.<\/li>\n<li> U kubeadm, u fazama <code>init<\/code> ili <code>upload-certs<\/code>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73907\">postalo je mogu\u0107e<\/a><\/noindex> u\u010ditati certifikate potrebne za povezivanje novog control-plane-a na tajnu kubeadm-certs (koristi se zastavica <code>--experimental-upload-certs<\/code>).<\/li>\n<li> Za Windows instalacije dostupna je alfa verzija <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/689\">podr\u0161ke<\/a><\/noindex> gMSA (Group Managed Service Account) \u2014 posebne ra\u010dune u Active Directory-u koji se mogu koristiti i od kontejnera.<\/li>\n<li> Za GCE <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/70144\">aktivirali<\/a><\/noindex> mTLS-enkripciju izme\u0111u etcd-a i kube-apiserver-a.<\/li>\n<li> A\u017euriranja u kori\u0161tenom\/zavisnom softveru: Go 1.12.1, CSI 1.1, CoreDNS 1.3.1, podr\u0161ka za Docker 18.09 u kubeadm, a minimalna podr\u017eavana verzija Docker API-a postala je 1.26.<\/li>\n<\/ul>\n<p><\/p>\n<h2>P.S.<\/h2>\n<p>\nPro\u010ditajte i na na\u0161em blogu:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/432208\/\">Kubernetes 1.13: pregled glavnih noviteta<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/424331\/\">Kubernetes 1.12: pregled glavnih noviteta<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/415349\/\">Kubernetes 1.11: pregled glavnih noviteta<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/353114\/\">Kubernetes 1.10: pregled glavnih noviteta<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/445196\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042d\u0442\u043e\u0439 \u043d\u043e\u0447\u044c\u044e \u0441\u043e\u0441\u0442\u043e\u0438\u0442\u0441\u044f \u043e\u0447\u0435\u0440\u0435\u0434\u043d\u043e\u0439 \u0440\u0435\u043b\u0438\u0437 Kubernetes \u2014 1.14. \u041f\u043e \u0441\u043b\u043e\u0436\u0438\u0432\u0448\u0435\u0439\u0441\u044f \u0434\u043b\u044f \u043d\u0430\u0448\u0435\u0433\u043e \u0431\u043b\u043e\u0433\u0430 \u0442\u0440\u0430\u0434\u0438\u0446\u0438\u0438, \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u043e \u043a\u043b\u044e\u0447\u0435\u0432\u044b\u0445 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f\u0445 \u0432 \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u044d\u0442\u043e\u0433\u043e \u0437\u0430\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e Open Source-\u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430. \u0418\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044f, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u043d\u0430\u044f \u0434\u043b\u044f \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043a\u0438 \u044d\u0442\u043e\u0433\u043e \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430, \u0432\u0437\u044f\u0442\u0430 \u0438\u0437 \u0442\u0430\u0431\u043b\u0438\u0446\u044b Kubernetes enhancements tracking, CHANGELOG-1.14 \u0438 \u0441\u043e\u043e\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0445 issues, pull requests, Kubernetes Enhancement Proposals (KEP). \u041d\u0430\u0447\u043d\u0451\u043c \u0441 \u0432\u0430\u0436\u043d\u043e\u0433\u043e \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u043e\u0442 SIG cluster-lifecycle: \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-30272","post","type-post","status-publish","format-standard","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u042d\u0442\u043e\u0439 \u043d\u043e\u0447\u044c\u044e\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Kubernetes 1.14: \u043e\u0431\u0437\u043e\u0440 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u043d\u043e\u0432\u0448\u0435\u0441\u0442\u0432 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u042d\u0442\u043e\u0439 \u043d\u043e\u0447\u044c\u044e\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:34:36+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:34:36+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kubernetes 1.14: pregled glavnih noviteta | ProHoster","description":"Ove no\u0107i","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Kubernetes 1.14: \u043e\u0431\u0437\u043e\u0440 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u043d\u043e\u0432\u0448\u0435\u0441\u0442\u0432 | ProHoster","og:description":"\u042d\u0442\u043e\u0439 \u043d\u043e\u0447\u044c\u044e","og:url":"https:\/\/prohoster.info\/hr\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:34:36+00:00","article:modified_time":"2019-10-31T18:34:36+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"30272","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 00:28:09","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:37:28","updated":"2026-01-21 00:28:09","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/30272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=30272"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/30272\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=30272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=30272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=30272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}