{"id":39016,"date":"2019-10-31T22:27:21","date_gmt":"2019-10-31T19:27:21","guid":{"rendered":"https:\/\/prohoster.info\/blog\/7-luchshih-praktik-po-ekspluatatsii-kontejnerov-po-versii-google\/"},"modified":"2019-10-31T22:27:21","modified_gmt":"2019-10-31T19:27:21","slug":"7-luchshih-praktik-po-ekspluatatsii-kontejnerov-po-versii-google","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/7-luchshih-praktik-po-ekspluatatsii-kontejnerov-po-versii-google","title":{"rendered":"7 praktikat m\u00eb t\u00eb mira p\u00ebr operimin e konteiner\u00ebve sipas Google","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sh\u00ebn. p\u00ebrk.<\/b>: Autori i artikullit origjinal \u2014 Th\u00e9o Chamley, arkitekt i zgjidhjeve cloud n\u00eb Google. N\u00eb k\u00ebt\u00eb publikim p\u00ebr blogun Google Cloud, ai paraqiti nj\u00eb p\u00ebrmbledhje t\u00eb shkurt\u00ebr nga nj\u00eb udh\u00ebzues m\u00eb i detajuar i kompanis\u00eb s\u00eb tij t\u00eb quajtur \u00abPraktikat m\u00eb t\u00eb Mira p\u00ebr Operimin e Kontejner\u00ebve<\/a><\/noindex>\u00bb. N\u00eb t\u00eb, specialist\u00ebt e Google kan\u00eb mbledhur praktikat m\u00eb t\u00eb mira p\u00ebr p\u00ebrdorimin e kontejner\u00ebve n\u00eb kontekstin e p\u00ebrdorimit t\u00eb Google Kubernetes Engine dhe m\u00eb shum\u00eb, duke prekur nj\u00eb gam\u00eb t\u00eb gjer\u00eb temash: nga siguria te monitorimi dhe regjistrimi. Pra, cilat jan\u00eb praktikat m\u00eb t\u00eb r\u00ebnd\u00ebsishme n\u00eb pun\u00ebn me kontejner\u00ebt sipas mendimit t\u00eb Google?<\/i><\/p>\n

\"7<\/a><\/noindex><\/p>\n

Kubernetes Engine<\/a><\/noindex> (sh\u00ebrbimi i bazuar n\u00eb Kubernetes p\u00ebr ekzekutimin e aplikacioneve t\u00eb kontejnerizuara n\u00eb Google Cloud \u2014 sh\u00ebn. transl.<\/b>)<\/i> \u2014 \u00ebsht\u00eb nj\u00eb nga m\u00ebnyrat m\u00eb t\u00eb mira p\u00ebr t\u00eb ekzekutuar ngarkesa pune q\u00eb kan\u00eb nevoj\u00eb p\u00ebr skalim. Kubernetes<\/a><\/noindex> do t\u00eb siguroj\u00eb funksionimin pa probleme t\u00eb shumic\u00ebs s\u00eb aplikacioneve, n\u00ebse ato jan\u00eb t\u00eb kontejnerizuara. Por n\u00ebse d\u00ebshiron q\u00eb aplikacioni t\u00eb menaxhohet leht\u00ebsisht dhe t\u00eb p\u00ebrfitosh nga t\u00eb gjitha p\u00ebrfitimet e Kubernetes, duhet t\u00eb ndjek\u00ebsh praktikat m\u00eb t\u00eb mira. Ato do t\u00eb thjeshtojn\u00eb operimin e aplikacionit, monitorimin dhe shkall\u00ebzimin e tij, si dhe do t\u00eb rrisin sigurin\u00eb.<\/p>\n

N\u00eb k\u00ebt\u00eb artikull do t\u00eb shqyrtojm\u00eb nj\u00eb list\u00eb t\u00eb asaj q\u00eb duhet t\u00eb dini dhe t\u00eb b\u00ebni p\u00ebr funksionimin efikas t\u00eb kontejner\u00ebve n\u00eb Kubernetes. Ata q\u00eb d\u00ebshirojn\u00eb t\u00eb thellohen n\u00eb detaje duhet t\u00eb lexojn\u00eb materialin Praktikat m\u00eb t\u00eb Mira p\u00ebr Operimin e Kontejner\u00ebve<\/a><\/noindex>, si dhe t\u00eb kushtojn\u00eb v\u00ebmendje postit ton\u00eb m\u00eb t\u00eb hersh\u00ebm<\/a><\/noindex> n\u00eb lidhje me nd\u00ebrtimin e kontejner\u00ebve.<\/p>\n

1. P\u00ebrdorni mekanizmat native t\u00eb kontejner\u00ebve p\u00ebr regjistrimin e logeve<\/h2>\n

\nN\u00ebse aplikacioni ekzekutohet n\u00eb nj\u00eb klaster Kubernetes, p\u00ebr loge nuk \u00ebsht\u00eb nevoja p\u00ebr shum\u00eb. Nj\u00eb sistem i centralizuar i regjistrimit t\u00eb logeve ndoshta \u00ebsht\u00eb tashm\u00eb i integruar n\u00eb klasterin q\u00eb p\u00ebrdorni. N\u00eb rastin e p\u00ebrdorimit t\u00eb Kubernetes Engine, kjo menaxhohet nga Stackdriver Logging<\/a><\/noindex>. (Sh\u00ebn. p\u00ebrk.<\/b>: dhe p\u00ebr nj\u00eb instalim t\u00eb vet\u00eb-kontrolluar t\u00eb Kubernetes, rekomandojm\u00eb t\u00eb shqyrtoni zgjidhjen ton\u00eb me kod burimor \u2014 loghouse<\/a><\/noindex>.)<\/i> Mos i kompliko vetes jet\u00ebn dhe p\u00ebrdor mekanizmat native t\u00eb regjistrimit t\u00eb logeve t\u00eb kontejner\u00ebve. Shkruani loget n\u00eb stdout dhe stderr \u2014 ato do t\u00eb merren automatikisht, ruhen dhe indeksohen.<\/p>\n

N\u00ebse d\u00ebshironi, mund t\u00eb shkruani gjithashtu loge n\u00eb formatin JSON<\/a><\/noindex>. Ky qasje do t\u00eb lejoj\u00eb shtimin e t\u00eb dh\u00ebnave meta. Dhe po me to, n\u00eb Stackdriver Logging do t\u00eb shfaqet mund\u00ebsia p\u00ebr t\u00eb k\u00ebrkuar n\u00eb loget duke p\u00ebrdorur k\u00ebto metadatat.<\/p>\n

2. Sigurohuni q\u00eb kontejner\u00ebt t\u00eb jen\u00eb stateless dhe immutable<\/h2>\n

\nP\u00ebr funksionimin e sakt\u00eb t\u00eb kontejner\u00ebve n\u00eb klasterin Kubernetes, ata duhet t\u00eb jen\u00eb stateless dhe immutable. Kur k\u00ebto kushte p\u00ebrmbushen, Kubernetes do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb kryej\u00eb pun\u00ebn e tij, duke krijuar dhe shkat\u00ebrruar entitetet e aplikacionit kur dhe ku \u00ebsht\u00eb e nevojshme.<\/p>\n

Stateless<\/i> do t\u00eb thot\u00eb q\u00eb \u00e7do gjendje (t\u00eb dh\u00ebnat e vazhdueshme t\u00eb \u00e7do lloji) ruhet jasht\u00eb kontejnerit. P\u00ebr k\u00ebt\u00eb, n\u00eb var\u00ebsi t\u00eb nevojave, mund t\u00eb angazhohen lloje t\u00eb ndryshme t\u00eb ruajtjes s\u00eb jashtme: Ruajtja n\u00eb Cloud<\/a><\/noindex>, Disqe t\u00eb Q\u00ebndruesh\u00ebm<\/a><\/noindex>, Redis<\/a><\/noindex>, Cloud SQL<\/a><\/noindex> ose baza t\u00eb tjera t\u00eb dh\u00ebnash t\u00eb menaxhuara. (Sh\u00ebn. p\u00ebrk.<\/b>: M\u00eb shum\u00eb rreth k\u00ebsaj lexoni gjithashtu n\u00eb artikullin ton\u00eb \"Operator\u00ebt p\u00ebr Kubernetes: si t\u00eb nisni aplikacione stateful<\/a><\/noindex>\u00bb.)<\/i><\/p>\n

Immutable<\/i> do t\u00eb thot\u00eb q\u00eb kontejneri nuk do t\u00eb modifikohet gjat\u00eb jet\u00ebs s\u00eb tij: asnj\u00eb p\u00ebrdit\u00ebsim, patch, ndryshime n\u00eb konfigurim. N\u00ebse ju nevojitet t\u00eb p\u00ebrdit\u00ebsoni kodin e aplikacionit ose t\u00eb aplikoni nj\u00eb patch, krijoni nj\u00eb imazh t\u00eb ri dhe deployeni at\u00eb. Rekomandohet q\u00eb konfigurimi i kontejnerit (porti p\u00ebr d\u00ebgjim, opsionet e mjedisit ekzekutiv, etj.) t\u00eb nxirret jasht\u00eb \u2014 n\u00eb Secrets<\/a><\/noindex> dhe ConfigMaps<\/a><\/noindex>. Ato mund t\u00eb p\u00ebrdit\u00ebsohen pa pasur nevoj\u00eb t\u00eb nd\u00ebrtohet nj\u00eb imazh i ri i kontejnerit. P\u00ebr krijimin e thjesht\u00eb t\u00eb pipeline-ve p\u00ebr nd\u00ebrtimin e imazheve mund t\u00eb p\u00ebrdoret Cloud Build<\/a><\/noindex>. (Sh\u00ebn. p\u00ebrk.<\/b>: Ne p\u00ebrdorim nj\u00eb mjet Open Source p\u00ebr k\u00ebto q\u00ebllime dapp<\/a><\/noindex>.)<\/i><\/p>\n

\"7
\nShembulli i p\u00ebrdit\u00ebsimit t\u00eb konfigurimit t\u00eb Deployment n\u00eb Kubernetes duke p\u00ebrdorur ConfigMap, i montuar n\u00eb pod si konfigurim<\/i><\/p>\n

3. Shmangni kontejner\u00ebt e privilegjuar<\/h2>\n

\n\u0412\u044b \u0432\u0435\u0434\u044c \u043d\u0435 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0435\u0442\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043f\u043e\u0434 root’\u043e\u043c \u043d\u0430 \u0441\u0432\u043e\u0438\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445, \u0432\u0435\u0440\u043d\u043e? \u0415\u0441\u043b\u0438 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043f\u0440\u043e\u043d\u0438\u043a\u043d\u0435\u0442 \u0432 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435, \u043e\u043d \u043f\u043e\u043b\u0443\u0447\u0438\u0442 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root. \u0422\u0435 \u0436\u0435 \u0441\u043e\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u044f \u0441\u043f\u0440\u0430\u0432\u0435\u0434\u043b\u0438\u0432\u044b \u0438 \u0434\u043b\u044f \u0442\u043e\u0433\u043e, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b. \u0415\u0441\u043b\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0438\u0437\u043c\u0435\u043d\u044f\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u043d\u0430 \u0445\u043e\u0441\u0442\u0435, \u043c\u043e\u0436\u043d\u043e \u0432\u044b\u0434\u0430\u0442\u044c \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0443 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u044b\u0435 capabilities<\/i> n\u00ebp\u00ebrmjet opsionit securityContext<\/code><\/a><\/noindex> n\u00eb Kubernetes. N\u00ebse duhet t\u00eb ndryshoni sysctls<\/i>, Kubernetes ka nj\u00eb annotim t\u00eb ve\u00e7ant\u00eb<\/a><\/noindex> p\u00ebr k\u00ebt\u00eb. P\u00ebr gjith\u00e7ka, p\u00ebrpiquni t\u00eb p\u00ebrdorni sa m\u00eb shum\u00eb init-<\/a><\/noindex> dhe kontejner\u00ebt sidecar p\u00ebr t\u00eb kryer operacione t\u00eb tilla me privilegje. Ata nuk k\u00ebrkojn\u00eb akses p\u00ebr asnj\u00eb lloj trafiku, qoft\u00eb t\u00eb brendsh\u00ebm apo t\u00eb jasht\u00ebm.<\/p>\n

N\u00ebse jeni duke administruar nj\u00eb klaster, mund t\u00eb p\u00ebrdorni Politika e Siguris\u00eb s\u00eb Pod<\/a><\/noindex> p\u00ebr kufizimet n\u00eb p\u00ebrdorimin e kontejner\u00ebve t\u00eb privilegjuar.<\/p>\n

4. Shmangni drejtp\u00ebrdrejt\u00eb n\u00ebn root<\/h2>\n

\n\u041e \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0430\u0445 \u0443\u0436\u0435 \u0441\u043a\u0430\u0437\u0430\u043d\u043e, \u043d\u043e \u0431\u0443\u0434\u0435\u0442 \u0435\u0449\u0451 \u043b\u0443\u0447\u0448\u0435, \u0435\u0441\u043b\u0438 \u0432 \u0434\u043e\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043a \u044d\u0442\u043e\u043c\u0443 \u0432\u044b \u043d\u0435 \u0431\u0443\u0434\u0435\u0442\u0435 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0442\u044c \u043f\u043e\u0434 root’\u043e\u043c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0432\u043d\u0443\u0442\u0440\u0438 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0430. \u0415\u0441\u043b\u0438 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043d\u0430\u0439\u0434\u0451\u0442 \u0432 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0438 \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0443\u0434\u0430\u043b\u0451\u043d\u043d\u0443\u044e \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0441 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430, \u043f\u043e\u0441\u043b\u0435 \u0447\u0435\u0433\u043e \u0441\u043c\u043e\u0436\u0435\u0442 \u0432\u044b\u0439\u0442\u0438 \u0438\u0437 \u043f\u0440\u0435\u0434\u0435\u043b\u043e\u0432 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0430 \u0447\u0435\u0440\u0435\u0437 \u043f\u043e\u043a\u0430 \u0435\u0449\u0451 \u043d\u0435\u0438\u0437\u0432\u0435\u0441\u0442\u043d\u0443\u044e \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u0442\u043e \u043f\u043e\u043b\u0443\u0447\u0438\u0442 root’\u0430 \u043d\u0430 \u0445\u043e\u0441\u0442\u0435.<\/p>\n

\u041b\u0443\u0447\u0448\u0438\u0439 \u043f\u0443\u0442\u044c \u0438\u0437\u0431\u0435\u0436\u0430\u0442\u044c \u044d\u0442\u043e\u0433\u043e \u2014 \u0432 \u043f\u0435\u0440\u0432\u0443\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c \u043d\u0435 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0442\u044c \u043d\u0438\u0447\u0435\u0433\u043e \u043f\u043e\u0434 root’\u043e\u043c. \u0414\u043b\u044f \u044d\u0442\u043e\u0433\u043e \u043c\u043e\u0436\u043d\u043e \u0432\u043e\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c\u0441\u044f \u0434\u0438\u0440\u0435\u043a\u0442\u0438\u0432\u043e\u0439 USER<\/code> n\u00eb Dockerfile<\/code> ose runAsUser<\/code> n\u00eb Kubernetes. Administratori i grumbullit gjithashtu mund t\u00eb konfiguroj\u00eb nj\u00eb sjellje t\u00eb detyruar p\u00ebrmes Politika e Siguris\u00eb s\u00eb Pod<\/a><\/noindex>.<\/p>\n

5. B\u00ebni aplikacionin t\u00eb leht\u00eb p\u00ebr monitorim<\/h2>\n

\nAshtu si\u00e7 \u00ebsht\u00eb logimi, monitorimi \u00ebsht\u00eb nj\u00eb pjes\u00eb thelb\u00ebsore e menaxhimit t\u00eb aplikacionit. Nj\u00eb zgjidhje popullore p\u00ebr monitorimin n\u00eb komunitetin Kubernetes \u00ebsht\u00eb Prometheus<\/a><\/noindex> \u2014 nj\u00eb sistem q\u00eb zb discovers (zbulo) automatikisht pod-et dhe sh\u00ebrbimet q\u00eb k\u00ebrkojn\u00eb monitorim. (Sh\u00ebn. p\u00ebrk.<\/b>: Shih gjithashtu raportin ton\u00eb t\u00eb detajuar<\/a><\/noindex> n\u00eb lidhje me monitorimin me Prometheus dhe Kubernetes.)<\/i> Stackdriver<\/a><\/noindex> \u00ebsht\u00eb n\u00eb gjendje t\u00eb monitoroj\u00eb grumbujt Kubernetes dhe p\u00ebrfshin versionin e tij t\u00eb Prometheus p\u00ebr monitorimin e aplikacioneve.<\/p>\n

\"7
\nPaneli i monitorimit Kubernetes n\u00eb Stackdriver<\/i><\/p>\n

Prometheus pret q\u00eb aplikacioni t\u00eb hedh\u00eb metrikat n\u00eb endpoint HTTP. P\u00ebr k\u00ebt\u00eb, jan\u00eb t\u00eb disponueshme bibliotekat e klientit t\u00eb Prometheus<\/a><\/noindex>. I nj\u00ebjti format p\u00ebrdor edhe mjete t\u00eb tjera si OpenCensus<\/a><\/noindex> dhe Istio<\/a><\/noindex>.<\/p>\n

6. B\u00ebni t\u00eb arritsh\u00ebm gjendjen e sh\u00ebndetit t\u00eb aplikacionit<\/h2>\n

\nMenaxhimi i aplikacionit n\u00eb prodhim ndihmohet nga aft\u00ebsia e tij p\u00ebr t\u00eb raportuar mbi gjendjen e tij n\u00eb t\u00eb gjith\u00eb sistemin. A \u00ebsht\u00eb e hapur aplikacioni? A \u00ebsht\u00eb n\u00eb rregull? A \u00ebsht\u00eb gati t\u00eb pranoj\u00eb trafik? Si po sillet? M\u00ebnyra m\u00eb e zakonshme p\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb \u00e7\u00ebshtje \u00ebsht\u00eb implementimi i kontrollit t\u00eb sh\u00ebndetit (health checks)<\/i>. Kubernetes ka dy lloje t\u00eb tyre: liveness dhe readiness probes<\/a><\/noindex>.<\/p>\n

P\u00ebr liveness probe (kontrolli i jetes\u00ebs)<\/i> aplikacioni duhet t\u00eb ket\u00eb nj\u00eb endpoint HTTP q\u00eb kthen p\u00ebrgjigje \"200 OK\", n\u00ebse ai funksionon dhe var\u00ebsit\u00eb e tij kryesore jan\u00eb t\u00eb k\u00ebnaqura. P\u00ebr readiness probe (kontrolli i gatishm\u00ebris\u00eb p\u00ebr sh\u00ebrbim)<\/i> \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0434\u043e\u043b\u0436\u043d\u043e \u0438\u043c\u0435\u0442\u044c \u0434\u0440\u0443\u0433\u043e\u0439 HTTP endpoint, \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u044e\u0449\u0438\u0439 \u043e\u0442\u0432\u0435\u0442 \u00ab200 OK\u00bb, \u0435\u0441\u043b\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0432 \u0437\u0434\u043e\u0440\u043e\u0432\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438, \u0448\u0430\u0433\u0438 \u043f\u043e \u0438\u043d\u0438\u0446\u0438\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u044b \u0438 \u043b\u044e\u0431\u043e\u0439 \u043a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u044b\u0439 \u0437\u0430\u043f\u0440\u043e\u0441 \u043d\u0435 \u043f\u0440\u0438\u0432\u043e\u0434\u0438\u0442 \u043a \u043e\u0448\u0438\u0431\u043a\u0435. Kubernetes \u0431\u0443\u0434\u0435\u0442 \u043d\u0430\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u0442\u0440\u0430\u0444\u0438\u043a \u043d\u0430 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440 \u0442\u043e\u043b\u044c\u043a\u043e \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0433\u043e\u0442\u043e\u0432\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u044d\u0442\u0438\u043c\u0438 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430\u043c\u0438. \u0414\u0432\u0430 endpoint’\u0430 \u043c\u043e\u0433\u0443\u0442 \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0435\u043d\u044b, \u0435\u0441\u043b\u0438 \u0440\u0430\u0437\u043d\u0438\u0446\u0430 \u043c\u0435\u0436\u0434\u0443 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u044f\u043c\u0438 \u0436\u0438\u0437\u043d\u0435\u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0441\u0442\u0438 (liveness) \u0438 \u0433\u043e\u0442\u043e\u0432\u043d\u043e\u0441\u0442\u0438 (readiness) \u043d\u0435\u0442.<\/p>\n

M\u00eb shum\u00eb rreth k\u00ebsaj mund t\u00eb lexoni n\u00eb artikullin p\u00ebrkat\u00ebs nga Sandeep Dinesh, Advocati i Zhvilluesve n\u00eb Google: \"praktikat m\u00eb t\u00eb mira t\u00eb Kubernetes: Vendosja e kontrollimeve t\u00eb sh\u00ebndetit me sondat e gatishm\u00ebris\u00eb dhe vitalitetit\"<\/a><\/noindex>\u00bb.<\/p>\n

7. Zgjidhni me kujdes versionin e imazhit<\/h2>\n

\nShumica e imazheve publike dhe private p\u00ebrdorin nj\u00eb sistem etiketimi t\u00eb ngjash\u00ebm me at\u00eb t\u00eb p\u00ebrshkruar n\u00eb Praktikat m\u00eb t\u00eb mira p\u00ebr nd\u00ebrtimin e konteiner\u00ebve<\/a><\/noindex>. N\u00ebse imazhi p\u00ebrdor nj\u00eb sistem t\u00eb ngjash\u00ebm me versionimin semantik<\/a><\/noindex>, \u00ebsht\u00eb e nevojshme t\u00eb merren parasysh karakteristikat e etiketimit. P\u00ebr shembull, etiketimi latest<\/code> mund t\u00eb l\u00ebviz\u00eb shpesh nga nj\u00eb imazh n\u00eb nj\u00eb tjet\u00ebr \u2014 nuk mund t\u00eb mb\u00ebshteteni \u00eb p\u00ebr nd\u00ebrtimet dhe instalimet e parashikueshme dhe t\u00eb riprodhueshme.<\/p>\n

Mund t\u00eb p\u00ebrdorni etiket\u00ebn X.Y.Z<\/code> (ato zakonisht mbeten t\u00eb pandryshuar), megjithat\u00eb n\u00eb k\u00ebt\u00eb rast, sigurohuni t\u00eb ndiqni t\u00eb gjitha patch-et dhe p\u00ebrdit\u00ebsimet p\u00ebr imazhin. N\u00ebse imazhi q\u00eb p\u00ebrdoret ka nj\u00eb etiket\u00eb X.Y<\/code>, kjo \u00ebsht\u00eb nj\u00eb variant i mir\u00eb p\u00ebrmes q\u00ebndres\u00ebs. Duke e zgjedhur at\u00eb, automatikisht merrni patch-et dhe nj\u00ebkoh\u00ebsisht mb\u00ebshteteni n\u00eb nj\u00eb version t\u00eb stabilizuar t\u00eb aplikacionit.<\/p>\n

P.S. nga p\u00ebrkthyesi<\/h2>\n

\nLexoni gjithashtu n\u00eb blogun ton\u00eb:<\/p>\n