{"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\/sq\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv","title":{"rendered":"Kubernetes 1.14: nj\u00eb p\u00ebrmbledhje e risive kryesore","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Kubernetes 1.14: nj\u00eb p\u00ebrmbledhje e risive kryesore\" src=\"\/wp-content\/uploads\/2019\/03\/8fb5be29668f55ec42d31eb47200b639.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSonte <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/sig-release\/tree\/master\/releases\/release-1.14#timeline\">do t\u00eb ndodhi<\/a><\/noindex> nj\u00eb version i ri i Kubernetes \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/sig-release\/tree\/master\/releases\/release-1.14\">1.14<\/a><\/noindex>. Sipas tradit\u00ebs s\u00eb vendosur p\u00ebr blogun ton\u00eb, ne po ndajm\u00eb ndryshimet ky\u00e7e n\u00eb k\u00ebt\u00eb version t\u00eb k\u00ebtij produkti t\u00eb shk\u00eblqyer Open Source.<\/p>\n<p>Informacioni i p\u00ebrdorur p\u00ebr p\u00ebrgatitjen e k\u00ebtij materiali \u00ebsht\u00eb marr\u00eb nga <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/spreadsheets\/u\/1\/d\/116X6E-lmDJG5UZPlqDAFw8hN9vS6SNY4qRNZ9fKtsMU\/edit#gid=0\">tabela e ndjekjes s\u00eb p\u00ebrmir\u00ebsimeve Kubernetes<\/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> dhe \u00e7\u00ebshtjet p\u00ebrkat\u00ebse, k\u00ebrkesat p\u00ebr t\u00ebrheqje, Propozimet e P\u00ebrmir\u00ebsimeve t\u00eb Kubernetes (KEP).<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Le t\u00eb fillojm\u00eb me nj\u00eb hyrje t\u00eb r\u00ebnd\u00ebsishme nga SIG cluster-lifecycle: <b>klaster\u00eb dinamik\u00eb t\u00eb q\u00ebndruesh\u00ebm<\/b> Kubernetes (dhe n\u00ebse e shpreh\u00ebm m\u00eb sakt\u00eb, at\u00ebher\u00eb realizimet HA me vet\u00eb-hostim) tani <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/357\">mund t\u00eb krijohen<\/a><\/noindex> duke p\u00ebrdorur komandat e njohura (n\u00eb kontekstin e klaster\u00ebve me nj\u00eb nyje) <code>kubeadm<\/code> (<code>procesi<\/code> dhe <code>join<\/code>). N\u00ebse e p\u00ebrmbledhim, at\u00ebher\u00eb p\u00ebr k\u00ebt\u00eb:<\/p>\n<ul>\n<li> \u00e7ertifikatat e p\u00ebrdorura nga klasteri transferohen n\u00eb sekretet;<\/li>\n<li> p\u00ebr t\u00eb mund\u00ebsuar p\u00ebrdorimin e klasterit etcd brenda klasterit K8s (dmth. duke u liruar nga var\u00ebsia ekzistuese e jashtme) \u00ebsht\u00eb angazhuar <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/coreos\/etcd-operator\">etcd-operator<\/a><\/noindex>;<\/li>\n<li> dokumentohen konfigurimet e rekomanduara p\u00ebr balancuesin e ngarkes\u00ebs jashtme q\u00eb siguron nj\u00eb konfigurim t\u00eb q\u00ebndruesh\u00ebm (n\u00eb t\u00eb ardhmen planifikohet t\u00eb mund t\u00eb hiqet edhe kjo var\u00ebsi, por jo n\u00eb k\u00ebt\u00eb etap\u00eb).<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes 1.14: nj\u00eb p\u00ebrmbledhje e risive kryesore\" src=\"\/wp-content\/uploads\/2019\/03\/0e82b7e8db1ad117dc87f68fa4669431.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Arkitektura HA-kllusterit Kubernetes, e cila \u00ebsht\u00eb krijuar me kubeadm<\/i><\/p>\n<p>Informacionet mbi implementimin mund t\u00eb gjenden n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/document\/d\/1P3oUJ_kdaRSTlGONujadGBpYegjn4RjBNZLHZ4zU7lI\/edit#\">propozimin p\u00ebr dizajn<\/a><\/noindex>. Kjo karakteristik\u00eb ishte me t\u00eb v\u00ebrtet\u00eb e shum\u00ebpritur: versione alfa ishte e pritur q\u00eb t\u00eb dilte n\u00eb K8s 1.9, por doli vet\u00ebm tani.<\/p>\n<h2>API<\/h2>\n<p>\nEkipa <code>apliko<\/code> dhe n\u00eb p\u00ebrgjith\u00ebsi <b>menaxhimi deklarativ i objekteve<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/555\">u nxorr\u00ebn<\/a><\/noindex> nga <code>kubectl<\/code> n\u00eb apiserver. Vet\u00eb zhvilluesit e shpjegojn\u00eb shkurtimisht vendimin e tyre me t\u00eb v\u00ebrtet\u00eb se <code>kubectl aplikoni<\/code> \u00ebsht\u00eb nj\u00eb pjes\u00eb themelore e pun\u00ebs me konfigurimet n\u00eb Kubernetes, megjithat\u00eb \"\u00ebsht\u00eb e mbushur me bugs dhe \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb rregullohet\", p\u00ebr shkak t\u00eb s\u00eb cil\u00ebs kjo funksionalitet duhet t\u00eb sillet n\u00eb nj\u00eb form\u00eb normale dhe t\u00eb kaloj\u00eb n\u00eb kontrollin e planeve. Shembuj t\u00eb thjesht\u00eb dhe t\u00eb qart\u00eb t\u00eb problemeve aktuale jan\u00eb:<\/p>\n<p><img decoding=\"async\" alt=\"Kubernetes 1.14: nj\u00eb p\u00ebrmbledhje e risive kryesore\" src=\"\/wp-content\/uploads\/2019\/03\/379b0d830491bbb0e7ac3c3ccfff71c4.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDetajet mbi implementimin - n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/blob\/master\/keps\/sig-api-machinery\/0006-apply.md\">KEP<\/a><\/noindex>. Gatishm\u00ebria aktuale - versioni alfa (promovimi n\u00eb beta \u00ebsht\u00eb planifikuar p\u00ebr versionin e ardhsh\u00ebm t\u00eb Kubernetes).<\/p>\n<p>N\u00eb versionin alfa \u00ebsht\u00eb b\u00ebr\u00eb e disponueshme <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/692\">mund\u00ebsia<\/a><\/noindex> p\u00ebrdorimi i skem\u00ebs OpenAPI v3 p\u00ebr <b>krijimin dhe publikimin e dokumentacionit OpenAPI p\u00ebr CustomResources<\/b> (CR), q\u00eb p\u00ebrdoren p\u00ebr validimin (n\u00eb an\u00ebn e serverit) e burimeve K8s, t\u00eb p\u00ebrcaktuar nga p\u00ebrdoruesi (CustomResourceDefinition, CRD). Publikimi i OpenAPI p\u00ebr CRD lejon klient\u00ebt (p.sh., <code>kubectl<\/code>) t\u00eb kryejn\u00eb validim n\u00eb an\u00ebn e tyre (n\u00eb kuad\u00ebr t\u00eb <code>kubectl krijo<\/code> dhe <code>kubectl aplikoni<\/code>) dhe t\u00eb jepni dokumentacionin rreth skem\u00ebs (<code>kubectl shpjego<\/code>). Detajet \u2014 n\u00eb <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>Log\u00ebt q\u00eb ekzistonin m\u00eb par\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74837\">tani hapen<\/a><\/noindex> me flamur <code>O_APPEND<\/code> ([ <code>O_TRUNC<\/code>) p\u00ebr t\u00eb evituar humbjen e log\u00ebve n\u00eb disa situata dhe p\u00ebr leht\u00ebsim t\u00eb truncate-t t\u00eb log\u00ebve nga utilitetet e jashtme p\u00ebr rotacion.<\/p>\n<p>Gjithashtu, n\u00eb kontekstin e API-s\u00eb s\u00eb Kubernetes mund t\u00eb theksohet se n\u00eb <code>PodSandbox<\/code> dhe <code>PodSandboxStatus<\/code> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73833\">shtuar<\/a><\/noindex> fusha <code>runtime_handler<\/code> p\u00ebr t\u00eb mbajtur informacionin n\u00eb lidhje me <code>RuntimeClass<\/code> n\u00eb pod&#8217;in (lexoni m\u00eb shum\u00eb p\u00ebr t\u00eb n\u00eb tekstin mbi <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/424331\/\">\u00c7lirimi i Kubernetes 1.12<\/a><\/noindex>, ku ky klas\u00eb u shfaq si version alfa), dhe n\u00eb Admission Webhooks <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74998\">\u00ebsht\u00eb realizuar<\/a><\/noindex> mund\u00ebsia p\u00ebr t\u00eb p\u00ebrcaktuar cilat versione <code>AdmissionReview<\/code> ata mb\u00ebshtesin. P\u00ebrfundimisht, n\u00eb rregullat e Admission Webhooks tani <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74477\">mund t\u00eb kufizojn\u00eb<\/a><\/noindex> shkall\u00ebt e p\u00ebrdorimit me namespaces dhe kufijt\u00eb e klastra.<\/p>\n<h2>Kasa<\/h2>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/storage\/volumes\/#local\"><code><b>VOLUMET E Q\u00cbNDROSHME T\u00cb D\u00cbRGESAVE<\/b><\/code><\/a><\/noindex>, q\u00eb pat\u00ebn status beta q\u00eb nga l\u00ebshimi <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\">u shpall\u00ebn<\/a><\/noindex> t\u00eb stabilizuar (GA): ky feature gate nuk ndalet m\u00eb dhe do t\u00eb hiqet n\u00eb Kubernetes 1.17.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/559\">Mund\u00ebsia<\/a><\/noindex> p\u00ebrdorimi i variablave t\u00eb mjedisit t\u00eb ashtuquajtur <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> (p.sh., emri i pod&#8217;it) p\u00ebr emrat e dosjeve q\u00eb jan\u00eb montuar si <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/storage\/volumes\/#using-subpath\"><code>subPath<\/code><\/a><\/noindex>, zhvilloi\u2014n\u00eb form\u00ebn e nj\u00eb fushe t\u00eb re <code>subPathExpr<\/code>, me ndihm\u00ebn e t\u00eb cilit tani p\u00ebrcaktohet emri i nevojsh\u00ebm i direktoriumit. Funksionaliteti fillimisht u shfaq n\u00eb Kubernetes 1.11, por mbeti n\u00eb statusin alfa deri n\u00eb 1.14.<\/p>\n<p>Si n\u00eb versionin e kaluar t\u00eb Kubernetes, shum\u00eb ndryshime t\u00eb r\u00ebnd\u00ebsishme jan\u00eb paraqitur p\u00ebr CSI (Container Storage Interface) t\u00eb zhvilluar aktivisht:<\/p>\n<h3>CSI<\/h3>\n<p>\nB\u00ebri t\u00eb mundur (n\u00eb kuad\u00ebr t\u00eb versionit alfa) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/556\">mb\u00ebshtetje<\/a><\/noindex> <b>ndryshimin e madh\u00ebsis\u00eb p\u00ebr volumin CSI<\/b>. P\u00ebr ta p\u00ebrdorur at\u00eb, do t\u00eb nevojitet aktivizimi i porteve t\u00eb funksioneve t\u00eb quajtura <code>ExpandCSIVolumes<\/code>, si dhe mb\u00ebshtetje p\u00ebr k\u00ebt\u00eb operacion n\u00eb drejtuesin e ve\u00e7ant\u00eb t\u00eb CSI.<\/p>\n<p>Nj\u00eb tjet\u00ebr funksionalitet p\u00ebr CSI n\u00eb versionin alfa \u00ebsht\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/596\">mund\u00ebsia<\/a><\/noindex> t\u00eb referohen direkt (dmth. pa p\u00ebrdorimin e PV\/PVC) n\u00eb volumet CSI n\u00eb kuad\u00ebr t\u00eb specifikimit t\u00eb pod&#8217;eve. Kjo <b>heq kufizimin n\u00eb p\u00ebrdorimin e CSI si depo t\u00eb larg\u00ebta ekskluzivisht<\/b>, duke hapur dyert p\u00ebr ta n\u00eb bot\u00ebn e <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes-csi.github.io\/docs\/ephemeral-local-volumes.html\">volumene lokale ephemeral<\/a><\/noindex>. P\u00ebr ta p\u00ebrdorur (<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/vladimirvivien\/kubernetes.github.io\/blob\/b78107abfdb2b5877973b84062d93cdf98ef1b9c\/content\/en\/docs\/concepts\/storage\/volumes.md#csi-ephemeral-volumes\">shembulli nga dokumenti<\/a><\/noindex>) nevojitet aktivizimi i <code>CSIInlineVolume<\/code> portes s\u00eb funksioneve.<\/p>\n<p>Ka progress i \u00ebsht\u00eb b\u00ebr\u00eb edhe n\u00eb \"brendin\u00eb\" e Kubernetes, q\u00eb lidhen me CSI, t\u00eb cilat nuk jan\u00eb aq t\u00eb dukshme p\u00ebr p\u00ebrdoruesit e fundit (administrator\u00ebt e sistemeve)... N\u00eb k\u00ebt\u00eb moment, zhvilluesit jan\u00eb t\u00eb detyruar t\u00eb mb\u00ebshtesin dy versione t\u00eb \u00e7do plugin ruajtjeje: nj\u00ebr\u00ebn - \"si m\u00eb par\u00eb\", brenda kodit K8s (in-tree), dhe tjetr\u00ebn - n\u00eb kuad\u00ebr t\u00eb CSI t\u00eb ri. <i>(lexoni m\u00eb shum\u00eb p\u00ebr t\u00eb, p\u00ebr shembull, n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/424211\/\">k\u00ebtu<\/a><\/noindex>)<\/i>. Kjo shkakton shqet\u00ebsime t\u00eb qarta q\u00eb duhet t\u00eb adresohen nd\u00ebrsa stabilizohet CSI si i till\u00eb. Thjesht t\u00eb merrni dhe t\u00eb shpallni API-t\u00eb e brendshme (in-tree) si t\u00eb vjetra (deprecated) nuk \u00ebsht\u00eb e mundur p\u00ebr shkak t\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/reference\/using-api\/deprecation-policy\/#deprecating-parts-of-the-api\">politikat p\u00ebrkat\u00ebse t\u00eb Kubernetesit.<\/a><\/noindex>.<\/p>\n<p>E gjith\u00eb kjo ka \u00e7uar n\u00eb arritjen e versioneve alfa <b><noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/625\">procesi i migrimit<\/a><\/noindex> t\u00eb kodit t\u00eb brendsh\u00ebm t\u00eb plugineve.<\/b>, realizuar si in-tree, n\u00eb plugin-e CSI, duke e b\u00ebr\u00eb k\u00ebshtu q\u00eb shqet\u00ebsimet e zhvilluesve t\u00eb reduktohen n\u00eb mb\u00ebshtetje t\u00eb nj\u00eb versioni t\u00eb vet\u00ebm t\u00eb plugins-eve t\u00eb tyre, nd\u00ebrsa kompatibiliteti me API-t\u00eb e vjetra do t\u00eb ruhet dhe ato do t\u00eb mund t\u00eb shpallen t\u00eb vjetruara sipas skenarit t\u00eb zakonsh\u00ebm. Pritet q\u00eb n\u00eb versionin e ardhsh\u00ebm t\u00eb Kubernetes (1.15) t\u00eb b\u00ebhet migrimi i t\u00eb gjith\u00eb plugin-eve t\u00eb ofruesve t\u00eb cloud, implementimi do t\u00eb marr\u00eb statusin beta dhe do t\u00eb aktivizohet n\u00eb instalimet K8s si standard. Detajet mund t\u00eb shihen n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/community\/blob\/master\/contributors\/design-proposals\/storage\/csi-migration.md\">propozimin p\u00ebr dizajn<\/a><\/noindex>. Pasoj\u00eb e k\u00ebsaj migrimi gjithashtu ishte <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74544\">refuzimi<\/a><\/noindex> i kufizimeve p\u00ebr volumet e p\u00ebrcaktuara nga ofruesit e caktuar t\u00eb cloud (AWS, Azure, GCE, Cinder).<\/p>\n<p>P\u00ebrve\u00e7 k\u00ebsaj, mb\u00ebshtetja p\u00ebr pajisjet bllokuese me CSI (<code>CSIBlockVolume<\/code>) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74909\">u kalua<\/a><\/noindex> n\u00eb versionin beta.<\/p>\n<h2>Nodet \/ Kubelet<\/h2>\n<p>\nVersioni alfa i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/727\">endpoint-it t\u00eb ri<\/a><\/noindex> n\u00eb Kubelet, i destinuar p\u00ebr <b>raportimin e metrikeve p\u00ebr burimet kryesore<\/b>. N\u00eb p\u00ebrgjith\u00ebsi, n\u00ebse m\u00eb par\u00eb Kubelet merrte statistikat p\u00ebr p\u00ebrdorimin e konteiner\u00ebve nga cAdvisor, tani k\u00ebto t\u00eb dh\u00ebna vijn\u00eb nga ambienti ekzekutiv i konteinerit n\u00ebp\u00ebrmjet CRI (Container Runtime Interface), megjithat\u00eb ruhet edhe p\u00ebrputhshm\u00ebria p\u00ebr t\u00eb punuar me versionet e vjetra t\u00eb Docker. M\u00eb par\u00eb, statistikat e mbledhura n\u00eb Kubelet jepeshin p\u00ebrmes REST API, por tani p\u00ebr k\u00ebt\u00eb p\u00ebrdoret nj\u00eb endpoint i vendosur n\u00eb adres\u00ebn <code>\/metrics\/resource\/v1alpha1<\/code>. Strategjia afatgjat\u00eb e zhvilluesve <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/issues\/68522\">\u00ebsht\u00eb<\/a><\/noindex> t\u00eb minimizoj\u00eb grupin e metrikave q\u00eb ofrohen nga Kubelet. <i>Nga ana tjet\u00ebr, k\u00ebto metrika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/pull\/726\">tani quhen<\/a><\/noindex> jo \u00abcore metrics\u00bb, por \u00abresource metrics\u00bb, dhe p\u00ebrshkruhen si \u00abfirst-class resources, such as cpu, and memory\u00bb.<\/i><\/p>\n<p>Nj\u00eb nuanc\u00eb interesante: megjith\u00eb avantazhin e duksh\u00ebm n\u00eb performanc\u00eb t\u00eb endpoint-it gRPC n\u00eb krahasim me rastet e ndryshme t\u00eb p\u00ebrdorimit t\u00eb formatit Prometheus <i>(rezultati i nj\u00eb nga benchmark&#8217;et shiko m\u00eb posht\u00eb)<\/i>, autor\u00ebt preferuan formatin tekstual t\u00eb Prometheus p\u00ebr shkak t\u00eb lidershipit t\u00eb duksh\u00ebm t\u00eb k\u00ebtij sistemi monitorimi n\u00eb komunitet.<\/p>\n<blockquote><p><i>\u00abgRPC nuk \u00ebsht\u00eb n\u00eb p\u00ebrputhje me linjat kryesore t\u00eb monitorimit. Endpoint-i do t\u00eb jet\u00eb i dobish\u00ebm vet\u00ebm p\u00ebr t\u00eb d\u00ebrguar metrika n\u00eb Metrics Server ose komponent\u00ebt e monitorimit q\u00eb integrohen direkt me t\u00eb. Kur p\u00ebrdoret caching n\u00eb Metrics Server, performanca e formatit t\u00eb tekstit Prometheus \u00ebsht\u00eb m\u00eb e lart\u00eb. <b>mjaft e mir\u00eb<\/b> p\u00ebr ne, p\u00ebr t\u00eb preferuar Prometheus n\u00eb vend t\u00eb gRPC, duke marr\u00eb parasysh p\u00ebrhapjen e gjer\u00eb t\u00eb Prometheus n\u00eb komunitet. Kur formati OpenMetrics t\u00eb b\u00ebhet m\u00eb stabil, ne mund t\u00eb arrijm\u00eb n\u00eb performanc\u00ebn e gRPC me formatin e bazuar n\u00eb proto.\u00bb<\/i><\/p><\/blockquote>\n<p>\n<img decoding=\"async\" alt=\"Kubernetes 1.14: nj\u00eb p\u00ebrmbledhje e risive kryesore\" src=\"\/wp-content\/uploads\/2019\/03\/ad7e45b61fc4676a2df3c2d33d5688b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Nj\u00eb nga testet krahasuese t\u00eb performanc\u00ebs s\u00eb p\u00ebrdorimit t\u00eb formateve gRPC dhe Prometheus n\u00eb endpoint&#8217;in e ri Kubelet p\u00ebr metrika. M\u00eb shum\u00eb grafik\u00eb dhe detaje t\u00eb tjera mund t\u00eb gjenden n\u00eb <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>Nd\u00ebr ndryshimet e tjera:<\/p>\n<ul>\n<li> Kubelet tani (nj\u00eb her\u00eb) <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73802\">p\u00ebrpiqet t\u00eb ndal\u00eb<\/a><\/noindex> konteiner\u00ebt n\u00eb gjendje t\u00eb panjohur (unknown) p\u00ebrpara operacioneve t\u00eb rinisjes dhe fshirjes.<\/li>\n<li> Kur p\u00ebrdoret <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/workloads\/pods\/podpreset\/\"><code>PodPresets<\/code><\/a><\/noindex> tani init-konteineri <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/71479\">shtohet<\/a><\/noindex> ka t\u00eb nj\u00ebjt\u00ebn informacion si konteineri normal.<\/li>\n<li> Kubelet <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73659\">ka filluar t\u00eb p\u00ebrdor\u00eb<\/a><\/noindex> <code>usageNanoCores<\/code> nga ofruesi i statistikave CRI, dhe p\u00ebr nodet dhe konteiner\u00ebt n\u00eb Windows <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74788\">shtuar<\/a><\/noindex> statistikat e rrjetit.<\/li>\n<li> Informacion mbi sistemin operativ dhe arkitektur\u00ebn tani regjistrohet n\u00eb etiketa <code>kubernetes.io\/os<\/code> dhe <code>kubernetes.io\/arch<\/code> objekteve Node (e kaluar nga beta n\u00eb GA).<\/li>\n<li> Mund\u00ebsia p\u00ebr t\u00eb p\u00ebrcaktuar nj\u00eb grup t\u00eb caktuar p\u00ebrdoruesish p\u00ebr kontejner\u00ebt n\u00eb pod&#8217;in (<code>RunAsGroup<\/code>, \u00ebsht\u00eb prezantuar n\u00eb <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\">ka p\u00ebrparuar<\/a><\/noindex> n\u00eb versionin beta (aktivizuar nga e para).<\/li>\n<li> du dhe find, t\u00eb p\u00ebrdorura n\u00eb cAdvisor, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74675\">u z\u00ebvend\u00ebsuan<\/a><\/noindex> me implementime n\u00eb Go.<\/li>\n<\/ul>\n<p><\/p>\n<h2>CLI<\/h2>\n<p>\nN\u00eb cli-runtime dhe kubectl <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74140\">u shtua<\/a><\/noindex> flaga -k p\u00ebr integrim me <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\"><b>kustomize<\/b><\/a><\/noindex> (p\u00ebr m\u00eb tep\u00ebr, zhvillimi i tij tani \u00ebsht\u00eb n\u00eb nj\u00eb depozit\u00eb t\u00eb ve\u00e7ant\u00eb), dmth. p\u00ebr procesimin e skedar\u00ebve YAML shtes\u00eb nga direktorive t\u00eb ve\u00e7anta kustomizimi (detajet mbi p\u00ebrdorimin e tyre shihni n\u00eb <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: nj\u00eb p\u00ebrmbledhje e risive kryesore\" src=\"\/wp-content\/uploads\/2019\/03\/e38550cfb642d81237aad4d87b9b3386.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Shembulli i p\u00ebrdorimit t\u00eb thjesht\u00eb t\u00eb skedarit <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/glossary.md#kustomization\">kustomization<\/a><\/noindex> (nd\u00ebrsa mund t\u00eb ket\u00eb aplikime m\u00eb t\u00eb komplikuara kustomize brenda <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kustomize\/blob\/master\/docs\/glossary.md#overlay\">overlays<\/a><\/noindex>)<\/i><\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/71651\">Shtuar<\/a><\/noindex> komanda e re <code>kubectl create cronjob<\/code>, emri i s\u00eb cil\u00ebs flet p\u00ebr vete.<\/li>\n<li> N\u00eb <code>kubectl logs<\/code> tani mund t\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/67573\">kombinoj\u00eb<\/a><\/noindex> flagat <code>-f<\/code> (<code>--follow<\/code> p\u00ebr rrjedhjen e logeve) dhe <code>-l<\/code> (<code>--selector<\/code> p\u00ebr pyetjen e etiketimeve).<\/li>\n<li> kubectl <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/72641\">m\u00ebsuam<\/a><\/noindex> t\u00eb kopjojm\u00eb skedar\u00ebt, t\u00eb p\u00ebrzgjedhur me ndihm\u00ebn e wild card.<\/li>\n<li> N\u00eb komand\u00ebn <code>kubectl wait<\/code> <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/70599\">u shtua<\/a><\/noindex> flaga <code>--all<\/code> p\u00ebr t\u00eb p\u00ebrzgjedhur t\u00eb gjitha burimet n\u00eb hap\u00ebsir\u00ebn em\u00ebrtuese t\u00eb llojit t\u00eb caktuar t\u00eb burimeve.<\/li>\n<\/ul>\n<p><\/p>\n<h2>T\u00eb tjera<\/h2>\n<p>\nStatusi i q\u00ebndruesh\u00ebm (GA) u dha mund\u00ebsive t\u00eb m\u00ebposhtme:<\/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>, i p\u00ebrdorur n\u00eb specifikimin e pod&#8217;it p\u00ebr t\u00eb p\u00ebrcaktuar kushte t\u00eb tjera q\u00eb merren parasysh n\u00eb gatishm\u00ebrin\u00eb e pod&#8217;it;<\/li>\n<li> Mb\u00ebshtetje p\u00ebr faqe t\u00eb m\u00ebdha (porti i quajtur <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> APIs e klas\u00ebs s\u00eb prioritetit, <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/configuration\/pod-priority-preemption\/\">Prioriteti i Pod dhe Parandalimi<\/a><\/noindex>.<\/li>\n<\/ul>\n<p>\nNdryshime t\u00eb tjera t\u00eb paraqitura n\u00eb Kubernetes 1.14:<\/p>\n<ul>\n<li> Politika RBAC p\u00ebr parazgjedhje nuk jep m\u00eb akses n\u00eb API <code>discovery<\/code> dhe <code>access-review<\/code> p\u00ebrdoruesve pa autentifikim <i>(unauthenticated)<\/i>.<\/li>\n<li> Mb\u00ebshtetje zyrtare p\u00ebr CoreDNS <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/69940\">sigurohet<\/a><\/noindex> vet\u00ebm p\u00ebr Linux, k\u00ebshtu q\u00eb kur p\u00ebrdorni kubeadm p\u00ebr implementimin e tij (CoreDNS) n\u00eb klaster, nyjet duhet t\u00eb funksionojn\u00eb vet\u00ebm n\u00eb Linux (p\u00ebr k\u00ebt\u00eb kufizim p\u00ebrdoren nodeSelectors).<\/li>\n<li> Konfigurimi i CoreDNS p\u00ebr parazgjedhje tani <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73267\">p\u00ebrdor<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/coredns.io\/plugins\/forward\/\">pluginin forward<\/a><\/noindex> n\u00eb vend t\u00eb proxy. P\u00ebr m\u00eb tep\u00ebr, n\u00eb CoreDNS <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/74137\">shtuar<\/a><\/noindex> readinessProbe, e cila parandalon balancimin e ngarkes\u00ebs n\u00eb p\u00ebrkat\u00ebsit\u00eb (t\u00eb pa gatshme p\u00ebr sh\u00ebrbim) pod&#8217;et.<\/li>\n<li> N\u00eb kubeadm, n\u00eb fazat <code>procesi<\/code> ose <code>upload-certs<\/code>, <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/73907\">ka b\u00ebr\u00eb t\u00eb mundur<\/a><\/noindex> ngarkimin e certifikatave, t\u00eb k\u00ebrkuara p\u00ebr lidhjen e nj\u00eb control-plane t\u00eb ri me sekretin kubeadm-certs (p\u00ebrdoret flags <code>--experimental-upload-certs<\/code>).<\/li>\n<li> P\u00ebr instalimet Windows ka dal\u00eb nj\u00eb version alfa <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/enhancements\/issues\/689\">mb\u00ebshtetje<\/a><\/noindex> gMSA (Group Managed Service Account) \u2014 llogari t\u00eb ve\u00e7anta n\u00eb Active Directory, q\u00eb mund t\u00eb p\u00ebrdoren edhe nga konteineret.<\/li>\n<li> P\u00ebr GCE <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/pull\/70144\">aktivizuar<\/a><\/noindex> kriptimi mTLS midis etcd dhe kube-apiserver.<\/li>\n<li> P\u00ebrdit\u00ebsimet n\u00eb software-n e p\u00ebrdorur\/zbatuar: Go 1.12.1, CSI 1.1, CoreDNS 1.3.1, mb\u00ebshtetje p\u00ebr Docker 18.09 n\u00eb kubeadm, nd\u00ebrsa versioni minimal i mb\u00ebshtetur i API Docker tani \u00ebsht\u00eb 1.26.<\/li>\n<\/ul>\n<p><\/p>\n<h2>P.S.<\/h2>\n<p>\nLexoni gjithashtu n\u00eb blogun ton\u00eb:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/432208\/\">Kubernetes 1.13: p\u00ebrmbledhje e risive kryesore<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/424331\/\">Kubernetes 1.12: p\u00ebrmbledhje e risive kryesore<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/415349\/\">Kubernetes 1.11: p\u00ebrmbledhje e risive kryesore<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/flant\/blog\/353114\/\">Kubernetes 1.10: p\u00ebrmbledhje e risive kryesore<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Burimi: <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 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"\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\" \/>\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\/sq\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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 \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\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/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: p\u00ebrmbledhje e risive kryesore | ProHoster","description":"Sonte do t\u00eb ndodh\u00eb nj\u00eb tjet\u00ebr version i Kubernetes \u2014 1.14. Sipas tradit\u00ebs son\u00eb p\u00ebr k\u00ebt\u00eb blog, do t'ju informojm\u00eb p\u00ebr ndryshimet kryesore n\u00eb k\u00ebt\u00eb version t\u00eb mrekulluesh\u00ebm Open Source. Informacioni i p\u00ebrdorur p\u00ebr p\u00ebrgatitjen e k\u00ebtij materiali \u00ebsht\u00eb marr\u00eb nga tabela e ndjekjes s\u00eb p\u00ebrmir\u00ebsimeve t\u00eb Kubernetes, CHANGELOG-1.14 dhe \u00e7\u00ebshtjet p\u00ebrkat\u00ebse, k\u00ebrkesat p\u00ebr t\u00ebrheqje, Propozitat p\u00ebr P\u00ebrmir\u00ebsimin e Kubernetes (KEP). Le t\u00eb fillojm\u00eb me nj\u00eb hyrje t\u00eb r\u00ebnd\u00ebsishme nga SIG cluster-lifecycle: dinamike","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/kubernetes-1-14-obzor-osnovnyh-novshestv","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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 \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","og:url":"https:\/\/prohoster.info\/sq\/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"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/30272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=30272"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/30272\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=30272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=30272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=30272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}