Kidong Lee

On August 10th at #UbuConKorea, I'm going to present about the topic: "Building container images without Dockerfile" It does sound trolling, right? 🤣 While it's very true, I'm going to discuss which options are available to build container images from the developer productivity perspectives. During the session, I'd also like to touch how .NET Aspire makes our lives easier to build and deploy cloud-native apps. I'll see you there! #cloudnative #dotnet #aspire #containers #dockerfile #msbuild #docker #dockercompose #aspirate #chiseledcontainer

75

Curious about Cloud Native Buildpacks and how they can help you? Then this video is for you. Heroku Architect and CNB Co-Founder Terence Lee will give you a comprehensive understanding of what Cloud Native Buildpacks are, and when and why you should consider using them. Watch now!

42

𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞: 𝐒𝐢𝐦𝐩𝐥𝐢𝐟𝐲 𝐘𝐨𝐮𝐫 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭𝐬 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 -> https://lnkd.in/gj-tfEyH Ever deploy the same app to different environments (dev, test, prod) and tweak configs each time? There's a better way! Meet Kustomize, a powerful tool for customizing Kubernetes deployments without code changes. Think of it like outfitting your app for different occasions. 𝐁𝐚𝐬𝐞 𝐌𝐚𝐧𝐢𝐟𝐞𝐬𝐭: Your app's core configuration, the basic outfit. 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐚𝐭𝐢𝐨𝐧: The magic touch! Patches and overlays customize the base for each environment, like adding a blazer for production. 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 𝐨𝐟 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞: 𝐑𝐞𝐝𝐮𝐜𝐞𝐝 𝐃𝐮𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧: One base manifest, customized for each environment. No more copy-pasting! 𝐂𝐥𝐞𝐚𝐧 𝐂𝐨𝐝𝐞: Keep your app code clean and separate from environment-specific configs. 𝐃𝐞𝐜𝐥𝐚𝐫𝐚𝐭𝐢𝐯𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Simply define what you want, and Kustomize takes care of the details. 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞 𝐢𝐬 𝐩𝐞𝐫𝐟𝐞𝐜𝐭 𝐟𝐨𝐫: Developers who want clean separation of concerns. Ops teams who need to manage deployments across environments. Is Kustomize the new Helm?  Not quite! While both manage deployments, Kustomize focuses on configuration, while Helm offers templating and package management for complex deployments. Think of Kustomize as your go-to tool for configuration customization, and Helm for full-fledged deployment management. Want to learn more? Dive deeper into Kustomize documentation and explore its capabilities! 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 -> https://lnkd.in/gj-tfEyH  #kubernetes #kustomize #devops #cloudnative

83

댓글 42

𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞: 𝐒𝐢𝐦𝐩𝐥𝐢𝐟𝐲 𝐘𝐨𝐮𝐫 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭𝐬 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 -> https://lnkd.in/gj-tfEyH Ever deploy the same app to different environments (dev, test, prod) and tweak configs each time? There's a better way! Meet Kustomize, a powerful tool for customizing Kubernetes deployments without code changes. Think of it like outfitting your app for different occasions. 𝐁𝐚𝐬𝐞 𝐌𝐚𝐧𝐢𝐟𝐞𝐬𝐭: Your app's core configuration, the basic outfit. 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐚𝐭𝐢𝐨𝐧: The magic touch! Patches and overlays customize the base for each environment, like adding a blazer for production. 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 𝐨𝐟 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞: 𝐑𝐞𝐝𝐮𝐜𝐞𝐝 𝐃𝐮𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧: One base manifest, customized for each environment. No more copy-pasting! 𝐂𝐥𝐞𝐚𝐧 𝐂𝐨𝐝𝐞: Keep your app code clean and separate from environment-specific configs. 𝐃𝐞𝐜𝐥𝐚𝐫𝐚𝐭𝐢𝐯𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Simply define what you want, and Kustomize takes care of the details. 𝐊𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐞 𝐢𝐬 𝐩𝐞𝐫𝐟𝐞𝐜𝐭 𝐟𝐨𝐫: Developers who want clean separation of concerns. Ops teams who need to manage deployments across environments. Is Kustomize the new Helm?  Not quite! While both manage deployments, Kustomize focuses on configuration, while Helm offers templating and package management for complex deployments. Think of Kustomize as your go-to tool for configuration customization, and Helm for full-fledged deployment management. Want to learn more? Dive deeper into Kustomize documentation and explore its capabilities! 𝑱𝒐𝒊𝒏 𝑶𝒖𝒓 𝑻𝒆𝒄𝒉 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒕𝒚 -> 𝑮𝒖𝒊𝒅𝒆 𝑶𝒕𝒉𝒆𝒓’𝒔 -> 𝑾𝒊𝒏 𝑬𝒙𝒄𝒊𝒕𝒊𝒏𝒈 𝑹𝒆𝒘𝒂𝒓𝒅𝒔 -> https://lnkd.in/gj-tfEyH  #kubernetes #devops #devops #cloudnative

