<?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>Nodes on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/nodes/</link><description>Recent content in Nodes on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Tue, 02 Sep 2025 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/nodes/atom.xml" rel="self" type="application/rss+xml"/><item><title>How to Upgrade the cgroup Version of a Kubernetes Node</title><link>https://www.chenshaowen.com/en/blog/how-upgrade-kubernetes-node-cgroup-version.html</link><pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate><atom:modified>Tue, 02 Sep 2025 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-upgrade-kubernetes-node-cgroup-version.html</guid><description>1. Interface Path Differences Between cgroup v1 and v2 v1 1 2 3 4 /sys/fs/cgroup/cpu/cpu.cfs_quota_us /sys/fs/cgroup/cpu/cpuacct.usage /sys/fs/cgroup/memory/memory.limit_in_bytes /sys/fs/cgroup/memory/memory.usage_in_bytes v2 1 2 3 4 /sys/fs/cgroup/cpu.max /sys/fs/cgroup/cpu.stat /sys/fs/cgroup/memory.max /sys/fs/cgroup/memory.current cgroup v2 is the upgraded version of v1, with advantages such as more unified resource hierarchy management and precise resource isolation. But it also means that when writing code, the paths for reading the relevant interface files are different, so compatibility handling is required.</description><dc:creator>微信公众号</dc:creator><category>Kubernetes</category><category>Upgrade</category><category>Operations</category><category>cgroup</category><category>Learning</category><category>Nodes</category><category>Resource Isolation</category><category>Troubleshooting</category><category>Kubelet</category></item><item><title>Adding a Windows Node to Kubernetes</title><link>https://www.chenshaowen.com/en/blog/add-windows-node-for-k8s.html</link><pubDate>Sat, 13 Jun 2020 00:00:00 +0000</pubDate><atom:modified>Sat, 13 Jun 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/add-windows-node-for-k8s.html</guid><description>Here a Windows node is used mainly as a Worker, while the Master control plane stays on Linux.
1. System Configuration 1.1 Kubernetes Control Plane Since version 1.14, Kubernetes has added production-grade support for Windows nodes. Because Microsoft&amp;rsquo;s official documentation mainly covers installing the flannel network plugin, it is recommended here that Kubernetes also use the flannel plugin.</description><dc:creator>微信公众号</dc:creator><category>Kubernetes</category><category>Windows</category><category>Nodes</category><category>Installation</category><category>Operations</category></item></channel></rss>