{"id":80532,"date":"2020-05-07T01:42:17","date_gmt":"2020-05-06T23:42:17","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem"},"modified":"2020-05-07T01:42:17","modified_gmt":"2020-05-06T23:42:17","slug":"problemy-s-dns-v-kubernetes-publichnyj-postmortem","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem","title":{"rendered":"Problemet me DNS n\u00eb Kubernetes. Postmortem publik","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Sh\u00ebnim:<\/b> kjo \u00ebsht\u00eb nj\u00eb p\u00ebrkthim i nj\u00eb postmortemi publik nga blogu inxhinierik i kompanis\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/preply.com\/\">Preply<\/a><\/noindex>. N\u00eb t\u00eb p\u00ebrshkruhet problemi me conntrack n\u00eb klasterin Kubernetes, i cili \u00e7oi n\u00eb nj\u00eb bllokim t\u00eb pjessh\u00ebm t\u00eb disa sh\u00ebrbimeve t\u00eb prodhimit.<\/i><\/p>\n<p>Ky artikull mund t\u00eb jet\u00eb i dobish\u00ebm p\u00ebr ata q\u00eb d\u00ebshirojn\u00eb t\u00eb din\u00eb pak m\u00eb shum\u00eb rreth postmortemeve ose t\u00eb parandalojn\u00eb disa probleme t\u00eb mundshme me DNS n\u00eb t\u00eb ardhmen.<\/p>\n<p><img decoding=\"async\" alt=\"Problemet me DNS n\u00eb Kubernetes. Postmortem publik\" src=\"\/wp-content\/uploads\/2020\/05\/0e841b0231f11171d52d82030cd1df21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Nuk \u00ebsht\u00eb DNS<br \/>\nNuk mund t\u00eb jet\u00eb q\u00eb \u00ebsht\u00eb DNS<br \/>\nIshte DNS<\/i><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Pak fjal\u00eb p\u00ebr postmortemet dhe proceset n\u00eb Preply<\/h2>\n<p><\/p>\n<blockquote><p>N\u00eb postmortem p\u00ebrshkruhet nj\u00eb d\u00ebshtim n\u00eb funksionim ose ndonj\u00eb ngjarje n\u00eb prodhim. Postmortemi p\u00ebrfshin nj\u00eb kronologji t\u00eb ngjarjeve, p\u00ebrshkrimin e ndikimit mbi p\u00ebrdoruesin, shkakun e par\u00eb, veprimet dhe m\u00ebsimet e nxjerra.<\/p>\n<p><i><noindex><a rel=\"nofollow\" href=\"http:\/\/shop.oreilly.com\/product\/0636920063964.do\">Seeking SRE<\/a><\/noindex><\/i><\/p><\/blockquote>\n<p>\nN\u00eb mbledhjet javore me pizz\u00eb, n\u00eb mesin e ekipit teknik, ne ndajm\u00eb informacion t\u00eb ndrysh\u00ebm. Nj\u00eb nga pjes\u00ebt m\u00eb t\u00eb r\u00ebnd\u00ebsishme t\u00eb k\u00ebtyre mbledhjeve jan\u00eb postmortemet, t\u00eb cilat shpesh shoq\u00ebrohen me prezantime dhe nj\u00eb analiz\u00eb m\u00eb t\u00eb thell\u00eb t\u00eb incidentit t\u00eb ndodhur. Edhe pse ne nuk 'duartrokasim' pas postmortemeve, ne p\u00ebrpiqemi t\u00eb zhvillojm\u00eb nj\u00eb kultur\u00eb 'pa faj\u00ebsim' (<noindex><a rel=\"nofollow\" href=\"https:\/\/codeascraft.com\/2012\/05\/22\/blameless-postmortems\/\">blameless culture<\/a><\/noindex>). Besojm\u00eb se shkruarja dhe paraqitja e postmortemeve mund t\u00eb na ndihmojn\u00eb (dhe jo vet\u00ebm ne) n\u00eb parandalimin e incidenteve t\u00eb ngjashme n\u00eb t\u00eb ardhmen, prandaj ne i ndajm\u00eb ato.<\/p>\n<blockquote><p>Personat e involvuar n\u00eb incident duhet t\u00eb ndihen se mund t\u00eb flasin holl\u00ebsisht p\u00ebr t\u00eb, pa frik\u00eb nga d\u00ebnimi ose hakmarrja. Asnj\u00eb faji! Shkruarja e postmortemit nuk \u00ebsht\u00eb nj\u00eb d\u00ebnim, por nj\u00eb mund\u00ebsi p\u00ebr t\u00eb m\u00ebsuar p\u00ebr t\u00eb gjith\u00eb kompanin\u00eb.<\/p>\n<p><i><noindex><a rel=\"nofollow\" href=\"https:\/\/devblog.axway.com\/dev-insights\/keep-calms-devops-s-sharing\/\">Keep CALMS &amp; DevOps: S is for Sharing<\/a><\/noindex><\/i><\/p><\/blockquote>\n<p><\/p>\n<h2>Problemet me DNS n\u00eb Kubernetes. Postmortem<\/h2>\n<p>\n<b>Data:<\/b> 28.02.2020<\/p>\n<p><b>Shkruar nga:<\/b> Amet U., Andrey S., Igor K., Alexey P.<\/p>\n<p><b>Statusi:<\/b> E p\u00ebrfunduar<\/p>\n<p><b>Shkurtimisht:<\/b> Disponueshm\u00ebria e pjesshme e DNS (26 minuta) p\u00ebr disa sh\u00ebrbime n\u00eb klasterin Kubernetes<\/p>\n<p><b>Ndikimi:<\/b> 15000 ngjarje t\u00eb humbura p\u00ebr sh\u00ebrbimet A, B dhe C<\/p>\n<p><b>Shkaku i par\u00eb:<\/b> Kube-proxy nuk arriti t\u00eb fshij\u00eb si\u00e7 duhet regjistrimin e vjet\u00ebr nga tabela conntrack, prandaj disa sh\u00ebrbime vazhduan t\u00eb p\u00ebrpiqen t\u00eb lidheshin me podet q\u00eb nuk ekzistonin<\/p>\n<pre><code class=\"bash\">E0228 20:13:53.795782       1 proxier.go:610] D\u00ebshtoi t\u00eb fshij\u00eb kube-system\/kube-dns:dns endpoint connections, gabim: gabim n\u00eb fshirjen e regjistrimeve conntrack p\u00ebr UDP peer {100.64.0.10, 100.110.33.231}, gabim: komanda conntrack ktheu: ...<\/code><\/pre>\n<p>\n<b>Gara:<\/b> P\u00ebr shkak t\u00eb ngarkes\u00ebs s\u00eb ul\u00ebt brenda klasterit Kubernetes, CoreDNS-autoscaler reduktoi numrin e pod\u00ebve n\u00eb deployment nga tre n\u00eb dy<\/p>\n<p><b>Zgjidhja:<\/b> Nj\u00eb tjet\u00ebr deployment aplikacioni inicoi krijimin e nodeve t\u00eb reja, CoreDNS-autoscaler shtoi m\u00eb shum\u00eb pod\u00eb p\u00ebr t\u00eb sh\u00ebrbyer klasterin, \u00e7far\u00eb shkaktoi p\u00ebrshkrimin e tabel\u00ebs conntrack<\/p>\n<p><b>Zbulimi:<\/b> Monitorimi Prometheus zbuloi nj\u00eb num\u00ebr t\u00eb madh t\u00eb gabimeve 5xx p\u00ebr sh\u00ebrbimet A, B dhe C dhe inicioi nj\u00eb thirrje p\u00ebr inxhinier\u00ebt n\u00eb detyr\u00eb<\/p>\n<p><img decoding=\"async\" alt=\"Problemet me DNS n\u00eb Kubernetes. Postmortem publik\" src=\"\/wp-content\/uploads\/2020\/05\/14a2216ce7564f05c6dc3e7cb1c3dbb0.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Gabimet 5xx n\u00eb Kibana<\/i><\/p>\n<h3>Veprime<\/h3>\n<p><\/p>\n<p>Veprimi<br \/>\nTipo<br \/>\nP\u00ebrgjegj\u00ebs<br \/>\nDetyra<\/p>\n<p>\u00c7aktivizoni autoscaler-in p\u00ebr CoreDNS<br \/>\nparandaloni.<br \/>\nAmet U.<br \/>\nDEVOPS-695<\/p>\n<p>Instaloni serverin DNS memorizues<br \/>\npak\u00ebsimet.<br \/>\nMax V.<br \/>\nDEVOPS-665<\/p>\n<p>Konfiguroni monitorimin conntrack<br \/>\nparandaloni.<br \/>\nAmet U.<br \/>\nDEVOPS-674<\/p>\n<p><\/p>\n<h3>M\u00ebsimet e nxjerra<\/h3>\n<p>\n<b>\u00c7far\u00eb shkoi mir\u00eb:<\/b><\/p>\n<ul>\n<li>Monitorimi funksionoi sakt\u00eb. Reagimi ishte i shpejt\u00eb dhe i organizuar<\/li>\n<li>Nuk u p\u00ebrball\u00ebm me asnj\u00eb kufizim n\u00eb node<\/li>\n<\/ul>\n<p><b>\u00c7far\u00eb nuk shkoi si\u00e7 duhet:<\/b><\/p>\n<ul>\n<li>Akoma nj\u00eb shkak i par\u00eb i panjohur, duke dukur si <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/issues\/66651\">nj\u00eb bug specifik<\/a><\/noindex> n\u00eb conntrack<\/li>\n<li>T\u00eb gjitha veprimet korrigjojn\u00eb vet\u00ebm pasojat, jo shkakun e par\u00eb (bugun)<\/li>\n<li>E dinim se nj\u00eb ose m\u00eb von\u00eb mund t\u00eb kishim probleme me DNS, por nuk e prioritizuam detyr\u00ebn<\/li>\n<\/ul>\n<p>\n<b>Ku pat\u00ebm fat:<\/b><\/p>\n<ul>\n<li>Nj\u00eb tjet\u00ebr ndihm\u00ebs inicoi CoreDNS-autoscaler, i cili p\u00ebrshkroi tabel\u00ebn conntrack<\/li>\n<li>Ky bug preku vet\u00ebm nj\u00eb pjes\u00eb t\u00eb sh\u00ebrbimeve<\/li>\n<\/ul>\n<p><\/p>\n<h3>Kronologjia (EET)<\/h3>\n<p><\/p>\n<p>Koha<br \/>\nVeprimi<\/p>\n<p>22:13<br \/>\nCoreDNS-autoscaler reduktoi numrin e pod\u00ebve nga tre n\u00eb dy<\/p>\n<p>22:18<br \/>\nInxhinier\u00ebt n\u00eb detyr\u00eb filluan t\u00eb merrnin telefonata nga sistemi i monitorimit<\/p>\n<p>22:21<br \/>\nInxhinier\u00ebt n\u00eb detyr\u00eb filluan t\u00eb hetojn\u00eb shkakun e gabimeve<\/p>\n<p>22:39<br \/>\nInxhinier\u00ebt n\u00eb detyr\u00eb filluan t\u00eb rikthejn\u00eb nj\u00eb nga sh\u00ebrbimet e fundit n\u00eb versionin e m\u00ebparsh\u00ebm<\/p>\n<p>22:40<br \/>\nGabimet 5xx ndaluan s\u00eb shfaquri, situata u stabilizua<\/p>\n<p><\/p>\n<ul>\n<li><b>Koha deri n\u00eb zbulim:<\/b> 4 minuta<\/li>\n<li><b>Koha deri n\u00eb veprim:<\/b> 21 minuta<\/li>\n<li><b>Koha deri n\u00eb korrigjim:<\/b> 1 minut\u00eb<\/li>\n<\/ul>\n<p><\/p>\n<h3>Informacione shtes\u00eb<\/h3>\n<p><\/p>\n<ul>\n<li>Loget e CoreDNS:\n<pre><code class=\"bash\">I0228 20:13:53.507780       1 event.go:221] Ngjarja(v1.ObjectReference{Lloj:&quot;Deployment&quot;, Emri:&quot;coredns&quot;, UID:&quot;2493eb55-3dc0-11ea-b3a2-02bb48f8c230&quot;, APIVersion:&quot;apps\/v1&quot;, ResourceVersion:&quot;132690686&quot;, FieldPath:&quot;&quot;}): tipi: 'Normal' arsye: 'ScalingReplicaSet' M\u00ebkatohet seti i replikave coredns-6cbb6646c9 n\u00eb 2<\/code><\/pre>\n<\/li>\n<li>Linket n\u00eb Kibana (t\u00eb prer\u00eb), Grafana (t\u00eb prer\u00eb)<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.projectcalico.org\/when-linux-conntrack-is-no-longer-your-friend\/\">Ku Linux conntrack nuk \u00ebsht\u00eb m\u00eb miku juaj<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/blog\/2019\/03\/29\/kube-proxy-subtleties-debugging-an-intermittent-connection-reset\/\">N\u00ebnkuptimet e kube-proxy: Debugging nj\u00eb rivendosje t\u00eb lidhjes<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.weave.works\/blog\/racy-conntrack-and-dns-lookup-timeouts\">Konfliktet e conntrack dhe koh\u00ebzgjatjet e k\u00ebrkesave DNS<\/a><\/noindex><\/li>\n<\/ul>\n<p>\nP\u00ebr t\u00eb minimizuar p\u00ebrdorimin e procesorit, b\u00ebrthama Linux p\u00ebrdor nj\u00eb gj\u00eb si conntrack. N\u00ebse e shqyrtojm\u00eb shkurt, kjo \u00ebsht\u00eb nj\u00eb utilitare q\u00eb p\u00ebrmban nj\u00eb list\u00eb t\u00eb regjistrimeve NAT, t\u00eb cilat mbahen n\u00eb nj\u00eb tabel\u00eb t\u00eb ve\u00e7ant\u00eb. Kur paketa e ardhshme vjen nga e nj\u00ebjta pod n\u00eb t\u00eb nj\u00ebjtin pod si m\u00eb par\u00eb, adresa p\u00ebrfundimtare IP nuk do t\u00eb llogaritet nga e para, por do t\u00eb merret nga tabela conntrack.<br \/>\n<img decoding=\"async\" alt=\"Problemet me DNS n\u00eb Kubernetes. Postmortem publik\" src=\"\/wp-content\/uploads\/2020\/05\/895db4057ee0912e16e017c6e3134162.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Si funksionon conntrack<\/i><\/p>\n<h2>P\u00ebrfundimet<\/h2>\n<p>\nKy ishte nj\u00eb shembull i nj\u00eb prej postmortem-\u00ebve tona me disa lidhje t\u00eb dobishme. Konkretisht n\u00eb k\u00ebt\u00eb artikull, ne ndajm\u00eb informacion q\u00eb mund t\u00eb jet\u00eb i dobish\u00ebm p\u00ebr kompanit\u00eb e tjera. K\u00ebtu \u00ebsht\u00eb arsyja pse ne nuk kemi frik\u00eb t\u00eb b\u00ebjm\u00eb gabime dhe pse ne e b\u00ebjm\u00eb nj\u00eb prej postmortem-\u00ebve tona publike. K\u00ebtu jan\u00eb disa postmortem t\u00eb tjera interesante publikisht:<\/p>\n<ul>\n<li>GitLab: <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/blog\/2017\/02\/10\/postmortem-of-database-outage-of-january-31\/\">Postmortem-i i nd\u00ebrprerjes s\u00eb databaz\u00ebs m\u00eb 31 janar<\/a><\/noindex><\/li>\n<li>Dropbox: <noindex><a rel=\"nofollow\" href=\"https:\/\/dropbox.tech\/infrastructure\/outage-post-mortem\">Postmortem-i i nd\u00ebrprerjes<\/a><\/noindex><\/li>\n<li>Spotify: <noindex><a rel=\"nofollow\" href=\"https:\/\/labs.spotify.com\/2017\/03\/31\/spotifys-lovehate-relationship-with-dns\/\">Marr\u00ebdh\u00ebnia Love\/Hate e Spotify me DNS<\/a><\/noindex><\/li>\n<li>Shum\u00eb t\u00eb tjera nga <noindex><a rel=\"nofollow\" href=\"https:\/\/gist.github.com\/cheapRoc\/d9e73fe05480330c1e36410cbdf0e867\">ky gist<\/a><\/noindex> dhe repository <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/hjacobs\/kubernetes-failure-stories\">Historit\u00eb e D\u00ebshtimeve n\u00eb Kubernetes<\/a><\/noindex><\/li>\n<li>Po ashtu <noindex><a rel=\"nofollow\" href=\"https:\/\/landing.google.com\/sre\/sre-book\/chapters\/postmortem\/\">shembull<\/a><\/noindex> postmortemi publik me SRE Book<\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/500346\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0433\u043e \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c\u0430 \u0438\u0437 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043d\u043e\u0433\u043e \u0431\u043b\u043e\u0433\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Preply. \u0412 \u043d\u0435\u043c \u043e\u043f\u0438\u0441\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0441 conntrack \u0432 Kubernetes-\u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0435, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u0440\u0438\u0432\u0435\u043b\u0430 \u043a \u0447\u0430\u0441\u0442\u0438\u0447\u043d\u043e\u043c\u0443 \u043f\u0440\u043e\u0441\u0442\u043e\u044e \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u043f\u0440\u043e\u0434\u0430\u043a\u0448\u043d\u0430. \u0414\u0430\u043d\u043d\u0430\u044f \u0441\u0442\u0430\u0442\u044c\u044f \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c \u043f\u043e\u043b\u0435\u0437\u043d\u043e\u0439 \u0442\u0435\u043c, \u043a\u0442\u043e \u0445\u043e\u0447\u0435\u0442 \u0443\u0437\u043d\u0430\u0442\u044c \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0431\u043e\u043b\u044c\u0448\u0435 \u043e \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c\u0430\u0445 \u0438\u043b\u0438 \u043f\u0440\u0435\u0434\u043e\u0442\u0432\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0441 DNS \u0432 \u0431\u0443\u0434\u0443\u0449\u0435\u043c. \u042d\u0442\u043e \u043d\u0435 DNS \u041d\u0435 \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":80533,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-80532","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0433\u043e \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c\u0430 \u0438\u0437 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043d\u043e\u0433\u043e \u0431\u043b\u043e\u0433\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Preply.\" \/>\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\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\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\udd47\u041f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0441 DNS \u0432 Kubernetes. \u041f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0439 \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0433\u043e \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c\u0430 \u0438\u0437 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043d\u043e\u0433\u043e \u0431\u043b\u043e\u0433\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Preply.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem\" \/>\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=\"2020-05-06T23:42:17+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-06T23:42:17+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\udd47Problemet me DNS n\u00eb Kubernetes. Postmortem publik | ProHoster","description":"Sh\u00ebnim. p\u00ebrkthimi: kjo \u00ebsht\u00eb p\u00ebrkthimi i nj\u00eb post-mortem publik nga blogu inxhinierik i kompanis\u00eb Preply.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem","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\udd47\u041f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0441 DNS \u0432 Kubernetes. \u041f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0439 \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c | ProHoster","og:description":"\u041f\u0440\u0438\u043c. \u043f\u0435\u0440\u0435\u0432.: \u044d\u0442\u043e \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u043e\u0433\u043e \u043f\u043e\u0441\u0442\u043c\u043e\u0440\u0442\u0435\u043c\u0430 \u0438\u0437 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043d\u043e\u0433\u043e \u0431\u043b\u043e\u0433\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Preply.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem","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":"2020-05-06T23:42:17+00:00","article:modified_time":"2020-05-06T23:42:17+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"80532","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":"","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 16:16:27","updated":"2022-09-28 05:25:18","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/80532","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=80532"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/80532\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/80533"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=80532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=80532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=80532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}