@da_lika1:

DaDa
DaDa
Open In TikTok:
Region: KH
Monday 15 June 2026 03:58:07 GMT
7775
704
20
13

Music

Download

Comments

san.tk62
San Tk :
Sart o♥️🥰🥰
2026-06-27 00:16:39
0
pholy624
Pholy :
ស្អាតណាស់ប៊ី🥰
2026-06-16 12:30:19
1
.bongla.5
🥰 បងឡា 🥰 :
វ៉ាវៗ😳
2026-06-15 04:09:25
0
bro.nang8931
Bro Nang :
🥰
2026-06-20 01:53:07
0
raksazkp
🦋Raksa♡‿♡cute🦋 :
🥰🥰🥰
2026-06-15 13:30:52
0
user77704655
Seng Darong :
😍😍😍
2026-06-15 13:09:41
0
chhai884
Da Ra កំពត :
❤️❤️❤️
2026-06-15 05:26:20
0
user965786180532
user96578618053 បងសនា :
🥰🥰🥰
2026-06-15 05:16:28
0
ig.chanthy.pv
FB:Chanthy Psk :
🥰🥰🥰
2026-06-15 04:28:12
0
vichhai.voeun
Vichhai Voeun :
🥰🥰🥰
2026-06-15 04:27:32
0
user2700541722887
Nhem Nou :
❤️❤️❤️
2026-06-15 04:12:21
0
sekato47
Sekato :
😳😳🥰🥰🥰🥰
2026-06-15 04:08:16
0
tiger787761
Ti Ger :
🥰🥰🥰
2026-06-15 04:04:09
0
tep.bro
𝐏𝐚𝐫𝐢𝐬 :
😳😳😳
2026-06-15 04:03:36
0
you__1627
កន ផុន :
😱😱😱
2026-06-15 04:02:04
0
____._____.p___
🐅____…….—-_____ÿæ Pħęĩň___—-. :
💗💗💗
2026-06-15 04:01:28
0
kakada412
kakada412 :
❤️❤️❤️
2026-06-15 04:00:49
0
mach.rotha8
Mach Rotha :
💗💗💗
2026-06-15 03:59:52
0
toungsaro
toungsaro :
❤️❤️
2026-06-24 05:08:52
1
To see more videos from user @da_lika1, please go to the Tikwm homepage.

Other Videos

K8s Debugging: Fixing Unreachable Cluster DNS!   When a Kubernetes pod loses the ability to resolve names, your first line of defense is checking the health of the CoreDNS pods inside the kube-system namespace. If these pods are crashing or stuck in a restart loop, the culprit is almost always a broken Corefile configuration. The Corefile orchestrates your entire cluster's DNS routing through critical plugins: kubernetes for mapping internal service names, forward for routing public traffic to upstream resolvers, cache for memory efficiency, and loop to detect and kill infinite routing loops. Even a minor syntax error or typo in this file will trigger a catastrophic, cluster-wide DNS blackout. If CoreDNS is perfectly healthy but your application pods still can't reach it, a restrictive Network Policy is likely blocking the traffic. Applying a global
K8s Debugging: Fixing Unreachable Cluster DNS! When a Kubernetes pod loses the ability to resolve names, your first line of defense is checking the health of the CoreDNS pods inside the kube-system namespace. If these pods are crashing or stuck in a restart loop, the culprit is almost always a broken Corefile configuration. The Corefile orchestrates your entire cluster's DNS routing through critical plugins: kubernetes for mapping internal service names, forward for routing public traffic to upstream resolvers, cache for memory efficiency, and loop to detect and kill infinite routing loops. Even a minor syntax error or typo in this file will trigger a catastrophic, cluster-wide DNS blackout. If CoreDNS is perfectly healthy but your application pods still can't reach it, a restrictive Network Policy is likely blocking the traffic. Applying a global ""default deny egress"" policy instantly cuts off a pod's outbound communications, including its critical path to the cluster DNS. To fix this, you must explicitly inject an egress rule allowing outbound traffic on port 53 for both UDP and TCP protocols. Because Kubernetes network policies cannot target a cluster Service object directly, you must configure your rule to allow traffic either directly to the CoreDNS pods via their selector labels or to the specific cluster DNS IP address using an IP block. Save this for your next K8s outage. Or your next interview. ▶️ Part 1: https://youtube.com/shorts/J-zSd2lsMaI ▶️ Part 3: https://youtube.com/shorts/Tieokbq9jWg #Kubernetes #K8s #CoreDNS #NetworkPolicy #DevOps #SRE #Troubleshooting #SysAdmin #CloudNative #PlatformEngineering #Networking #TechTips #Backend

About