64

댓글 27

(請注意：中文內容設於下方) [iThome Ironman Contest 2024 - Kubernetes]  Can you take on the challenge of posting technical articles for 30 consecutive days without interruption?   This year, CNTUG and iThome are co-hosting the Ironman Contest in the "Kubernetes" category.   Starting now until September 15th (Sunday) at 11:59 PM, publish your first article and begin a 30-day streak of uninterrupted technical article posts to complete the challenge and become an Ironman.   Invite your skilled friends to take on the Ironman Contest challenge! * Excerpt from the contest guidelines - Competition Rules: This competition allows the use of generative AI and other emerging technologies. The content should primarily be in Traditional Chinese (technical terms are not restricted). * If you start early and accidentally interrupt the streak, you can restart the 30-day series as long as it is before September 15th. * iThome Ironman Contest 2024 event website: https://lnkd.in/gigRAYGE * For detailed competition rules, please refer to the event guidelines: https://lnkd.in/g8FMnHZp === [iThome 鐵人賽 2024 - Kubernetes 組] 你能 30 天不中斷的發技術文章挑戰嗎？ 今年 CNTUG 跟 iThome 合辦鐵人賽「Kubernetes」組。 即日起到 9/15 (日) 23:59 前發出你的第一篇文章，並開始連續發表 30 天技術文章不中斷，就能完賽鍊成鐵人。 趕快揪你的強者朋友來挑戰鐵人賽吧！ * 節錄自活動簡章 - 競賽規範：本競賽可使用生成式人工智慧等新興科技，發文內容應以繁體中文為主（專有名詞不在此限）。 * 如果提早開賽不小心中斷，只要在 9/15 前都還來得及重新開始 30 天連載。 * iThome 鐵人賽 2024 活動網站：https://lnkd.in/gigRAYGE * 競賽規範請詳閱活動簡章：https://lnkd.in/g8FMnHZp

12

https://lnkd.in/g_5WieaK Optimizing MongoDB Checkpointing for Performance #MongoDB #MongoDBTricks #MongoDBPerformance #DBA #NoSQL

6

As an application developer or data architect, how do you manage distributed transactions in distributed systems? Is it Saga, 2PC, or TCC? Recently, at the KubeDay Japan conference, our CTO, Hiroyuki Yamada and architect, Toshihiro Suzuki discussed the pros and cons of these various protocols in distributed systems. We'll post the video soon, but here is his KubeDay deck. Let us know what you think! Here's Hiroyuki Yamada and Toshihiro Suzuki slide deck! Enjoy! https://lnkd.in/egrtvwWY #database #japan #technology #innovation #scalarlabs #cloud #microservices

5

Join me this afternoon to learn about .NET and AI. RSVP below.

1

Do you want to know about how to better manage transactions in microservices? If you do, please check our presentation at KubeDay! https://lnkd.in/gCYznq7p Title: Towards Effortless Transaction Management in Microservices Abstract: Developing microservice applications based on the database-per-service pattern is challenging because you need to ensure the transactional consistency of multiple, possibly diverse, databases of microservices. Saga and TCC are widely used to address the challenge, but these approaches require the applications to ensure isolation, forcing the application developers to implement complex recovery mechanisms. Another way is using a two-phase commit (2PC). However, 2PC is often discussed as an anti-pattern in microservice architecture since it is considered limited in scalability and availability. In this session, we revisit the benefits of microservice architecture and rethink the advantages and disadvantages of the existing approaches for transaction management. We also introduce a solution that achieves effortless transaction management in microservices without losing the most benefits.

22

댓글 3

