<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Huy Du on Medium]]></title>
        <description><![CDATA[Stories by Huy Du on Medium]]></description>
        <link>https://medium.com/@dugiahuy?source=rss-67bb7cd3a981------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cKjxuNaThvIuwsB4.</url>
            <title>Stories by Huy Du on Medium</title>
            <link>https://medium.com/@dugiahuy?source=rss-67bb7cd3a981------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:32:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dugiahuy/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Setting Up Software Engineer Development]]></title>
            <link>https://medium.com/@dugiahuy/setting-up-software-engineer-development-2e59c52c15ba?source=rss-67bb7cd3a981------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e59c52c15ba</guid>
            <category><![CDATA[software-engineer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[setup-guide]]></category>
            <dc:creator><![CDATA[Huy Du]]></dc:creator>
            <pubDate>Wed, 09 Aug 2023 09:11:21 GMT</pubDate>
            <atom:updated>2023-08-10T05:29:22.685Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_V0c0I8c5I-iN2lnzM0ZQ.png" /><figcaption>Credit: <a href="https://dugiahuy.com/blog/setting-up-software-engineer-development/"><em>https://dugiahuy.com/blog/setting-up-software-engineer-development/</em></a></figcaption></figure><p>Setting up development environments is a frequent ritual in a software engineer’s journey, a task I’ve lost count of over my career. Yet this time, I’ve documented the steps, saving future hours in configuring a new development for coding.</p><blockquote><em>Original from: </em><a href="https://dugiahuy.com/blog/setting-up-software-engineer-development/"><em>https://dugiahuy.com/blog/setting-up-software-engineer-development/</em></a></blockquote><h3>Basic Usage for Macbook Productivity</h3><p>Customize System Preferences with following options</p><h4><strong>Trackpad</strong></h4><ul><li>Tap to click</li><li>Tracking speed: Maximum as Fast</li></ul><h4><strong>Trackpad Options</strong></h4><ul><li>Use trackpad for dragging</li><li>Dragging Style -&gt; Three finger flag</li></ul><h4><strong>Keyboard</strong></h4><ul><li>Add language typing system: Simple Telex (Vietnamese)</li></ul><h4><strong>Keyboard layouts</strong></h4><ul><li>Disable Correct spelling automatically</li></ul><h4><strong>Security and Privacy</strong></h4><ul><li>Enabling FileVault for data encryption.</li><li>Configuring a firewall and managing app permissions.</li><li>Using a password manager for secure credentials.</li></ul><h4><strong>Backup and Restoring</strong></h4><ul><li>Time Machine: Setup automatic backups. Good usage for external drive.</li><li>Cloud Storage: Syncing important files and settings.</li></ul><h3>Essential Applications</h3><h4><strong>Safari</strong></h4><ul><li>Tabs: Compact layout</li><li>Privacy: Prevent tracking</li><li>Advanced: Show full website address and Show Develop menu in menu bar</li></ul><h4><strong>Rectangle</strong></h4><p>Import <a href="https://github.com/dugiahuy/dotfiles/blob/master/RectangleConfig.json">my personal setting in dotfiles</a></p><h4><strong>Logi Option+</strong></h4><p>Install driver for logitech devices</p><p>Many other applications can refer to <a href="https://github.com/dugiahuy/dotfiles/blob/master/Brewfile">Brewfile in my dotfiles</a> repo</p><h3>Essential Developer Tools</h3><p>In the world of software development, there are numerous important tools that you need to install. After using these tools for several years, I always emphasize for a simpler and effective performance. That’s why I created <a href="https://github.com/dugiahuy/dotfiles/">my dotfiles</a> to simplify it. Dotfiles allow you to install and manage all the necessary tools automatically and effortlessly, making the setup process much easier.</p><h4>A typical developer environment requires the following tools:</h4><ul><li><strong>Xcode</strong>: Apple’s integrated development environment.</li><li><strong>Homebrew</strong>: A package manager for macOS. I utilize a <strong>Brewfile</strong> to automate the setup of my common packages.</li><li><strong>Zsh</strong>: The Z shell replaces the default Bash shell on macOS.</li><li><strong>Prezto</strong>: A rapid configuration framework for <strong>Zsh</strong> that I migrated to after using <strong>Oh-my-zsh</strong> for a while.</li><li><strong>Terminal</strong>: Personally, I opt for <strong>iTerm</strong>, though you can also use <strong>Kitty</strong> for GPU-rendered text.</li></ul><h4>For custom configurations, place them in the following files:</h4><ul><li><strong>.zshrc</strong>: Configuration for your shell environment.</li><li><strong>.zpreztorc</strong>: Configuration for your Zsh plugins.</li></ul><h3>Development Environment</h3><h4>IDE</h4><p>I used to be a terminal fanatic, and having <strong>Emacs</strong> and <strong>Vim</strong> was absolutely indispensable. But as time marched on, I opted for the simplicity of <strong>VSCode</strong> — a bit like swapping out sneakers for a comfy pair of slippers.</p><h4>Version Control</h4><p>Using Git with <strong>Sublime Merge</strong> (GUI) and command line</p><h4>Programming Language</h4><p><strong>Ruby</strong> and <strong>Golang</strong> drive my backend development, while <strong>Python</strong> fuels AI hobby projects. Therefore, smoothly managing language environments and isolated development through package manager is vital.</p><h4>Package Manager</h4><p>With various options for each language, I’ve streamlined my process by adopting <strong>asdf</strong>— a time-saving choice.</p><h4>Virtualization</h4><p>Containerized development like <strong>Docker</strong> offers isolation and quick setup. However, for enhanced speed, opt for a native setup with manual tool installation. There’s always a tradeoff, the cost determined by your decision.</p><h3><strong>Bonus Productivity Tips</strong></h3><h4><strong>Delete a word and a line in iTerm2</strong></h4><p>I exposed those config in <a href="https://github.com/dugiahuy/dotfiles/blob/master/iterm.json">my iTerm profile</a></p><p>Reference: <a href="https://icheft.com/2020/08/12/Delete-a-word-and-a-line-in-iTerm2/">https://icheft.com/2020/08/12/Delete-a-word-and-a-line-in-iTerm2/</a></p><h4><strong>Port 5000 was occupied by Control Center in the new MacOS version</strong></h4><p>If your local development server uses this port, you can regain control by disabling the <strong>AirPlay Receiver</strong> Setting.</p><h4><strong>Clone all repos of company at once</strong></h4><p>Require gh package in your machine, or can install by brew install gh.</p><p>Login with gh</p><pre>gh auth login</pre><p>Clone all repos that defined by --limit option under your new folder my-org. Replace my-org with your organization name:</p><pre>mkdir my-org &amp;&amp; cd my-org<br><br>gh repo list my-org - limit 1000 | while read -r repo _; do<br>  gh repo clone &quot;$repo&quot; &quot;$repo&quot;<br>done</pre><h3>Final Thoughts</h3><p>Setting up software engineer development environment involves several pivotal steps — from tool selection to environment customization. Embrace the journey, iterate, and don’t hesitate to innovate with your medley of tools and configurations.</p><p>In this dynamic landscape, a well-organized, optimized development environment is the compass to navigate the ever-evolving realm of software engineering. Enhanced productivity, refined code, and creative breakthroughs await. Share your experiences, comments, and let’s collectively craft the future of seamless coding together.</p><h4>Reference</h4><ul><li>Dotfiles: <a href="https://github.com/dugiahuy/dotfiles">https://github.com/dugiahuy/dotfiles</a></li><li>Original post: <a href="https://dugiahuy.com/blog/setting-up-software-engineer-development/">https://dugiahuy.com/blog/setting-up-software-engineer-development/</a></li><li><a href="https://icheft.com/2020/08/12/Delete-a-word-and-a-line-in-iTerm2/">Delete a word and a line in iTerm2</a></li><li><a href="https://nono.ma/port-5000-used-by-control-center-in-macos-controlce">Port 5000 used by Control Center in macOS Monterey</a></li><li><a href="https://stackoverflow.com/questions/19576742/how-to-clone-all-repos-at-once-from-github">How to clone all repos at once</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e59c52c15ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Helm 101]]></title>
            <link>https://medium.com/dwarves-foundation/kubernetes-helm-101-78f70eeb0d1?source=rss-67bb7cd3a981------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f70eeb0d1</guid>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Huy Du]]></dc:creator>
            <pubDate>Wed, 30 Oct 2019 08:07:17 GMT</pubDate>
            <atom:updated>2019-10-30T08:24:40.025Z</atom:updated>
            <content:encoded><![CDATA[<p>In recent years, Kubernetes has exploded tremendously. At the same time, it creates new communities including ecosystems that make it easier to develop and deploy complex applications. If Kubernetes means the shipman of the ship, then Helm is the steering wheel of that shipman in the career of every DevOps and Developer.</p><p><strong>Helm is a Package Manager for Kubernetes</strong>, analogous to <em>NPM</em> or <em>YARN</em>. However, it’s not just the Package Manager, it is also a Deployment Management for Kubernetes. In simpler terms, instead of having to define various Kubernetes resources to deploy an application, with Helm you just type a few commands in the terminal and enter, done!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*Lz14y_N5ZiEbP3VArRQ9_g.png" /><figcaption>Photo by <a href="https://boxboat.com/authors/peyton-vaughn">Peyton Vaughn</a> on B<a href="https://boxboat.com/2018/09/19/helm-and-kubernetes-deployments/">oxBoat</a></figcaption></figure><p>In this article, we will learn about Helm, a powerful tool that makes life working with Kubernetes easier than ever. Although these terms are quite common with developers today, we will skim a jiffy for those who don’t know:</p><ul><li><strong><em>Containerization:</em></strong> <em>a next-generation virtualization and automation solution</em> after <em>Hypervisor Virtualization</em>. It widely applied today because of the breakthrough effect with outstanding advantages in creating and deploying applications faster, more scalable and more securely than traditional methods.</li><li><strong><em>Docker:</em></strong> <em>a number one software to create, manage and run containers</em>. Most chosen for all popular <em>Containerization</em> applications today. Many large cloud solutions like Google Cloud, Amazon Web Services, Microsoft Azure are using it.</li><li><strong><em>Kubernetes:</em></strong> <em>a famous open source used for container orchestration</em>. With the rise of <em>Containerization</em>, the management and coordination of container-based applications became complicated and difficult, making Kubernetes an effective and indispensable solution for systems using Containerization.</li></ul><h3>Helm Overview</h3><h4>Concepts</h4><p>Helm has 4 basic concepts:</p><ul><li><strong><em>Chart:</em></strong> <em>a collection of YAML files; bundle of the Kubernetes resources</em> needed to build a Kubernetes application. For ease of visualization, Helm Chart can be compared like a Docker Image. Of course, Helm also has a Helm Hub where to search and share Charts for popular apps.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H9IhHLfj_IBi7863_bzz7Q.png" /><figcaption>The structure of a regular Helm <strong>Chart</strong></figcaption></figure><ul><li><strong><em>Config: </em></strong><em>a configuration in the </em><strong><em>values.yaml</em></strong><em> file</em>, which contains configuration explicit to a release of Kubernetes application. It can be the config for <em>service</em>, <em>ingress, deployment,</em> etc. until specific applications such as <em>Kafka, Consul, Vault, NATS-streaming,</em> etc.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_7JVA9dB_D4Gz5Dnv5Ux6Q.png" /><figcaption><strong>Config</strong> value for different environments of <strong>Kafka</strong></figcaption></figure><ul><li><strong><em>Release: </em></strong><em>a chart instance is loaded into Kubernetes</em>. It can be viewed as a version of the Kubernetes application running based on Chart and associated with a specific Config.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VpAVQiCwtTZUgt42LOnEw.png" /><figcaption><strong>Release</strong> of Helm at <a href="https://dwarves.foundation/"><strong>Dwarves Foundation</strong></a></figcaption></figure><ul><li><strong><em>Repositories: </em></strong><em>a repository of published Charts</em>. These can be private repositories that are only used within the company or public through the <a href="https://hub.helm.sh/">Helm Hub</a>. Some Charts may have different versions of many companies or publishers. Particularly, Charts in a <strong>Stable</strong> repository must always meet the criteria from the <a href="https://github.com/helm/charts/blob/master/CONTRIBUTING.md#technical-requirements">Technical Requirements of Helm</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IydkwxyW48Xs4qgZi-XkgQ.png" /><figcaption>I used to deploy <strong>Vault</strong> Chart, which belongs to <strong>Banzaicloud</strong> or <strong>Incubator</strong> depending on the use-case</figcaption></figure><h4>Architecture</h4><p>Helm has a fairly simple client-server architecture, including a CLI client and an in-cluster server running in the Kubernetes cluster:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mClrYLFakC6B6f62vVnhcA.png" /><figcaption>Helm Architecture</figcaption></figure><ul><li><strong><em>Helm Client</em></strong>: Provides the developer to use it a command-line interface (CLI) to work with Charts, Config, Release, Repositories. Helm Client will interact with Tiller Server, to perform various actions such as <em>install</em>, <em>upgrade</em> and <em>rollback</em> with Charts, Release.</li><li><strong><em>Tiller Server:</em></strong> an in-cluster server in the Kubernetes cluster, interacting with the Helm Client and communicating with the Kubernetes API server. Thus, Helm can easily manage Kubernetes with tasks such as <em>install, upgrade, query</em> and <em>remove</em> for Kubernetes resources.</li></ul><p>Here are some basic concepts and architectures to help you understand and grasp Helm more quickly. In the next section, we’ll take some tutorials to deep dive into Helm. Let’s do it!</p><h3>Helm in Action</h3><p>Before we begin, we’ll need to prepare a few things for us to be able to practice with Helm.</p><ul><li>Firstly, we need a Kubernetes cluster<strong><em>.</em></strong> At <a href="https://dwarves.foundation/"><strong>Dwarves Foundation</strong></a>, we’re using the Google Kubernetes Engine for a production environment and the Kubernetes on-premise for a staging environment. If you don’t have any Kubernetes cluster, don’t worry. You can use <a href="https://kubernetes.io/docs/setup/learning-environment/minikube/">Minikube</a>, which offers an excellent way to work with a single-node Kubernetes cluster locally.</li><li>And, we’ll need a basic purpose that manages the application within the Kubernetes cluster. In fact, I have a responsibility for overseeing and configuring <a href="https://solapp.io/"><strong>Sol</strong></a>, <a href="https://solapp.io/">the<strong> Travel Log</strong> </a>product of the <a href="https://dwarves.foundation/"><strong>Dwarves Foundation</strong></a>. It using Kafka as a message streaming for communication between its’ microservices. For this tutorial, we’ll install Kafka to the Kubernetes cluster via Helm.</li></ul><h4>Installing Helm</h4><p>There are multiple ways to install Helm that are obviously described on <a href="https://helm.sh/docs/using_helm/#installing-helm">the Helm documentation</a>. Helm has two parts: The Helm client (helm) and the Helm server (Tiller). <strong>The quickest way to install helm on macOS is using </strong><a href="https://brew.sh/"><strong>Homebrew</strong></a>, a package manager for macOS platforms.</p><p>It is a simple command to install the Helm client locally via Homebrew:</p><pre>brew install kubernetes-helm</pre><p>Next step is to initialize helm, please ensure that the Kubernetes cluster is running and accessible through <em>kubectl</em>. When you initialize helm, a deployment named tiller-deploy will be deployed in the kube-system namespace.</p><p>Initialize helm using the following command.</p><pre>helm init</pre><p>You can check the tiller deployment in the kube-system namespace using <em>kubectl </em>command.</p><pre>kubectl get deployment tiller-deploy -n kube-system</pre><h4>Deploy an Application using Helm</h4><p>Now we’re going to deploy a Kafka cluster using helm.</p><p>It’s many charts of Kafka when we search on the Helm Hub. Unfortunately, Kafka doesn’t have a Stable chart, so you can choose which one fits with your use case. For this tutorial, we’ll install the Kafka chart of Bitnami into <em>queue-production</em> namespace.</p><p>As a simple way, we can install Kafka with helm by the following command:</p><pre># Add Incubator repository<br>helm repo add bitnami https://charts.bitnami.com/bitnami</pre><pre># Update helm repository<br>helm repo update</pre><pre># Install Kafka<br>helm install bitnami/kafka --name kafka --namespace queue</pre><p>Now, it already installed on your Kubernetes cluster, but it may not work properly for your needs. For me, I usually looking for a <em>values.yaml </em>file, and store it locally to save a specific configuration for instance of the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c1vOb1DXKkmPdnrtI06HtA.png" /></figure><p>Execute the following helm install command to deploy a Kafka with your Config in <em>values-prod.yaml</em>. It will download the Kafka helm chart from the Bitnami repo and apply your configuration via <em>values.yaml</em> file.</p><pre>helm install bitnami/kafka \<br>  --name kafka-prod \<br>  --namespace queue-production \<br>  -f bitnami/values-prod.yaml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*05cxOYBgGLbxcHgfOcrGVA.png" /></figure><p>You can check the install helm chart using the following command</p><pre>helm ls </pre><p>If you want to delete that installation from the Kubernetes cluster, you can use delete command:</p><pre>helm delete --purge kafka-prod</pre><h3>Conclusion</h3><p>We’ve witnessed the ecosystem around Kubernetes blossom, and new tools are appearing every day. Helm is an essential tool for DevOps and Developer using Kubernetes in their production environment. Tools like Helm are often used when considering quick deployment strategies and cost savings in operations.</p><p>You can refer to more information in <a href="https://helm.sh/docs/">the documentation of Helm</a>. In the next article, I will show you how to create a Helm Chart of NATS-streaming. Hopefully, this article will help you who are intending to learn about Helm as well as the necessary tools of the DevOps. Thank you, please give me your commend if there are deficiencies and I will do better in the next articles.</p><h3>Read more</h3><ul><li><a href="https://hackernoon.com/what-is-containerization-83ae53a709a6#targetText=Containerization%20involves%20bundling%20an%20application,ecosystems%20are%20Docker%20and%20Kubernetes."><em>What is Containerization?</em></a></li><li><a href="https://helm.sh/docs/"><em>Helm documentation</em></a></li><li><a href="https://www.baeldung.com/kubernetes-helm"><em>Using Helm and Kubernetes</em></a></li><li><a href="https://boxboat.com/2018/09/19/helm-and-kubernetes-deployments/"><em>What is Helm and why is it important for Kubernetes deployments?</em></a></li><li><a href="https://devopscube.com/install-configure-helm-kubernetes/"><em>Helm Tutorial: How To Install and Configure Helm</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f70eeb0d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dwarves-foundation/kubernetes-helm-101-78f70eeb0d1">Kubernetes Helm 101</a> was originally published in <a href="https://medium.com/dwarves-foundation">Dwarves Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Helm 101]]></title>
            <link>https://medium.com/@dugiahuy/kubernetes-helm-101-88074e2b76d9?source=rss-67bb7cd3a981------2</link>
            <guid isPermaLink="false">https://medium.com/p/88074e2b76d9</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[dwarves]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Huy Du]]></dc:creator>
            <pubDate>Sun, 27 Oct 2019 12:16:40 GMT</pubDate>
            <atom:updated>2019-10-27T17:27:07.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sơ lược về Kubernetes <strong>Helm</strong></h3><p>Những năm vừa qua, Kubernetes đã bùng nổ vô cùng mạnh mẽ. Cùng lúc đó tạo ra những cộng đồng, hệ sinh thái mới giúp việc phát triển, triển khai ứng dụng vốn phức tạp và khó khăn trở nên đơn giản hơn. Kubernetes có nghĩa là người lái tàu thì Helm chính là bánh lái của con tàu ấy trong “nghiệp” của mỗi DevOps và Developer.</p><p><a href="https://helm.sh/"><strong>Helm</strong></a><strong> là một package manager dành cho Kubernetes</strong>. Cũng giống như những package manager nổi tiếng của NodeJS như <em>NPM</em> hay <em>YARN</em>, Helm dùng để quản lý các Kubernetes application được dựng lên từ những Kubernetes resource. Hiểu nôm na là thay vì phải define một nùi Kubernetes resource để triển khai một ứng dụng, thì với Helm bạn chỉ việc gõ vài lệnh trong terminal và enter cái “bụp”, xong!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*Lz14y_N5ZiEbP3VArRQ9_g.png" /><figcaption>Photo by <a href="https://boxboat.com/authors/peyton-vaughn">Peyton Vaughn</a> on B<a href="https://boxboat.com/2018/09/19/helm-and-kubernetes-deployments/">oxBoat</a></figcaption></figure><p>Trong bài viết này, chúng ta sẽ cùng tìm hiểu về Helm, một công cụ mạnh mẽ giúp làm việc với Kubernetes dễ dàng hơn bao giờ hết. Mặc dù những thuật ngữ này khá phổ biến với Developer hiện nay, chúng ta sẽ lướt qua một chút để dành cho những người chưa biết:</p><ul><li><strong><em>Containerization:</em></strong> là giải pháp ảo hoá, tự động hoá thế hệ mới kế tiếp sau Hypervisor Virtualization, được áp dụng rộng rãi hiện nay bởi hiệu quả đột phá với các ưu điểm vượt trội về tốc độ triển khai, khả năng mở rộng, tính an toàn và trải nghiệm người dùng.</li><li><strong><em>Docker:</em></strong> là phần mềm tạo, quản lý và chạy <em>container </em>số một hiện nay. Được lựa chọn hầu hết cho tất cả các ứng dụng <em>Containerization </em>phổ biến hiện nay.</li><li><strong><em>Kubernetes: </em></strong>là phần mềm nổi tiếng dùng để điều phối hoạt động của các <em>container. </em>Cùng với sự trỗi dậy của <em>Containerization </em>thì việc quản lý và điều phối những ứng dụng sử dụng <em>container </em>trở nên phức tạp và khó khăn khiến Kubernetes trở thành một giải pháp hữu hiệu, không thể thiếu đối với những hệ thống sử dụng <em>Containerization.</em></li></ul><h3>Các khái niệm</h3><p>Helm có 4 khái niệm cơ bản:</p><ul><li><strong><em>Chart</em></strong>: là tập hợp những file YAML template của những Kubernetes resource cần thiết để dựng lên một ứng dụng Kubernetes. Để dễ hình dung, <em>Chart</em> của Helm có thể được so sánh giống như một <em>Image </em>của Docker. Đương nhiên Helm cũng có <a href="https://hub.helm.sh/">Helm Hub</a> nơi để tìm kiếm và chia sẻ Chart của những ứng dụng phổ biến.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H9IhHLfj_IBi7863_bzz7Q.png" /><figcaption>Cấu trúc của một Helm Chart thông thường</figcaption></figure><ul><li><strong><em>Config</em></strong>: nằm trong file <strong>values.yaml</strong> chứa những configuration dành riêng cho một bản release của Kubernetes application. Đó có thể là config cho <em>service, ingress, deployment,…</em> cho đến những application riêng biệt như <em>Kafka, Consul, Vault, NATS-streaming,</em>…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_7JVA9dB_D4Gz5Dnv5Ux6Q.png" /><figcaption><em>Config</em> dành cho những environment khác nhau của một Kubernetes application</figcaption></figure><ul><li><strong><em>Release</em></strong>: là một version của K8s application đang chạy dựa trên <em>Chart</em> và kết hợp với một <em>Config</em> cụ thể.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VpAVQiCwtTZUgt42LOnEw.png" /><figcaption>Release của Helm ở công ty <a href="https://dwarves.foundation/"><strong>Dwarves Foundation</strong></a></figcaption></figure><ul><li><strong><em>Repositories</em></strong>: Helm Charts có thể được publish thông qua nhiều repo khác nhau. Nó có thể là những private repo chỉ dùng trong nội bộ công ty, hoặc public thông qua <a href="https://hub.helm.sh/">Helm Hub</a>. Một số Chart có thể có nhiều phiên bản của từng công ty hoặc publisher khác nhau. Riêng những Chart trong repo <strong>Stable </strong>thì luôn phải đáp ứng được tiêu chí từ <a href="https://github.com/helm/charts/blob/master/CONTRIBUTING.md#technical-requirements">Technical Requirements của Helm</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IydkwxyW48Xs4qgZi-XkgQ.png" /><figcaption><strong>Vault</strong> mình sử dụng chart của <strong>Banzaicloud</strong> hoặc <strong>Incubator</strong> tuỳ vào usecase sử dụng</figcaption></figure><h3>Kiến trúc</h3><p>Helm có một kiến trúc client-server khá đơn giản, bao gồm <em>client CLI</em> và một <em>server</em> chạy trong Kubernetes cluster:</p><ul><li><strong><em>Helm Client</em></strong>: cung cấp cho developer sử dụng nó một command-line interface (CLI) để làm việc với <em>Charts</em>, <em>Config, Release</em>, <em>Repositories</em>. Helm Client sẽ tương tác với Tiller Server, để thực hiện các hành động khác nhau như <em>install, upgrade</em> và <em>rollback</em> với những <em>Charts, Release.</em></li><li><strong><em>Tiller Server</em>: </strong>là một server nằm trong Kubernetes cluster, tương tác với Helm Client và giao tiếp Kubernetes API server. Nhờ đó Helm có thể dễ dàng quản lý Kubernetes với các tác vụ như <em>install, upgrade, query </em>và <em>remove </em>đối với Kubernetes resources<em>.</em></li></ul><h3>Lời nhắn gửi</h3><p>Vừa rồi là một số khái niệm cơ bản và kiến trúc để giúp bạn có thể hiểu và nắm bắt Helm một cách nhanh chóng hơn. Hệ sinh thái Kubernetes đang phát triển với tốc độ điên cuồng và các công cụ mới xuất hiện mỗi ngày. Helm là cộng cụ thiết yếu dành cho DevOps và Developer đang sử dụng Kubernetes ở môi trường production của mình. Các công cụ như Helm thường được sử dụng khi có chiến lược triển khai nhanh chóng và tiết kiệm chi phí vận hành.</p><p>Các bạn có thể tham khảo thêm thông tin tại <a href="https://helm.sh/docs">document của Helm</a>. Trong bài viết tiếp theo, mình sẽ hướng dẫn cách thực hiện những tác vụ cơ bản của Helm và cách tạo một Helm Chart như thế nào.</p><p>Hi vọng bài viết này sẽ giúp ích cho các bạn đang có ý định tìm hiểu về Helm cũng như các công cụ cần thiết của một DevOps. Cảm ơn các bạn đã theo dõi bài viết, hãy góp ý cho mình nếu có sai sót và mình sẽ làm tốt hơn ở những bài viết sau.</p><h4>Đọc thêm</h4><ul><li><a href="https://hackernoon.com/what-is-containerization-83ae53a709a6#targetText=Containerization%20involves%20bundling%20an%20application,ecosystems%20are%20Docker%20and%20Kubernetes."><em>What is Containeriztion?</em></a></li><li><a href="https://helm.sh/docs/"><em>Helm documentation</em></a></li><li><a href="https://www.baeldung.com/kubernetes-helm"><em>Using Helm and Kubernetes</em></a></li><li><a href="https://boxboat.com/2018/09/19/helm-and-kubernetes-deployments/"><em>What is Helm and why is it important for Kubernetes deployments?</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88074e2b76d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>