🥇Amaphutha angu-10 avamile uma usebenzisa i-Kubernetes

Qaphela. transl.: Ababhali balesi sihloko bangonjiniyela abavela enkampanini encane yaseCzech, i-pipetail. Bakwazile ukuhlanganisa uhlu oluhle [kwesinye isikhathi oluvinjelwe, kodwa noma kunjalo] olucindezela kakhulu kanye nemibono eyiphutha ehlobene nokusebenza kwamaqoqo e-Kubernetes.

Eminyakeni eminingi yokusebenzisa i-Kubernetes, sisebenze nenani elikhulu lamaqoqo (womabili aphethwe nangalawulwa - ku-GCP, AWS kanye ne-Azure). Ngokuhamba kwesikhathi, saqala ukuqaphela ukuthi amanye amaphutha ayephindaphindwa njalo. Nokho, akukho amahloni kulokhu: okuningi sikwenze ngokwethu!

I-athikili iqukethe amaphutha avame kakhulu futhi isho nendlela yokuwalungisa.

1. Izinsiza: izicelo kanye nemikhawulo

Le nto idinga ukunakwa okuseduze nendawo yokuqala ohlwini.

Isicelo se-CPU ngokuvamile kungenzeka ukuthi ayicacisiwe nhlobo noma inenani eliphansi kakhulu (ukubeka ama-pods amaningi endaweni ngayinye ngangokunokwenzeka). Ngakho-ke, ama-node agcwala ngokweqile. Ngezikhathi zomthwalo omkhulu, amandla okucubungula e-node asetshenziswa ngokugcwele futhi umthwalo othile womsebenzi uthola kuphela lokho "okucelile" ngakho. CPU throttling. Lokhu kuholela ekwandeni kokubambezeleka kwesicelo, ukuphela kwesikhathi, neminye imiphumela engemihle. (Funda kabanzi ngalokhu kwenye inguqulo yethu yakamuva: “Imikhawulo ye-CPU kanye nokudonsa kanzima ku-Kubernetes"- cishe. transl.)

BestEffort (kakhulu hhayi kunconyiwe):

resources: {}

Isicelo se-CPU esiphansi kakhulu (kakhulu hhayi kunconyiwe):

   resources:
      Requests:
        cpu: "1m"

Ngakolunye uhlangothi, ukuba khona komkhawulo we-CPU kungaholela ekweqeni okungenangqondo kwemijikelezo yewashi ngama-pods, noma ngabe iphrosesa ye-node ingalayishiwe ngokugcwele. Futhi, lokhu kungaholela ekubambezelekeni okukhulayo. Ukungqubuzana kuyaqhubeka eduze kwepharamitha Isabelo se-CPU CFS ku-Linux kernel kanye ne-CPU throttling kuye ngemikhawulo emisiwe, kanye nokukhubaza isabelo se-CFS... Maye, imikhawulo ye-CPU ingabangela izinkinga eziningi kunalokho engazixazulula. Ulwazi olwengeziwe mayelana nalokhu lungatholakala kusixhumanisi esingezansi.

Ukukhetha ngokweqile (ukuzibophezela ngokweqile) izinkinga zenkumbulo zingaholela ezinkingeni ezinkulu. Ukufinyelela umkhawulo we-CPU kuhlanganisa ukweqa imijikelezo yewashi, kuyilapho ukufinyelela umkhawulo wenkumbulo kuhlanganisa nokubulala i-pod. Wake wakubona OOMkill? Yebo, yilokho kanye esikhuluma ngakho.

Ingabe ufuna ukunciphisa amathuba okuba lokhu kwenzeke? Ungabeki kakhulu inkumbulo futhi usebenzise i-Guaranteed QoS (Ikhwalithi Yesevisi) ngokusetha isicelo sememori sifike emkhawulweni (njengakusibonelo esingezansi). Funda kabanzi ngalokhu ku Henning Jacobs izethulo (Unjiniyela Oholayo eZalando).

Burstable (amathuba aphezulu okuthola i-OOMkilled):

   resources:
      requests:
        memory: "128Mi"
        cpu: "500m"
      limits:
        memory: "256Mi"
        cpu: 2

Kuqinisekisiwe:

   resources:
      requests:
        memory: "128Mi"
        cpu: 2
      limits:
        memory: "128Mi"
        cpu: 2

Yini engasiza lapho usetha izinsiza?

Ngosizo luka i-metrics-server ungabona ukusetshenziswa kwensiza ye-CPU yamanje kanye nokusetshenziswa kwenkumbulo ngama-pods (kanye neziqukathi ezingaphakathi kwazo). Ngokunokwenzeka, usuvele uyayisebenzisa. Vele usebenzise imiyalo elandelayo:

kubectl top pods
kubectl top pods --containers
kubectl top nodes

Nokho, abonisa kuphela ukusetshenziswa kwamanje. Ingakunikeza umbono onzima wokuhleleka kobukhulu, kodwa ekugcineni uzodinga umlando wezinguquko kumamethrikhi ngokuhamba kwesikhathi (ukuphendula imibuzo efana nokuthi: “Ibiyini i-CPU ephezulu kakhulu?”, “Bekunjani umthwalo izolo ekuseni?”, njll.). Ukuze lokhu ungasebenzisa Prometheus, I-DataDog namanye amathuluzi. Bavele bathole amamethrikhi kuseva ye-metrics futhi bawagcine, futhi umsebenzisi angakwazi ukuwabuza futhi awahlele ngokufanele.

I-VerticalPodAutoscaler kuvumela shintsha le nqubo. Ilandelela i-CPU nomlando wokusetshenziswa kwenkumbulo futhi imise izicelo ezintsha nemikhawulo ngokusekelwe kulolu lwazi.

Ukusebenzisa amandla ekhompyutha ngendlela efanele akuwona umsebenzi olula. Kufana nokudlala iTetris ngaso sonke isikhathi. Uma ukhokha kakhulu ngamandla wokubala ngokusetshenziswa okumaphakathi okuphansi (yithi ~10%), sincoma ukuthi ubheke imikhiqizo esuselwe ku-AWS Fargate noma i-Virtual Kubelet. Akhelwe phezu kwemodeli yokukhokha engenasiphakeli/ukukhokha ngakunye kokusetshenziswa, okungenzeka kushibhe ngaphansi kwezimo ezinjalo.

2. Ukuphila kanye nokulungela ukuhlola

Ngokuzenzakalela, ukuhlola ukuphila nokulungela akunikwa amandla ku-Kubernetes. Futhi kwesinye isikhathi bayakhohlwa ukuwavula...

Kodwa ungayiqala kanjani enye isevisi uma kwenzeka iphutha elibulalayo? Futhi i-balancer yomthwalo yazi kanjani ukuthi i-pod isilungele ukwamukela ithrafikhi? Noma ukuthi ingakwazi ukuphatha ithrafikhi eyengeziwe?

Lezi zivivinyo zivame ukudideka komunye nomunye:

Ukuphila - ukuhlola "ukusinda", okuqalisa kabusha i-pod uma yehluleka;
Ukulungela - ukuhlola ukulungela, uma kuhluleka, kunqamula i-pod kusevisi ye-Kubernetes (lokhu kungabhekwa kusetshenziswa kubectl get endpoints) futhi ithrafikhi ayifiki kuyo kuze kube yilapho ukuhlola okulandelayo kuqedwa ngempumelelo.

Womabili lamasheke KWENZIWE NGESIKHATHI WONKE UMJIKELO WEMPILO WE-POD. Kubaluleke kakhulu.

Umbono oyiphutha ojwayelekile ukuthi ama-probes wokulungela aqhutshwa kuphela ekuqaleni ukuze olinganiselayo azi ukuthi i-pod isilungile (Ready) futhi ingaqala ukucubungula ithrafikhi. Noma kunjalo, lokhu kungenye yezinketho zokusetshenziswa kwazo.

Okunye ukuthi kungenzeka ukuthola ukuthi ithrafikhi ku-pod idlulele futhi iyayilayisha kakhulu (noma i-pod yenza izibalo zokusebenzisa izinsiza). Kulokhu, ukuhlolwa kokulungela kuyasiza nciphisa umthwalo ku-pod futhi "uyipholise".. Ukuphothulwa ngempumelelo kokuhlolwa kokulungela esikhathini esizayo kuyakuvumela ukwandisa umthwalo ku-pod futhi. Kulokhu (uma ukuhlolwa kokulungela kwehluleka), ukwehluleka kohlolo lwe-liveness kungaba okuphambene kakhulu. Kungani uqale kabusha i-pod enempilo futhi esebenza kanzima?

Ngakho-ke, kwezinye izimo, awekho nhlobo amasheke angcono kunokuwanika amandla ngamapharamitha alungiselelwe ngokungalungile. Njengoba kushiwo ngenhla, uma isheke liveness amakhophi ukulungela ukuhlola, khona-ke usenkingeni enkulu. Okukhethwa kukho ukumisa ukuhlolwa ukulungela kuphela, futhi ukuphila okuyingozi shiya eceleni.

Zombili izinhlobo zokuhlola akufanele zehluleke lapho ukuncika okuvamile kwehluleka, ngaphandle kwalokho lokhu kuzoholela ekuhlulekeni kwe-cascading (okufana ne-avalanche) kwawo wonke ama-pods. Ngamanye amazwi, ungazilimazi.

3. I-LoadBalancer yesevisi ngayinye ye-HTTP

Kungenzeka kakhulu, unezinsizakalo ze-HTTP kuqoqo lakho ongathanda ukulidlulisela emhlabeni wangaphandle.

Uma uvula isevisi njenge type: LoadBalancer, isilawuli sayo (kuye ngokuthi umhlinzeki wesevisi) sizohlinzeka futhi sixoxisane nge-LoadBalancer yangaphandle (hhayi ngempela ukuthi isebenza ku-L7, kodwa kunalokho ngisho naku-L4), futhi lokhu kungase kuthinte izindleko (ikheli langaphandle le-IPv4 elimile, amandla ekhompuyutha, ukukhokhiswa kwesekhondi ngalinye. ) ngenxa yesidingo sokudala inani elikhulu lezinsiza ezinjalo.

Kulokhu, kunengqondo kakhulu ukusebenzisa isilinganisi somthwalo sangaphandle esisodwa, ukuvula izinsizakalo njenge type: NodePort. Noma okungcono, nweba okuthile okufana nalokhu nginx-ingress-isilawuli (noma I-traefik), ozoba yedwa INodePort iphoyinti lokugcina elihlotshaniswa nesilinganisi somthwalo wangaphandle futhi izohambisa ithrafikhi kuqoqo kusetshenziswa ingress-Kubernetes izinsiza.

Ezinye izinsiza ze-intra-cluster (micro) ezisebenzisanayo “zingakwazi ukuxhumana” zisebenzisa izinsiza ezifana I-ClusterIP kanye nendlela yokutholwa kwesevisi eyakhelwe ngaphakathi nge-DNS. Vele ungasebenzisi i-DNS/IP yabo yomphakathi, njengoba lokhu kungase kube nomthelela ukubambezeleka futhi kukhuphule izindleko zezinsizakalo zamafu.

4. Ukukala iqoqo ngokuzenzakalelayo ngaphandle kokucabangela izici zalo

Lapho ungeza ama-node futhi uwakhipha kuqoqo, akufanele uthembele kwamanye amamethrikhi ayisisekelo njengokusetshenziswa kwe-CPU kulawo ma-node. Ukuhlelwa kwephodi kufanele kucabangele okuningi imikhawulo, okufana nokuhambisana kwe-pod/node, ukungcoliswa nokubekezelela, izicelo zezinsiza, i-QoS, njll. Ukusebenzisa i-autoscaler yangaphandle engacabangi lawa ma-nuances kungaholela ezinkingeni.

Cabanga ukuthi i-pod ethile kufanele ihlelwe, kodwa wonke amandla e-CPU atholakalayo ayacelwa/ahlakazwa kanye ne-pod. ubhajwa esimeni Pending. I-autoscaler yangaphandle ibona isilinganiso samanje somthwalo we-CPU (hhayi oceliwe) futhi asiqali ukunwetshwa (isikali) - akengezi enye i-node. Ngenxa yalokho, le pod ngeke ihlelwe.

Kulokhu, ukukala okuhlanekezelwe (sikala) — ukususa i-node kuqoqo kuhlala kunzima kakhulu ukukusebenzisa. Cabanga ukuthi une-pod esezingeni eliphezulu (enesitoreji esiqhubekayo sixhunyiwe). Imiqulu ephikelelayo ngokuvamile ngezakwa indawo ethile yokutholakala futhi azifanisiwe esifundeni. Ngakho-ke, uma i-autoscaler yangaphandle isusa i-node nale pod, umhleli ngeke akwazi ukuhlela le pod kwenye indawo, ngoba lokhu kungenziwa kuphela endaweni yokutholakala lapho isitoreji esiqhubekayo sikhona. I-Pod izobambeka esimweni Pending.

Kudume kakhulu emphakathini wakwaKubernetes iqoqo-autoscaler. Isebenza ngeqoqo, isekela ama-API avela kubahlinzeki abakhulu bamafu, icabangela yonke imikhawulo futhi ingakala ezimweni ezingenhla. Iyakwazi futhi ukungena ngenkathi igcina yonke imikhawulo ebekiwe, ngaleyo ndlela yonga imali (ebengasetshenziselwa umthamo ongasetshenzisiwe).

5. Ukunganaki amakhono e-IAM/RBAC

Qaphela ukusebenzisa abasebenzisi be-IAM abanezimfihlo eziphikelelayo ze imishini kanye nezicelo. Hlela ukufinyelela kwesikhashana usebenzisa izindima nama-akhawunti wesevisi (ama-akhawunti wesevisi).

Sivame ukuhlangana neqiniso lokuthi okhiye bokufinyelela (nezimfihlo) bafakwe ikhodi eqinile ekucushweni kohlelo lokusebenza, kanye nokushaya indiva ukuzungeziswa kwezimfihlo naphezu kokuba nokufinyelela ku-Cloud IAM. Sebenzisa izindima ze-IAM nama-akhawunti esevisi esikhundleni sabasebenzisi lapho kufanele khona.

Khohlwa nge-kube2iam bese uqonda ngqo kuzindima ze-IAM zama-akhawunti esevisi (njengoba kuchazwe ku inothi yegama elifanayo Štěpán Vraný):

apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::123456789012:role/my-app-role
  name: my-serviceaccount
  namespace: default

Isichasiselo esisodwa. Akunzima kangako, akunjalo?

Futhi, unganikezi ama-akhawunti wesevisi kanye namalungelo amaphrofayela esibonelo admin и cluster-adminuma bengayidingi. Lokhu kunzima kakhulu ukukusebenzisa, ikakhulukazi kuma-RBAC K8, kodwa kuwufanele umzamo.

6. Ungathembeli ku-anti-affinity ezenzakalelayo ukuze uthole ama-pods

Cabanga ukuthi unezifaniso ezintathu zokunye ukusetshenziswa endaweni eyodwa. I-node iyawa, futhi kanye nawo wonke ama-replicas. Isimo esingemnandi, akunjalo? Kodwa kungani zonke izifanekiso zazisendaweni eyodwa? Ingabe i-Kubernetes akufanele inikeze ukutholakala okuphezulu (HA)?!

Ngeshwa, umhleli we-Kubernetes, ngokusuka kwakhe, akahambisani nemithetho yokuphila okuhlukile (anti-affinity) okwemidumba. Kufanele zichazwe ngokucacile:

// опущено для краткости
      labels:
        app: zk
// опущено для краткости
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: "app"
                    operator: In
                    values:
                    - zk
              topologyKey: "kubernetes.io/hostname"

Yilokho kuphela. Manje ama-pods azohlelwa kuma-node ahlukene (lesi simo sibhekwa kuphela ngesikhathi sokuhlela, kodwa hhayi ngesikhathi sokusebenza - yingakho requiredDuringSchedulingIgnoredDuringExecution).

Lapha sikhuluma ngakho podAntiAffinity ezindaweni ezahlukene: topologyKey: "kubernetes.io/hostname", - futhi hhayi mayelana nezindawo zokutholakala ezihlukene. Ukuze usebenzise i-HA egcwele ngokugcwele, kuzodingeka umbe ujule kulesi sihloko.

7. Ukuziba ama-PodDisruptionBudgets

Cabanga ukuthi unomthwalo wokukhiqiza kuqoqo le-Kubernetes. Ngezikhathi ezithile, ama-node kanye ne-cluster ngokwayo kufanele ibuyekezwe (noma inqanyulwe). I-PodDisruptionBudget (PDB) into efana nesivumelwano sesiqinisekiso sesevisi phakathi kwabalawuli beqoqo nabasebenzisi.

I-PDB ikuvumela ukuthi ugweme ukuphazamiseka kwesevisi okubangelwa ukuntuleka kwama-node:

apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
  name: zk-pdb
spec:
  minAvailable: 2
  selector:
    matchLabels:
      app: zookeeper

Kulesi sibonelo, wena, njengomsebenzisi weqoqo, uthi kubaphathi: "Hey, nginesevisi yezookeeper, futhi kungakhathaliseki ukuthi wenzani, ngingathanda ukuba okungenani kube nezifanekiso ezimbili zale sevisi ezihlale zikhona."

Ungafunda okwengeziwe ngalokhu lapha.

8. Abasebenzisi abaningi noma izindawo kuqoqo elivamile

Izindawo zokuhlala e- Kubernetes (izikhala zamagama) unganikezi ukwahlukanisa okuqinile.

Umbono oyiphutha ojwayelekile ukuthi uma uthumela umthwalo ongewona womkhiqizo endaweni eyodwa yegama kanye nomthwalo we-prod kwenye, khona-ke ngeke zithonyane nganoma iyiphi indlela... Nokho, izinga elithile lokuzihlukanisa lingafinyelelwa kusetshenziswa izicelo/imikhawulo yensiza, ukubeka izilinganiso, nokusetha amakilasi abalulekile. Ukuhlukaniswa okuthile "okungokomzimba" endizeni yedatha kunikezwa ama-affinities, ukubekezelela, ama-tants (noma ama-nodeselectors), kodwa ukuhlukana okunjalo impela yinkimbinkimbi sebenzisa.

Labo abadinga ukuhlanganisa zombili izinhlobo zemithwalo yemisebenzi ku-cluster efanayo kuzodingeka babhekane nobunzima. Uma singekho isidingo esinjalo, futhi ungakwazi ukukhokhela elinye iqoqo ngaphezulu (isho, efwini lomphakathi), ngakho-ke kungcono ukwenza kanjalo. Lokhu kuzofeza izinga eliphezulu kakhulu le-insulation.

9. Inqubomgomo Yethrafikhi yangaphandle: Iqoqo

Kaningi sibona ukuthi yonke i-traffic ngaphakathi kweqoqo iza ngesevisi efana ne-NodePort, lapho inqubomgomo ezenzakalelayo isethwe. externalTrafficPolicy: Cluster... Kusho ukuthi INodePort ivuliwe kuwo wonke ama-node ku-cluster, futhi ungasebenzisa noma iyiphi yazo ukuze uhlanganyele nesevisi oyifunayo (iqoqo lama-pods).

Ngasikhathi sinye, ama-pods wangempela ahlotshaniswa nensizakalo ye-NodePort eshiwo ngenhla avame ukutholakala kokuthile isethi engaphansi yalawa ma-node. Ngamanye amazwi, uma ngixhuma ku-node engenayo i-pod edingekayo, izodlulisela ithrafikhi kwenye indawo, ukwengeza i-hop nokubambezeleka okwandayo (uma amanodi atholakala ezindaweni ezitholakalayo/ezikhungweni zedatha ezihlukene, ukubambezeleka kungaba phezulu kakhulu; ngaphezu kwalokho, izindleko zethrafikhi ye-egress zizokhuphuka).

Ngakolunye uhlangothi, uma isevisi ethile ye-Kubernetes inesethi yenqubomgomo externalTrafficPolicy: Local, bese i-NodePort ivula kuphela kulawo ma-node lapho ama-pods adingekayo esebenza khona. Uma usebenzisa isilinganisi somthwalo sangaphandle esihlola isimo (ukuhlolwa kwezempilo) ama-endpoints (isebenza kanjani AWS ELB), Yena izothumela ithrafikhi kuphela ezindaweni ezidingekayo, okuzoba nomphumela onenzuzo ekubambezelekeni, izidingo zekhompuyutha, izikweletu ze-egress (kanye nomqondo ovamile ubeka okufanayo).

Maningi amathuba okuthi usuvele usebenzisa into efana nale I-traefik noma nginx-ingress-isilawuli njenge-NodePort endpoint (noma i-LoadBalancer, ephinde isebenzisa i-NodePort) ukuhambisa ithrafikhi yokungena kwe-HTTP, futhi ukusetha le nketho kunganciphisa kakhulu ukubambezeleka kwezicelo ezinjalo.

В lolu shicilelo Ungafunda kabanzi mayelana ne-externalTrafficPolicy, izinzuzo zayo kanye nokubi.

10. Ungaboshelwa kumaqoqo futhi ungayisebenzisi kabi indiza yokulawula

Ngaphambilini, kwakuyisiko ukubiza amaseva ngamagama afanele: Anton, HAL9000 kanye ne-Colossus... Namuhla zithathelwe indawo izihlonzi ezikhiqizwa ngokungahleliwe. Kodwa-ke, lo mkhuba wasala, futhi manje amagama afanele aya kumaqoqo.

Indaba ejwayelekile (esekelwe ezenzakalweni zangempela): konke kwaqala ngobufakazi bomqondo, ngakho iqoqo lalinegama eliziqhenyayo. testing… Sekudlule iminyaka futhi ISAsetshenziswa ekukhiqizeni, futhi wonke umuntu uyesaba ukuyithinta.

Akukho lutho olujabulisayo mayelana namaqoqo aphenduka izilwane ezifuywayo, ngakho-ke sincoma ukuwasusa ngezikhathi ezithile ngenkathi sizilolonga ukululama kwenhlekelele (lokhu kuzosiza ubunjiniyela besiphithiphithi - cishe. transl.). Ngaphezu kwalokho, ngeke kube buhlungu ukusebenza kungqimba lokulawula (indiza yokulawula). Ukwesaba ukumthinta akulona uphawu oluhle. njll ufile? Bafo, nisenkingeni ngempela!

Ngakolunye uhlangothi, akufanele uthathwe wukuxhaphaza. Ngokuhamba kwesikhathi isendlalelo sokulawula singase sihambe kancane. Ngokunokwenzeka, lokhu kungenxa yenani elikhulu lezinto ezidalwe ngaphandle kokujikeleza kwazo (isimo esivamile lapho usebenzisa i-Helm enezilungiselelo ezizenzakalelayo, yingakho isimo sayo kuma-configmaps/secrets singabuyekeziwe - ngenxa yalokho, izinkulungwane zezinto zinqwabelana ungqimba lokulawula) noma ngokuhlelwa njalo kwezinto ze-kube-api (ukukala okuzenzakalelayo, kwe-CI/CD, ukuqapha, izingodo zomcimbi, izilawuli, njll.).

Ngaphezu kwalokho, sincoma ukuthi uhlole izivumelwano ze-SLA/SLO nomhlinzeki ophethwe we-Kubernetes futhi unake iziqinisekiso. Umthengisi angaqinisekisa lawula ukutholakala kwesendlalelo (noma izingxenye zayo ezingaphansi), kodwa hhayi ukubambezeleka kwe-p99 kwezicelo ozithumela kuyo. Ngamanye amazwi, ungangena kubectl get nodes, futhi uthole impendulo kuphela ngemva kwemizuzu eyi-10, futhi lokhu ngeke kube ukwephulwa kwemigomo yesivumelwano sesevisi.

11. Ibhonasi: usebenzisa ithegi yakamuva

Kodwa lokhu kakade kuyi-classic. Muva nje asikaze sihlangane nale nqubo, njengoba abaningi, sebefunde kokuhlangenwe nakho okubuhlungu, bayekile ukusebenzisa ithegi. :latest futhi waqala ukuphina izinguqulo. Hooray!

ECR igcina ukungaguquki kwamathegi esithombe; Sincoma ukuthi uzijwayeze nalesi sici esimangalisayo.

Isifingqo

Ungalindeli ukuthi yonke into isebenze ngobusuku obubodwa: I-Kubernetes ayiyona i-panacea. Uhlelo lokusebenza olubi izohlala ngale ndlela ngisho naseKubernetes (futhi mhlawumbe kuzoba kubi kakhulu). Ukunganaki kuzoholela ekubeni yinkimbinkimbi ngokweqile, umsebenzi ohamba kancane futhi ocindezelayo wesendlalelo sokulawula. Ukwengeza, usengozini yokushiywa ngaphandle kwesu lokutakula inhlekelele. Ungalindeli ukuthi i-Kubernetes izokunikeza ukuhlukaniswa nokutholakala okuphezulu ngaphandle kwebhokisi. Chitha isikhathi esithile wenza uhlelo lwakho lokusebenza lube ngokwemvelo ngempela.

Ungakwazi ukujwayelana nezipiliyoni ezingaphumelelanga zamaqembu ahlukahlukene leli qoqo lezindaba nguHenning Jacobs.

Abafisa ukwengeza ohlwini lwamaphutha anikezwe kulesi sihloko bangaxhumana nathi ku-Twitter (@MarekBartik, @MstrsObserver).

I-PS evela kumhumushi

Funda futhi kubhulogi yethu:

«Ukuklama Amaqoqo e-Kubernetes: Mangaki Kufanele Abekhona?";
«I-ABC Yokuvikeleka ku-Kubernetes: Ukuqinisekisa, Ukugunyazwa, Ukucwaninga";
«Ukukala okuzenzakalelayo nokuphathwa kwezinsiza ku-Kubernetes"(ukubuyekeza kanye nombiko wevidiyo);
«I-ConfigMaps ku-Kubernetes: ama-nuances okufanele ukwazi ngawo".

Source: www.habr.com

Amaphutha ayi-10 ajwayelekile lapho usebenzisa i-Kubernetes