<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Cloud Native on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/cloud-native/</link><description>Recent content in Cloud Native on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 22 Feb 2023 01:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/cloud-native/atom.xml" rel="self" type="application/rss+xml"/><item><title>Developing an Istio WasmPlugin with TinyGo</title><link>https://www.chenshaowen.com/en/blog/developing-istio-wasm-plugin-by-tinygo.html</link><pubDate>Wed, 22 Feb 2023 01:00:00 +0000</pubDate><atom:modified>Wed, 22 Feb 2023 01:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/developing-istio-wasm-plugin-by-tinygo.html</guid><description>wasme only supports up to Istio 1.9, while I am using Istio 1.14, so this post goes straight to tinygo for verification and learning.
1. Installing tinygo Requirements Go v1.18+
Install tinygo 1 2 brew tap tinygo-org/tools brew install tinygo Check the version 1 2 3 tinygo version tinygo version 0.</description><dc:creator>微信公众号</dc:creator><category>tinygo</category><category>Istio</category><category>Wasm</category><category>Cloud Native</category><category>Service Mesh</category><category>R&amp;D</category><category>Go</category><category>Learning</category><category>Extension</category></item><item><title>Multi-Cluster Applications Under Kubevela</title><link>https://www.chenshaowen.com/en/blog/multi-cluster-applications-under-kubevela.html</link><pubDate>Fri, 17 Sep 2021 00:00:00 +0000</pubDate><atom:modified>Fri, 17 Sep 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/multi-cluster-applications-under-kubevela.html</guid><description>Kubevela is currently at version 1.1. We usually consider 1.x releases to be relatively stable and safe to try in production. Through continuous tracking and learning, I have also come to appreciate some of the things Kubevela does well. This is a summary document.
1. What Problem Kubevela Solves Aimed at platform developers Several roles need to be distinguished: development, operations, and operations development.</description><dc:creator>微信公众号</dc:creator><category>Kubevela</category><category>Kubernetes</category><category>Application</category><category>Operations</category><category>Multi-Cluster</category><category>OAM</category><category>Learning</category><category>Cloud Native</category></item><item><title>Gateway Service on Kubernetes: APISIX</title><link>https://www.chenshaowen.com/en/blog/a-gateway-under-kubernetes-named-apisix.html</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 01 Sep 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-gateway-under-kubernetes-named-apisix.html</guid><description>1. Comparing a Few Common Gateways Nginx, a reverse proxy with a modular design, written in C OpenResty, a web development platform built around Nginx that can parse and execute Lua scripts Kong, an application on top of OpenResty, an API gateway with API management and request proxying, using PostgreSQL for storage APISIX, which replaces Kong&amp;rsquo;s PostgreSQL with Etcd and is built on Nginx&amp;rsquo;s core libraries APISIX&amp;rsquo;s advantage lies in the API management and extensibility it provides, so the gateway no longer merely forwards traffic to services but can be configured and customized.</description><dc:creator>微信公众号</dc:creator><category>Kubernetes</category><category>APISIX</category><category>Microservices</category><category>Gateway</category><category>Operations</category><category>Proxy</category><category>Learning</category><category>Cloud Native</category></item><item><title>A Universal Pipeline Design</title><link>https://www.chenshaowen.com/en/blog/a-universal-design-for-pipeline.html</link><pubDate>Wed, 19 May 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 19 May 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-universal-design-for-pipeline.html</guid><description>1. Decoupling the Engine to Unlock Pipeline Capabilities When designing a system, we often face a dilemma. Do we contain the complexity and offer a single, easy-to-use capability to the outside; or do we release the complexity and return flexibility to the user? This is a real test of product</description><dc:creator>微信公众号</dc:creator><category>Cloud Native</category><category>DevOps</category><category>CICD</category><category>Thoughts</category><category>R&amp;D</category></item><item><title>How Tekton Connects to Physical Machines for Builds</title><link>https://www.chenshaowen.com/en/blog/how-to-add-physical-machines-to-tekton.html</link><pubDate>Wed, 28 Apr 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 28 Apr 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-add-physical-machines-to-tekton.html</guid><description>1. Why Physical Build Machines Are Needed In the article How to Add a Remote macOS Physical Machine for Jenkins Pipeline Builds, I described how to add a physical build machine in Jenkins. This was not a requirement I made up on a whim — at the time, real ToB commercial customers were actually asking for a solution.</description><dc:creator>微信公众号</dc:creator><category>Tekton</category><category>Cloud Native</category><category>Kubernetes</category><category>CICD</category><category>DevOps</category><category>Operations</category></item><item><title>Distributing Files and Running Scripts on VM Nodes in Kubernetes</title><link>https://www.chenshaowen.com/en/blog/how-to-distribute-files-and-scripts-to-vm-under-kubernetes.html</link><pubDate>Sat, 24 Apr 2021 00:00:00 +0000</pubDate><atom:modified>Sat, 24 Apr 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-distribute-files-and-scripts-to-vm-under-kubernetes.html</guid><description>1. What This Article Mainly Discusses Never build a high tower on shifting sand. Business growth and the evolution of business forms both need solid, powerful IT systems to support them. Business content is transparent to the market, but IT systems cannot be built to perfection overnight. In the future, competition between companies will mainly come from competition between their IT systems, and the ability to respond quickly to business requirements will be the key to winning.</description><dc:creator>微信公众号</dc:creator><category>Kubernetes</category><category>Docker</category><category>PaaS</category><category>Operations</category><category>Configuration Management</category><category>Virtual Machines</category><category>Learning</category><category>Cloud Native</category></item><item><title>Using S2I to Build Cloud Native Applications</title><link>https://www.chenshaowen.com/en/blog/using-s2i-to-build-cloud-native-applications.html</link><pubDate>Mon, 26 Aug 2019 00:00:00 +0000</pubDate><atom:modified>Mon, 26 Aug 2019 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-s2i-to-build-cloud-native-applications.html</guid><description>1. What Problem S2I Solves It is foreseeable that a large number of applications will be deployed as containers in the future.
Container platforms care about images and containers, while application development cares about business code, and ultimately the code needs to be deployed as an image. From code to image — that is Source To Image, or S2I.</description><dc:creator>微信公众号</dc:creator><category>S2I</category><category>Docker</category><category>Cloud Native</category><category>Images</category><category>Operations</category><category>R&amp;D</category></item><item><title>PaaS Deployment with Buildpack</title><link>https://www.chenshaowen.com/en/blog/buildpack-for-paas-deployment.html</link><pubDate>Thu, 24 Jan 2019 00:00:00 +0000</pubDate><atom:modified>Thu, 24 Jan 2019 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/buildpack-for-paas-deployment.html</guid><description>I have been learning Go recently, and the internal PaaS platform we commonly use happens to support Go as well as related Web frameworks. A PaaS system that supports multiple languages cannot do without the buildpack mechanism. Although PaaS platforms keep being upgraded, the buildpack mechanism has always been retained.</description><dc:creator>微信公众号</dc:creator><category>PaaS</category><category>Buildpack</category><category>Operations</category><category>R&amp;D</category><category>Deployment</category><category>Learning</category><category>Cloud Native</category><category>Multi-language</category></item></channel></rss>