Kubernetes babban kayan aiki ne don gudanar da kwantena Docker a cikin yanayin samar da tari. Koyaya, akwai matsalolin da Kubernetes ba zai iya magance su ba. Don ƙaddamar da samarwa akai-akai, muna buƙatar cikakken jigilar Blue/Green mai sarrafa kansa don guje wa raguwar lokaci a cikin tsari, wanda kuma yana buƙatar ɗaukar buƙatun HTTP na waje da aiwatar da abubuwan saukar da SSL. Wannan yana buƙatar haɗin kai tare da ma'aunin nauyi kamar ha-proxy. Wani ƙalubale shine juzu'i na kubernetes ta atomatik lokacin da yake gudana a cikin yanayin gajimare, misali jujjuya gunkin cikin dare.
Duk da yake Kubernetes ba shi da waɗannan fasalulluka daga cikin akwatin, yana ba da API wanda zaku iya amfani da shi don magance matsaloli iri ɗaya. An ƙera kayan aiki don tura Blue/Green mai sarrafa kansa da ƙima na gungu na Kubernetes a matsayin wani ɓangare na aikin Cloud RTI, wanda aka ƙirƙira bisa tushen buɗe ido.
Wannan labarin, kwafin bidiyo, yana nuna muku yadda ake saita Kubernetes tare da sauran abubuwan buɗe tushen tushen don ƙirƙirar yanayin shirye-shiryen samarwa wanda ke karɓar lambar daga git ɗin ba tare da raguwa a cikin samarwa ba.
Don haka, da zarar kun sami damar yin amfani da aikace-aikacenku daga duniyar waje, za ku iya fara tsarawa gabaɗaya ta atomatik, wato, kawo shi zuwa matakin da za ku iya aiwatar da git da kuma tabbatar da cewa wannan git aikata ya ƙare a samarwa. A dabi'a, lokacin aiwatar da waɗannan matakan, lokacin aiwatar da turawa, ba ma so mu gamu da raguwar lokaci. Don haka, duk wani aiki da kai a cikin Kubernetes yana farawa da API.
Kubernetes ba kayan aiki ba ne wanda za'a iya amfani dashi da kyau daga cikin akwatin. Tabbas, zaku iya yin hakan, amfani da kubectl da sauransu, amma har yanzu API shine abu mafi ban sha'awa da amfani game da wannan dandamali. Ta amfani da API azaman saitin ayyuka, zaku iya samun damar kusan duk abin da kuke son yi a Kubernetes. kubectl kanta shima yana amfani da REST API.
Wannan shine REST, saboda haka zaku iya amfani da kowane harshe ko kayan aiki don aiki tare da wannan API, amma rayuwarku za ta sami sauƙi ta wurin ɗakunan karatu na al'ada. Ƙungiyara ta rubuta irin waɗannan ɗakunan karatu guda 2: ɗaya don Java/OSGi da ɗaya don Go. Na biyu ba a yawan amfani da shi, amma a kowane hali kana da waɗannan abubuwa masu amfani a hannunka. Suna aikin buɗe tushen lasisin wani ɓangare. Akwai da yawa irin waɗannan ɗakunan karatu don harsuna daban-daban, don haka za ku iya zaɓar waɗanda suka fi dacewa da ku.
Don haka, kafin ku fara sarrafa aikin aikin ku, kuna buƙatar tabbatar da cewa tsarin ba zai kasance ƙarƙashin kowane lokaci ba. Misali, ƙungiyarmu tana gudanar da ayyukan samarwa a tsakiyar rana lokacin da mutane ke amfani da aikace-aikacen a mafi yawan su, don haka yana da mahimmanci don guje wa jinkiri a cikin wannan tsari. Don guje wa raguwar lokaci, ana amfani da hanyoyi 2: shuɗi/koren turawa ko sabuntawa. A cikin yanayin ƙarshe, idan kuna da kwafi guda 5 na aikace-aikacen da ke gudana, ana sabunta su bi da bi ɗaya bayan ɗaya. Wannan hanyar tana aiki da kyau, amma ba ta dace ba idan kuna da nau'ikan aikace-aikacen daban-daban suna gudana lokaci guda yayin aikin turawa. A wannan yanayin, zaku iya sabunta ƙirar mai amfani yayin da backend ke gudana tsohon sigar, kuma aikace-aikacen zai daina aiki. Saboda haka, daga ra'ayi na shirye-shirye, yin aiki a irin waɗannan yanayi yana da wuyar gaske.
Wannan shine ɗayan dalilan da yasa muka gwammace mu yi amfani da tura shuɗi/kore don sarrafa tura aikace-aikacen mu. Tare da wannan hanyar, dole ne ku tabbatar da cewa sigar aikace-aikacen ɗaya ce kawai ke aiki a lokaci ɗaya.
Tsarin tura shuɗi/kore yayi kama da wannan. Muna karɓar zirga-zirga don aikace-aikacen mu ta hanyar ha-proxy, wanda ke tura shi zuwa kwafin aikace-aikacen nau'in iri ɗaya.
Lokacin da aka yi sabon ƙaddamarwa, muna amfani da Deployer, wanda aka ba da sababbin kayan aiki kuma yana tura sabon sigar. Aiwatar da sabon nau'in aikace-aikacen yana nufin cewa sabon saitin kwafi an “ɗauka”, bayan haka ana ƙaddamar da waɗannan kwafin sabon sigar a cikin wani dabam, sabon kwafsa. Koyaya, ha-proxy bai san komai game da su ba kuma bai kai musu wani nauyin aiki ba tukuna.
Sabili da haka, da farko, ya zama dole don yin aikin duba sabbin nau'ikan duba lafiyar don tabbatar da cewa kwafi suna shirye don hidimar kaya.
Duk abubuwan da ake turawa dole ne su goyi bayan wani nau'i na duba lafiya. Wannan na iya zama rajistan kiran HTTP mai sauƙi, lokacin da kuka karɓi lamba tare da matsayi 200, ko ƙarin bincike mai zurfi, wanda zaku bincika haɗin kwafi tare da bayanan bayanai da sauran ayyuka, kwanciyar hankali na haɗin mahalli mai ƙarfi. , kuma ko komai ya fara kuma yayi aiki daidai. Wannan tsari na iya zama mai rikitarwa.
Bayan tsarin ya tabbatar da cewa duk kwafin da aka sabunta suna aiki, Deployer zai sabunta tsarin kuma ya wuce daidaitaccen confd, wanda zai sake saita ha-proxy.
Bayan haka ne kawai za a tura zirga-zirgar ababen hawa zuwa kwaf ɗin tare da kwafin sabon sigar, kuma tsohon kwaf ɗin zai ɓace.
Wannan tsarin ba fasalin Kubernetes bane. Manufar ƙaddamar da Blue/koren ya kasance na dogon lokaci kuma koyaushe yana amfani da ma'aunin nauyi. Da farko, kuna jagorantar duk zirga-zirga zuwa tsohuwar sigar aikace-aikacen, kuma bayan sabuntawa, kun canza shi gaba ɗaya zuwa sabon sigar. Ana amfani da wannan ka'ida ba kawai a cikin Kubernetes ba.
Yanzu zan gabatar muku da wani sabon bangaren turawa - Deployer, wanda ke yin gwajin lafiyar jiki, sake fasalin proxies, da sauransu. Wannan ra'ayi ne wanda bai shafi duniyar waje ba kuma yana cikin Kubernetes. Zan nuna muku yadda zaku iya ƙirƙirar ra'ayin Mai Rarraba ku ta amfani da kayan aikin buɗe tushen.
Don haka, abu na farko da Deployer yayi shine ƙirƙirar mai sarrafa kwafin RC ta amfani da Kubernetes API. Wannan API ɗin yana ƙirƙirar kwasfa da ayyuka don ƙarin turawa, wato, yana ƙirƙirar sabon tari don aikace-aikacen mu. Da zaran RC ta gamsu cewa kwafin sun fara, zai yi gwajin lafiya akan aikin su. Don yin wannan, Deployer yana amfani da umarnin GET/health. Yana gudanar da abubuwan binciken da suka dace kuma yana bincika duk abubuwan da ke goyan bayan aikin gungun.
Bayan duk kwas ɗin sun ba da rahoton lafiyar su, Deployer ya ƙirƙiri sabon nau'in daidaitawa - da dai sauransu da aka rarraba ajiya, wanda Kubernetes ke amfani da shi a ciki, gami da adana tsarin daidaita ma'aunin nauyi. Muna rubuta bayanai zuwa etcd, da ƙaramin kayan aiki da ake kira confd Monitors da sauransu don sabbin bayanai.
Idan ya gano kowane canje-canje ga tsarin farko, yana haifar da sabon fayil ɗin saiti kuma yana tura shi zuwa ha-proxy. A wannan yanayin, ha-proxy yana sake yin aiki ba tare da rasa kowane haɗin kai ba kuma yana magance nauyin zuwa sabbin ayyuka waɗanda ke ba da damar sabon sigar aikace-aikacen mu suyi aiki.
Kamar yadda kake gani, duk da yawan abubuwan da aka gyara, babu wani abu mai rikitarwa a nan. Kuna buƙatar ƙarin kulawa ga API da sauransu. Ina so in gaya muku game da buɗaɗɗen kayan aikin da mu kanmu muke amfani da shi - Amdatu Kubernetes Deployer.
Kayan aiki ne don tsara ayyukan Kubernetes kuma yana da fasali masu zuwa:
- Blue/Green turawa;
- kafa ma'aunin nauyi na waje;
- gudanarwa mai siffantawa turawa;
- sarrafa ainihin ƙaddamarwa;
- duba ayyukan duban lafiya yayin turawa;
- aiwatar da masu canjin yanayi a cikin kwasfa.
An gina wannan Deployer a saman Kubernetes API kuma yana ba da API REST don sarrafa hannuwa da ƙaddamarwa, da kuma API na Websocket don raɗaɗɗen raƙuman ruwa yayin aiwatar da aikin.
Yana sanya bayanan daidaita ma'aunin nauyi a cikin da dai sauransu, don haka ba lallai ne ku yi amfani da ha-proxy tare da tallafin waje ba, amma cikin sauƙin amfani da fayil ɗin daidaita ma'aunin nauyi na ku. Amdatu Deployer an rubuta shi a cikin Go, kamar Kubernetes kanta, kuma Apache yana da lasisi.
Kafin in fara amfani da wannan sigar mai aikawa, na yi amfani da mai siffanta ƙaddamarwa, wanda ke ƙayyadaddun sigogin da nake buƙata.
Ɗaya daga cikin mahimman sigogi na wannan lambar shine don kunna tutar "useHealthCheck". Muna buƙatar sakawa cewa dole ne a yi gwajin lafiya yayin aikin turawa. Ana iya kashe wannan saitin lokacin da turawa tayi amfani da kwantena na ɓangare na uku waɗanda basa buƙatar tabbatarwa. Wannan mai siffantawa kuma yana nuna adadin kwafi da URL na gaba wanda ha-proxy ke buƙata. A ƙarshe shine tutar ƙayyadaddun kwas ɗin "podspec", wanda ke kiran Kubernetes don bayani kan daidaita tashar jiragen ruwa, hoto, da sauransu. Wannan mai sauƙin siffantawa JSON ne.
Wani kayan aiki wanda ke cikin aikin Amdatu mai buɗewa shine Deploymentctl. Yana da UI don daidaita abubuwan tura aiki, yana adana tarihin turawa, kuma yana ƙunshe da mahaɗar yanar gizo don sake kira daga masu amfani da ɓangare na uku da masu haɓakawa. Maiyuwa ba za ku yi amfani da UI ba tunda Amdatu Deployer ita kanta API ce REST, amma wannan keɓancewar za ta iya sauƙaƙe muku aiki ba tare da haɗa kowane API ba. An rubuta Deploymentctl a cikin OSGi/Vertx ta amfani da Angular 2.
Yanzu zan nuna abin da ke sama akan allo ta amfani da rikodi da aka riga aka yi don kada ku jira. Za mu tura aikace-aikacen Go mai sauƙi. Kada ku damu idan baku gwada Go a baya ba, aikace-aikace ne mai sauƙi don haka yakamata ku iya gano shi.
Anan muna ƙirƙirar uwar garken HTTP wanda ke amsawa ga / lafiya kawai, don haka wannan aikace-aikacen yana gwada gwajin lafiyar kawai ba komai ba. Idan cak ɗin ya wuce, ana amfani da tsarin JSON da aka nuna a ƙasa. Ya ƙunshi nau'in aikace-aikacen da mai aikawa zai tura, da saƙon da kuke gani a saman fayil ɗin, da nau'in bayanan boolean - shin aikace-aikacenmu yana aiki ko a'a.
Na yaudari kadan tare da layi na ƙarshe, saboda na sanya ƙayyadadden ƙimar boolean a saman fayil ɗin, wanda a nan gaba zai taimaka mini in tura ko da aikace-aikacen "marasa lafiya". Za mu magance wannan daga baya.
Don haka mu fara. Da farko, muna bincika kasancewar kowane kwasfan fayiloli masu gudana ta amfani da umarnin ~ kubectl samun kwasfan fayiloli kuma, dangane da rashin amsawa daga URL na gaba, muna tabbatar da cewa babu wani turawa a halin yanzu.
Na gaba akan allo kuna ganin ƙirar Deploymentctl da na ambata, wanda aka saita sigogin turawa: sarari suna, sunan aikace-aikacen, sigar turawa, adadin kwafi, URL na gaba, sunan akwati, hoto, iyakokin albarkatu, lambar tashar jiragen ruwa don duba lafiya, da dai sauransu. Iyakokin albarkatu suna da mahimmanci, saboda suna ba ku damar amfani da matsakaicin yuwuwar adadin kayan aikin. Anan kuma zaka iya duba log ɗin Deployment.
Idan yanzu kuka maimaita umarnin ~ kubectl samun pods, zaku iya ganin cewa tsarin yana “daskare” na tsawon daƙiƙa 20, yayin da aka sake saita ha-proxy. Bayan wannan, kwaf ɗin yana farawa, kuma ana iya ganin kwafin mu a cikin log ɗin turawa.
Na yanke jira na daƙiƙa 20 daga bidiyon, kuma yanzu kuna iya gani akan allon cewa an tura sigar farko ta aikace-aikacen. Duk waɗannan an yi su ta amfani da UI kawai.
Yanzu bari mu gwada na biyu version. Don yin wannan, na canza saƙon aikace-aikacen daga "Sannu, Kubernetes!" a kan "Sannu, Deployer!", tsarin ya ƙirƙiri wannan hoton kuma ya sanya shi a cikin rajistar Docker, bayan haka kawai mu sake danna maɓallin "Deploy" a cikin taga Deploymentctl. A wannan yanayin, ana ƙaddamar da log ɗin turawa ta atomatik kamar yadda ya faru lokacin tura sigar farko ta aikace-aikacen.
Umurnin ~ kubectl samun pods yana nuna cewa a halin yanzu akwai nau'ikan aikace-aikacen guda 2 da ke gudana, amma gaba yana nuna cewa har yanzu muna ci gaba da sigar 1.
Ma'auni mai ɗaukar nauyi yana jira don kammala binciken lafiya kafin a tura zirga-zirga zuwa sabon sigar. Bayan daƙiƙa 20, mun canza zuwa curl kuma ga cewa yanzu muna da nau'in 2 na aikace-aikacen, kuma an goge na farko.
Wannan shi ne ƙaddamar da aikace-aikacen "lafiya". Bari mu ga abin da zai faru idan don sabon nau'in aikace-aikacen na canza yanayin lafiya daga gaskiya zuwa ƙarya, wato, na yi ƙoƙarin tura aikace-aikacen da ba shi da lafiya wanda ya gaza duba lafiyar lafiya. Wannan na iya faruwa idan an yi wasu kurakuran daidaitawa a cikin aikace-aikacen a matakin haɓakawa, kuma an aika shi cikin samarwa ta wannan fom.
Kamar yadda kake gani, ƙaddamarwa yana tafiya ta duk matakan da ke sama kuma ~ kubectl samun kwasfan fayiloli yana nuna cewa duka kwas ɗin suna gudana. Amma ba kamar aikin da aka yi a baya ba, log ɗin yana nuna matsayin ƙarewar lokaci. Wato, saboda gaskiyar cewa binciken lafiyar ya gaza, ba za a iya tura sabon sigar aikace-aikacen ba. A sakamakon haka, ka ga cewa tsarin ya koma amfani da tsohuwar sigar aikace-aikacen, kuma an cire sabon sigar.
Abu mai kyau game da wannan shine cewa ko da kuna da adadin buƙatun lokaci guda da ke shigowa cikin aikace-aikacen, ba za su ma lura da lokacin raguwa ba yayin aiwatar da tsarin turawa. Idan kun gwada wannan aikace-aikacen ta amfani da tsarin Gatling, wanda ke aika da buƙatun da yawa gwargwadon iyawa, to babu ɗayan waɗannan buƙatun da za a yi watsi da su. Wannan yana nufin cewa masu amfani da mu ba za su ma lura da sabuntawar sigar a ainihin lokacin ba. Idan ya gaza, aiki zai ci gaba a kan tsohon sigar, idan ya yi nasara, masu amfani za su canza zuwa sabon sigar.
Abu daya ne kawai zai iya kasawa - idan gwajin lafiyar ya yi nasara, amma aikace-aikacen ya gaza da zarar an sanya nauyin aiki a kansa, wato rushewar zai faru ne kawai bayan an gama turawa. A wannan yanayin, dole ne ka koma da hannu zuwa tsohon sigar. Don haka, mun kalli yadda ake amfani da Kubernetes tare da kayan aikin buɗaɗɗen tushe da aka tsara don shi. Tsarin turawa zai yi sauƙi idan kun gina waɗannan kayan aikin cikin bututunku na Gina/Ƙara. A lokaci guda, don fara turawa, zaku iya amfani da ko dai na'urar mai amfani ko sarrafa cikakken wannan tsari ta amfani da, misali, sadaukar da kai.
Sabis ɗin Ginanmu zai ƙirƙiri hoton Docker, tura shi cikin Docker Hub ko duk wani rajista da kuke amfani da shi. Docker Hub yana goyan bayan ƙugiya ta yanar gizo, don haka za mu iya haifar da turawa ta nesa ta hanyar Deployer ta hanyar da aka nuna a sama. Ta wannan hanyar za ku iya sarrafa sarrafa aikin tura aikace-aikacen ku zuwa yuwuwar samarwa.
Bari mu ci gaba zuwa jigo na gaba - ƙaddamar da gungu na Kubernetes. Lura cewa umarnin kubectl umarni ne mai ƙima. Tare da ƙarin taimako, cikin sauƙi za mu iya ƙara adadin kwafi a cikin gungu na yanzu. Koyaya, a aikace, yawanci muna son ƙara yawan nodes maimakon kwasfa.
A lokaci guda, a lokacin lokutan aiki za ku iya buƙatar ƙarawa, kuma da dare, don rage farashin ayyukan Amazon, kuna iya buƙatar rage yawan lokutan aikace-aikacen aikace-aikacen. Wannan ba yana nufin cewa ƙididdige adadin kwas ɗin kawai zai wadatar ba, domin ko da ɗaya daga cikin nodes ɗin ba ya aiki, har yanzu za ku biya Amazon. Wato tare da zazzage kwasfa, za ku buƙaci auna adadin injinan da ake amfani da su.
Wannan na iya zama ƙalubale saboda ko muna amfani da Amazon ko wani sabis na girgije, Kubernetes bai san komai ba game da adadin injunan da ake amfani da su. Ba shi da kayan aiki wanda ke ba ka damar sikelin tsarin a matakin kumburi.
Don haka dole ne mu kula da nodes da pods. Za mu iya sauƙaƙe ƙaddamar da sabbin nodes ta amfani da AWS API da injunan ƙungiyar Scaling don saita adadin nodes na ma'aikatan Kubernetes. Hakanan zaka iya amfani da girgije-init ko rubutun makamancin haka don yin rajistar nodes a cikin gungu na Kubernetes.
Sabuwar na'ura ta fara a cikin ƙungiyar Scaling, ta fara kanta a matsayin kumburi, yin rajista a cikin rajistar maigidan kuma ta fara aiki. Bayan wannan, zaku iya ƙara adadin kwafi don amfani akan nodes da aka samu. Ƙaddamarwa yana buƙatar ƙarin ƙoƙari saboda kuna buƙatar tabbatar da cewa irin wannan matakin baya haifar da lalata aikace-aikacen da aka riga aka yi bayan kashe na'urori "marasa amfani". Don hana irin wannan yanayin, kuna buƙatar saita nodes zuwa matsayin "marasa shiri". Wannan yana nufin cewa tsoho mai tsarawa zai yi watsi da waɗannan nodes lokacin tsara kwas ɗin DaemonSet. Mai tsara jadawalin ba zai share komai daga waɗannan sabar ba, amma kuma ba zai ƙaddamar da sabon kwantena a wurin ba. Mataki na gaba shine fitar da kullin magudanar ruwa, wato, canja wurin kwas ɗin da ke gudana daga gare ta zuwa wata na'ura, ko wasu nodes waɗanda ke da isasshen ƙarfin wannan. Da zarar kun tabbatar da cewa babu sauran kwantena akan waɗannan nodes, zaku iya cire su daga Kubernetes. Bayan wannan, kawai za su daina wanzuwa don Kubernetes. Na gaba, kuna buƙatar amfani da API na AWS don musaki nodes ko injuna mara amfani.
Kuna iya amfani da Amdatu Scalerd, wani kayan aikin buɗaɗɗen tushe mai kama da AWS API. Yana ba da CLI don ƙara ko cire nodes a cikin tari. Siffar sa mai ban sha'awa ita ce ikon daidaita mai tsara jadawalin ta amfani da fayil ɗin json mai zuwa.
Lambar da aka nuna tana rage ƙarfin gungu da rabi yayin lokacin dare. Yana daidaita duka adadin kwafin da ake samu da kuma ƙarfin da ake so na gungu na Amazon. Yin amfani da wannan mai tsarawa zai rage adadin nodes da dare kuma ya kara su da safe, yana adana farashin amfani da nodes daga sabis na girgije kamar Amazon. Ba a gina wannan fasalin a cikin Kubernetes ba, amma amfani da Scalerd zai ba ku damar haɓaka wannan dandamali duk yadda kuke so.
Ina so in nuna cewa mutane da yawa suna gaya mani, "Wannan duk yana da kyau kuma yana da kyau, amma menene game da bayanan bayanana, wanda yawanci yake a tsaye?" Ta yaya za ku iya gudanar da wani abu kamar wannan a cikin yanayi mai ƙarfi kamar Kubernetes? A ganina, bai kamata ku yi wannan ba, bai kamata ku yi ƙoƙarin gudanar da rumbun adana bayanai a Kubernetes ba. Wannan yana yiwuwa a zahiri, kuma akwai koyawa akan Intanet akan wannan batu, amma zai dagula rayuwar ku da gaske.
Ee, akwai ra'ayi na shagunan dagewa a cikin Kubernetes, kuma kuna iya ƙoƙarin gudanar da shagunan bayanai kamar Mongo ko MySQL, amma wannan babban aiki ne mai wahala. Wannan shi ne saboda gaskiyar cewa ɗakunan ajiya na bayanai ba su da cikakken goyon bayan hulɗa tare da yanayi mai ƙarfi. Yawancin ma'ajin bayanai suna buƙatar tsari mai mahimmanci, gami da daidaitawar tari, ba sa son sarrafa atomatik da sauran abubuwa makamantansu.
Don haka, bai kamata ku rikitar da rayuwar ku ta ƙoƙarin gudanar da rumbun adana bayanai a Kubernetes ba. Shirya aikin su ta hanyar gargajiya ta amfani da ayyukan da aka saba kuma kawai samar da Kubernetes tare da ikon amfani da su.
Don kammala batun, Ina so in gabatar muku da dandalin Cloud RTI bisa Kubernetes, wanda ƙungiyara ke aiki a kai. Yana ba da tsarin shiga tsakani, aikace-aikace da saka idanu na tari, da sauran abubuwa masu amfani da yawa waɗanda zasu zo da amfani. Yana amfani da kayan aikin buɗe tushen iri-iri kamar Grafana don nuna sa ido.
Akwai tambaya game da dalilin da yasa ake amfani da ma'auni mai ɗaukar nauyin ha-proxy tare da Kubernetes. Tambaya mai kyau saboda a halin yanzu akwai matakan daidaita nauyi 2. Ayyukan Kubernetes har yanzu suna kan adiresoshin IP na kama-da-wane. Ba za ku iya amfani da su don tashar jiragen ruwa a kan na'urori masu masaukin baki na waje ba saboda idan Amazon ya yi amfani da girgijen girgije, adireshin zai canza. Wannan shine dalilin da ya sa muke sanya ha-proxy a gaban sabis - don ƙirƙirar tsari mai mahimmanci don zirga-zirga don sadarwa tare da Kubernetes.
Wata tambaya mai kyau ita ce ta yaya za ku iya kula da canje-canjen tsarin bayanai lokacin yin jigilar shuɗi / kore? Gaskiyar ita ce, ba tare da la'akari da amfani da Kubernetes ba, canza tsarin tsarin bayanai abu ne mai wuyar gaske. Kuna buƙatar tabbatar da cewa tsoho da sabon tsari sun dace, bayan haka zaku iya sabunta bayanan bayanan sannan kuma sabunta aikace-aikacen da kansu. Kuna iya zafi musanyawa bayanan bayanan sannan ku sabunta aikace-aikacen. Na san mutanen da suka ƙaddamar da sabon tarin tarin bayanai tare da sabon tsari, wannan zaɓi ne idan kuna da rumbun adana bayanai marasa tsari kamar Mongo, amma ba aiki mai sauƙi ba ne. Idan ba ku da ƙarin tambayoyi, na gode da kulawar ku!
Wasu tallace-tallace 🙂
Na gode da kasancewa tare da mu. Kuna son labaran mu? Kuna son ganin ƙarin abun ciki mai ban sha'awa? Goyon bayan mu ta hanyar ba da oda ko ba da shawara ga abokai, , analog na musamman na sabar matakin shigarwa, wanda mu muka ƙirƙira muku: (akwai tare da RAID1 da RAID10, har zuwa 24 cores kuma har zuwa 40GB DDR4).
Dell R730xd 2x mai rahusa a cibiyar bayanan Equinix Tier IV a Amsterdam? Nan kawai a cikin Netherlands! Dell R420 - 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB - daga $99! Karanta game da
source: www.habr.com