PoWA 5 is out! 🚀 **Exciting News for PostgreSQL Enthusiasts! PoWA 5 is Here!** 🚀 Greetings from Taipei, where the PoWA team has just dropped the highly anticipated PoWA 5.0.0! Yes, you heard that right—your performance monitoring dreams just got a major upgrade. This new version comes packed with an overhauled powa-web UI, making it look sharp enough to be on the front cover of a design magazine. 📊 Expect a user experience that even your mom would find intuitive. With new data sources for replication stats, background writer insights, and even per-database metrics, it's like having a GPS for your PostgreSQL performance—because who doesn’t want to avoid data traffic jams? 🚦 A huge shoutout to those who reported bugs or contributed patches; without you, PoWA wouldn’t have the same charm! Want to make your PostgreSQL instance not just good, but great? Check it out: [PoWA on GitHub](https://lnkd.in/e5zWQqGb) Dive into the future of PostgreSQL performance analysis. Your servers will thank you! 🖥️✨ #PostgreSQL #PoWA #PerformanceMonitoring #DatabaseManagement #OpenSource Source: https://lnkd.in/e9WE9FR7

2

𝗲𝗕𝗣𝗙 𝗧𝗶𝗽 → 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗚𝗮𝗶𝗻𝘀 𝘄𝗶𝘁𝗵 𝗖𝗮𝗹𝗶𝗰𝗼 𝗲𝗕𝗣𝗙 Achieve better throughput and lower CPU usage in Kubernetes with Calico's eBPF dataplane. 𝗖𝗵𝗲𝗰𝗸 𝗶𝘁 𝗼𝘂𝘁 𝗵𝗲𝗿𝗲:  https://lnkd.in/gPkUjQtw

7

(請注意：中文內容設於下方) [KCD Taipei 2024 Session Promote VI] Grafana Alloy is an OpenTelemetry (OTel) collector launched by Grafana Labs, but have you ever thought about how to operate it in a multi-tenancy environment? The next session introduces Eric Huang’s “Best Practices for Grafana Alloy: Multi-Tenancy Design, Performance Optimization, and End-to-End Tracing.” This session will teach you how to quickly deploy Grafana Alloy and achieve multi-tenant design, including setting rate limits for individual tenants. Whether refining logs into metrics with Loki rulers or propagating trace context from front-end apps, it can all be configured to display on Grafana. === [KCD Taipei 2024 議程宣傳 VI] Grafana Alloy 是 Grafana Labs 推出的 OpenTelemetry (OTel) 收集器，但有想過要如何在 multi-tenancy 上運作嗎？ 下一個議程來介紹是 Eric Huang 的「Grafana Alloy 最佳實踐：多租户設計、性能優化與端到端追蹤」。 本次議程會教如何快速部署 Grafana Alloy，並達到 multi-tenant 設計，並且對個別 tenant 設定 rate limit。不論是 Loki rulers 從 log 精煉成 metrics，還是由前端 app 的 trace context propogation，都可以設定到 Grafana 上呈現。 #KCD #KCDTaipei #KCDTaipei2024 #CNCF

3

댓글 1

At EDB, we are proud of our long history of contributions to the open-source community. From Postgres to Barman and CloudNative PG, our experts are consistently writing code that unlocks new database possibilities for the workloads of the future. In a new blog, EDB software engineer Tianqiu Huang 黄天秋 (TQ) dives into EDB's recent contribution to the popular AI stack PrivateGPT, detailing the integration of PGVector as the embedding store in PrivateGPT. Key highlights: > Flexability and Cost-Effectiveness > Data Security and Storage > Power of PGVector. Get an inside look at how TQ integrated PGVector into PrivateGPT, making it a supported vector store. Read the full blog here: https://bit.ly/3RixnP2 #Postgres #PostgreSQL #justsolveitwithPostgres #EDBPostgresAI #data #AI #database #DBA #Barman #CloudNativePG #CNPG #PGVector #vector #vectordatabase #GPT #LLM #PrivateGPT

48

댓글 2

We just released the latest version of our SPC Histogram panel in the Grafana plugin repository (https://lnkd.in/dae6g-TK)! What's New: ✅ Gaussian Curve Functionality: You can now add a Gaussian (normal distribution) curve to your histograms. ✅ Histogram Curve: A new option to plot a smoothed curve along your histogram for better data visualization. ✅ Bug Fixes: We've squashed a few bugs to improve overall performance. ✅ New Documentation: Check out the updated documentation here: https://lnkd.in/e_VWvneh. Upgrade now and explore the new features! #KensoBI #Grafana #Histogram #DataVisualization #SPC

9