@sanyaymoe82: #အဲ့အကျီနဲ့ချစ်စရာလေးဆိုပီးလူသိများသွားတာလေ🤭💗

san yay moe( fan girl)🌻
san yay moe( fan girl)🌻
Open In TikTok:
Region: MM
Tuesday 08 September 2026 09:06:17 GMT
16174
1570
35
19

Music

Download

Comments

myint.myint.mar470
Myint Myint Mar :
ဘာဝတ်ဝတ်ကြည့်လို့ကောင်းတယ်လိုက်တယ်ခေတ်နဲ့ကိုက်ညီတယ်လေ
2026-09-08 15:30:15
2
khine..lay5
နတ်တလင်းသူလေးပါရှင့် :
ပလီတာလေးကပိုချစ်ဖို့ကောင်း
2026-09-14 16:19:38
1
snoopy3935
XING_x :
😁😁
2026-09-10 10:50:04
1
user267559268
Khin Khin :
🥰🥰🥰🥰🥰🥰
2026-09-09 03:52:58
1
ko.htun.htun.win72
Ko Htun Htun Win (သံပန်း) :
ဘယ်လိုဘဲဝတ်ဝတ်ချစ်စရာလေပါ
2026-09-09 17:01:50
1
maw.maw7449
Maw Maw :
🥰
2026-09-08 16:35:15
1
kyal6224
🍓 :
🥰
2026-09-08 10:59:21
2
sabelphyu503
နှင်းဆီမေ :
ချစ်စရာလေး
2026-09-08 12:00:11
1
yi.win4221
ဒေါ်ဟန်နွဲ့ :
2026-09-09 04:20:27
0
myint.myint.mar470
Myint Myint Mar :
စတိုင်လေ
2026-09-08 15:31:28
1
hla.hla850
Hla Hla :
🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰
2026-09-08 09:23:36
2
myint.myint.than7148
Myint Myint Than :
🥰
2026-09-08 10:48:37
2
user1815867496624
နွယ်💙💙 :
😁😁😁
2026-09-08 11:04:45
1
dawsansanhtay1
Daw San San Htay :
🥰🥰🥰🥰🥰🥰🥰
2026-09-08 11:55:38
1
user8848829153138
user8848829153138 :
🥰🥰🥰🥰🥰
2026-09-08 10:26:58
3
myinttarshin7
myinttarshin :
🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰
2026-09-08 10:43:20
2
lin.lin.6938
Lin Lin 6938 :
😂😂😂
2026-09-12 02:33:04
1
user884401804
win :
❤️❤️❤️
2026-09-15 13:04:04
1
zin.mar.lin761
Zin Mar lin :
🥰🥰🥰🥰🥰
2026-09-16 04:10:21
1
user7482027122587
မာမီစန်း :
🥰🥰🥰
2026-09-09 02:40:31
1
user174631617411
ကြည့်ကြည့်သန်း :
🥰🥰🥰
2026-09-09 09:53:57
0
ma.thidar.tun76
Ma Thidar Tun :
🥰🥰🥰🥰🥰
2026-09-09 05:15:11
0
user2695140634513
မသက်ထား :
😍😍😍
2026-09-08 09:08:07
1
To see more videos from user @sanyaymoe82, please go to the Tikwm homepage.

Other Videos

Terraform and Crossplane in Production! 🤯 Most teams treat Terraform and Crossplane like they have to pick one. That choice is what creates the bottleneck. Run everything through Terraform and your developers wait on a CI pipeline every time they need a test database or a cache. Let both tools manage the same resource, and you get something worse — Terraform sets the database one way, Crossplane quietly sets it back a minute later, and the two of them fight over it forever. So split the work by how often things change. Terraform builds the backbone. Cloud accounts, networks, permission policies, the Kubernetes clusters themselves. This stuff changes maybe twice a month, every change is big and risky, and a human should be reviewing all of it. Crossplane lives inside the cluster and handles what teams ask for every single day. A developer writes about ten lines of YAML saying they need a small Postgres for the payments service, commits it, and Crossplane builds it. Then it keeps checking that database forever. If somebody changes the config by hand, Crossplane puts it back. The rule that keeps them from fighting is simple. Every resource gets defined in exactly one place. Networks and clusters only in Terraform files. Databases and buckets only in Crossplane YAML. The tug of war can only happen if the same thing is written in both places. Do that and your platform team keeps a real gate on the risky stuff, while product teams stop filing tickets for a database. #Terraform #Crossplane #Kubernetes #DevOps #CloudNative
Terraform and Crossplane in Production! 🤯 Most teams treat Terraform and Crossplane like they have to pick one. That choice is what creates the bottleneck. Run everything through Terraform and your developers wait on a CI pipeline every time they need a test database or a cache. Let both tools manage the same resource, and you get something worse — Terraform sets the database one way, Crossplane quietly sets it back a minute later, and the two of them fight over it forever. So split the work by how often things change. Terraform builds the backbone. Cloud accounts, networks, permission policies, the Kubernetes clusters themselves. This stuff changes maybe twice a month, every change is big and risky, and a human should be reviewing all of it. Crossplane lives inside the cluster and handles what teams ask for every single day. A developer writes about ten lines of YAML saying they need a small Postgres for the payments service, commits it, and Crossplane builds it. Then it keeps checking that database forever. If somebody changes the config by hand, Crossplane puts it back. The rule that keeps them from fighting is simple. Every resource gets defined in exactly one place. Networks and clusters only in Terraform files. Databases and buckets only in Crossplane YAML. The tug of war can only happen if the same thing is written in both places. Do that and your platform team keeps a real gate on the risky stuff, while product teams stop filing tickets for a database. #Terraform #Crossplane #Kubernetes #DevOps #CloudNative

About