{"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\/ro\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem","title":{"rendered":"Probleme DNS \u00een Kubernetes. Post-mortem public","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i><b>Not\u0103 de traducere:<\/b> aceasta este traducerea unui post-mortem public din blogul ingineresc al companiei <noindex><a rel=\"nofollow\" href=\"https:\/\/preply.com\/\">Preply<\/a><\/noindex>. \u00cen acesta se descrie problema cu conntrack \u00een clusterul Kubernetes, care a dus la o \u00eentrerupere par\u021bial\u0103 a unor servicii de produc\u021bie.<\/i><\/p>\n<p>Acest articol poate fi util celor care doresc s\u0103 afle mai multe despre post-mortemuri sau s\u0103 previn\u0103 anumite probleme poten\u021biale cu DNS \u00een viitor.<\/p>\n<p><img decoding=\"async\" alt=\"Probleme DNS \u00een Kubernetes. Post-mortem public\" src=\"\/wp-content\/uploads\/2020\/05\/0e841b0231f11171d52d82030cd1df21.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Nu este DNS<br \/>\nNu poate fi c\u0103 este DNS<br \/>\nA fost DNS<\/i><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Despre post-mortemuri \u0219i procesele din Preply<\/h2>\n<p><\/p>\n<blockquote><p>Post-mortemul descrie o defec\u021biune \u00een func\u021bionare sau un eveniment \u00een productie. Post-mortemul include o cronologie a evenimentelor, descrierea impactului asupra utilizatorului, cauza r\u0103d\u0103cin\u0103, ac\u021biunile \u0219i lec\u021biile \u00eenv\u0103\u021bate.<\/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>\nLa \u00eent\u00e2lnirile s\u0103pt\u0103m\u00e2nale cu pizza, \u00een cercul echipei tehnice, \u00eemp\u0103rt\u0103\u0219im diverse informa\u021bii. Una dintre p\u0103r\u021bile cele mai importante ale acestor \u00eent\u00e2lniri sunt post-mortemurile, care sunt cel mai adesea \u00eenso\u021bite de o prezentare cu diapozitive \u0219i o analiz\u0103 mai profund\u0103 a incidentului petrecut. De\u0219i nu \u00abaplauz\u0103m\u00bb dup\u0103 post-mortemuri, ne str\u0103duim s\u0103 dezvolt\u0103m o cultur\u0103 \u00abf\u0103r\u0103 acuza\u021bii\u00bb (<noindex><a rel=\"nofollow\" href=\"https:\/\/codeascraft.com\/2012\/05\/22\/blameless-postmortems\/\">blameless culture<\/a><\/noindex>). Credem c\u0103 redactarea \u0219i prezentarea post-mortemurilor ne poate ajuta (\u0219i nu numai) s\u0103 prevenim incidente similare \u00een viitor, aceasta este \u0219i motivul pentru care le \u00eemp\u0103rt\u0103\u0219im.<\/p>\n<blockquote><p>Persoanele implicate \u00een incident trebuie s\u0103 simt\u0103 c\u0103 pot povesti \u00een detaliu despre acesta, f\u0103r\u0103 teama de pedeaps\u0103 sau r\u0103zbunare. Nicio mustrare! Redactarea post-mortemului nu este o pedeaps\u0103, ci o oportunitate de \u00eenv\u0103\u021bare pentru \u00eentreaga companie.<\/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 este pentru \u00cemp\u0103rt\u0103\u0219ire<\/a><\/noindex><\/i><\/p><\/blockquote>\n<p><\/p>\n<h2>Probleme DNS \u00een Kubernetes. Post-mortem<\/h2>\n<p>\n<b>Data:<\/b> 28.02.2020<\/p>\n<p><b>Autori:<\/b> Amet U., Andrei S., Igor K., Alexei P.<\/p>\n<p><b>Status:<\/b> Finalizat<\/p>\n<p><b>Pe scurt:<\/b> Ne disponibilitate par\u021bial\u0103 DNS (26 min) pentru unele servicii din clusterul Kubernetes<\/p>\n<p><b>Impact:<\/b> 15000 evenimente pierdute pentru serviciile A, B \u0219i C<\/p>\n<p><b>Cauza r\u0103d\u0103cin\u0103:<\/b> Kube-proxy nu a reu\u0219it s\u0103 \u0219tearg\u0103 corect \u00eenregistrarea veche din tabelul conntrack, astfel c\u0103 unele servicii \u00eencercau \u00een continuare s\u0103 se conecteze la podurile inexistente<\/p>\n<pre><code class=\"bash\">E0228 20:13:53.795782       1 proxier.go:610] E\u0219ec la \u0219tergerea kube-system\/kube-dns:dns endpoint connections, eroare: eroare la \u0219tergerea intr\u0103rilor conntrack pentru UDP peer {100.64.0.10, 100.110.33.231}, eroare: comanda conntrack a returnat: ...<\/code><\/pre>\n<p>\n<b>Declan\u0219ator:<\/b> Din cauza \u00eenc\u0103rc\u0103rii reduse \u00een interiorul clusterului Kubernetes, CoreDNS-autoscaler a redus num\u0103rul de poduri din implementare de la trei la dou\u0103<\/p>\n<p><b>Solu\u021bia:<\/b> O nou\u0103 desf\u0103\u0219urare a aplica\u021biei a ini\u021biat crearea de noduri noi, CoreDNS-autoscaler a ad\u0103ugat mai multe poduri pentru a sus\u021bine clusterul, ceea ce a provocat rescrierea tabelului conntrack<\/p>\n<p><b>Detectare:<\/b> Monitorizarea Prometheus a detectat un num\u0103r mare de erori 5xx pentru serviciile A, B \u0219i C \u0219i a ini\u021biat un apel c\u0103tre inginerii de gard\u0103<\/p>\n<p><img decoding=\"async\" alt=\"Probleme DNS \u00een Kubernetes. Post-mortem public\" src=\"\/wp-content\/uploads\/2020\/05\/14a2216ce7564f05c6dc3e7cb1c3dbb0.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Erori 5xx \u00een Kibana<\/i><\/p>\n<h3>Ac\u021biuni<\/h3>\n<p><\/p>\n<p>Ac\u021biune<br \/>\nTip<br \/>\nResponsabil<br \/>\nSarcin\u0103<\/p>\n<p>Dezactiveaz\u0103 autoscalarea pentru CoreDNS<br \/>\nprevine.<br \/>\nAmet U.<br \/>\nDEVOPS-695<\/p>\n<p>Instaleaz\u0103 serverul DNS de caching<br \/>\nreduce.<br \/>\nMax V.<br \/>\nDEVOPS-665<\/p>\n<p>Configureaz\u0103 monitorizarea conntrack<br \/>\nprevine.<br \/>\nAmet U.<br \/>\nDEVOPS-674<\/p>\n<p><\/p>\n<h3>Lec\u021biile \u00eenv\u0103\u021bate<\/h3>\n<p>\n<b>Ce a mers bine:<\/b><\/p>\n<ul>\n<li>Monitorizarea a func\u021bionat corespunz\u0103tor. R\u0103spunsul a fost rapid \u0219i bine organizat<\/li>\n<li>Nu ne-am lovit de niciun limit\u0103 pe noduri<\/li>\n<\/ul>\n<p><b>Ce a fost \u00een neregul\u0103:<\/b><\/p>\n<ul>\n<li>\u00cenc\u0103 nu se cunoa\u0219te cauza real\u0103, pare a fi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kubernetes\/issues\/66651\">o eroare specific\u0103<\/a><\/noindex> \u00een conntrack<\/li>\n<li>Toate ac\u021biunile corecteaz\u0103 doar efectele, nu cauza primar\u0103 (eroarea)<\/li>\n<li>\u0218tiam c\u0103 mai devreme sau mai t\u00e2rziu vom putea avea probleme cu DNS, dar nu am prioritizat sarcinile<\/li>\n<\/ul>\n<p>\n<b>Unde ne-a mers bine:<\/b><\/p>\n<ul>\n<li>O nou\u0103 desf\u0103\u0219urare a activat CoreDNS-autoscaler, care a rescris tabelul conntrack<\/li>\n<li>Aceast\u0103 eroare a afectat doar o parte a serviciilor<\/li>\n<\/ul>\n<p><\/p>\n<h3>Cronologia (EET)<\/h3>\n<p><\/p>\n<p>Timp<br \/>\nAc\u021biune<\/p>\n<p>22:13<br \/>\nCoreDNS-autoscaler a redus num\u0103rul de poduri de la trei la dou\u0103<\/p>\n<p>22:18<br \/>\nInginerii de gard\u0103 au \u00eenceput s\u0103 primeasc\u0103 apeluri din partea sistemului de monitorizare<\/p>\n<p>22:21<br \/>\nInginerii de gard\u0103 au \u00eenceput s\u0103 investigheze cauza erorilor<\/p>\n<p>22:39<br \/>\nInginerii de gard\u0103 au \u00eenceput s\u0103 revin\u0103 asupra uneia dintre ultimele servicii la versiunea anterioar\u0103<\/p>\n<p>22:40<br \/>\nErorile 5xx au \u00eencetat s\u0103 apar\u0103, situa\u021bia s-a stabilizat<\/p>\n<p><\/p>\n<ul>\n<li><b>Timpul p\u00e2n\u0103 la detectare:<\/b> 4 min<\/li>\n<li><b>Timpul p\u00e2n\u0103 la ac\u021biuni:<\/b> 21 min<\/li>\n<li><b>Timpul p\u00e2n\u0103 la corectare:<\/b> 1 min<\/li>\n<\/ul>\n<p><\/p>\n<h3>Informa\u021bii suplimentare<\/h3>\n<p><\/p>\n<ul>\n<li>Jurnalele CoreDNS:\n<pre><code class=\"bash\">I0228 20:13:53.507780       1 event.go:221] Event(v1.ObjectReference{Kind:\"Deployment\", Namespace:\"kube-system\", Name:\"coredns\", UID:\"2493eb55-3dc0-11ea-b3a2-02bb48f8c230\", APIVersion:\"apps\/v1\", ResourceVersion:\"132690686\", FieldPath:\"\"}): type: 'Normal' reason: 'ScalingReplicaSet' Replica set coredns-6cbb6646c9 a fost redus la 2<\/code><\/pre>\n<\/li>\n<li>Linkuri c\u0103tre Kibana (t\u0103iat), Grafana (t\u0103iat)<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.projectcalico.org\/when-linux-conntrack-is-no-longer-your-friend\/\">Unde Linux conntrack nu mai este prietenul t\u0103u<\/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\/\">Subtilit\u0103\u021bi kube-proxy: Debbuging reset\u0103rilor intermitente ale conexiunii<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.weave.works\/blog\/racy-conntrack-and-dns-lookup-timeouts\">Conntrack instabil \u0219i timpii de a\u0219teptare DNS<\/a><\/noindex><\/li>\n<\/ul>\n<p>\nPentru a minimiza utilizarea procesorului, nucleul Linux utilizeaz\u0103 ceva numit conntrack. Pe scurt, aceasta este o unealt\u0103 care con\u021bine o list\u0103 de \u00eenregistr\u0103ri NAT, p\u0103strate \u00eentr-un tabel special. C\u00e2nd urm\u0103torul pachet vine din acelea\u0219i poduri \u00een acela\u0219i pod ca \u00eenainte, adresa IP final\u0103 nu va fi calculat\u0103 din nou, ci va fi preluat\u0103 din tabelul conntrack.<br \/>\n<img decoding=\"async\" alt=\"Probleme DNS \u00een Kubernetes. Post-mortem public\" src=\"\/wp-content\/uploads\/2020\/05\/895db4057ee0912e16e017c6e3134162.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Cum func\u021bioneaz\u0103 conntrack<\/i><\/p>\n<h2>Concluzii<\/h2>\n<p>\nAceasta a fost un exemplu din unul dintre postmortem-urile noastre, cu c\u00e2teva linkuri utile. \u00cen acest articol, \u00eemp\u0103rt\u0103\u0219im informa\u021bii care pot fi de folos altor companii. De aceea, nu ne temem s\u0103 facem gre\u0219eli \u0219i de aceea am f\u0103cut unul dintre postmortem-urile noastre public. Iat\u0103 c\u00e2teva alte postmortem-uri publice interesante:<\/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 al \u00eentreruperii bazei de date din 31 ianuarie<\/a><\/noindex><\/li>\n<li>Dropbox: <noindex><a rel=\"nofollow\" href=\"https:\/\/dropbox.tech\/infrastructure\/outage-post-mortem\">Postmortem al \u00eentreruperii<\/a><\/noindex><\/li>\n<li>Spotify: <noindex><a rel=\"nofollow\" href=\"https:\/\/labs.spotify.com\/2017\/03\/31\/spotifys-lovehate-relationship-with-dns\/\">Rela\u021bia de dragoste\/ur\u0103 a Spotify cu DNS-ul<\/a><\/noindex><\/li>\n<li>Multe alte postmortem-uri din <noindex><a rel=\"nofollow\" href=\"https:\/\/gist.github.com\/cheapRoc\/d9e73fe05480330c1e36410cbdf0e867\">acest gist<\/a><\/noindex> \u0219i repository <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/hjacobs\/kubernetes-failure-stories\">Povestiri despre e\u0219ecurile Kubernetes<\/a><\/noindex><\/li>\n<li>De asemenea, <noindex><a rel=\"nofollow\" href=\"https:\/\/landing.google.com\/sre\/sre-book\/chapters\/postmortem\/\">exemplu<\/a><\/noindex> postmortem public cu SRE Book<\/li>\n<\/ul>\n<p>Sursa: <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.2.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\/ro\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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\udd47Probleme cu DNS \u00een Kubernetes. Postmortem public | ProHoster","description":"Not\u0103 de traducere: acesta este un traducere a postmortem-ului public din blogul ingineresc al companiei Preply.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/problemy-s-dns-v-kubernetes-publichnyj-postmortem","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/80532","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=80532"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/80532\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/80533"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=80532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=80532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=80532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}