<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloud-Native on Datayurei Blog</title><link>https://blog.datayurei.com/en/categories/cloud-native/</link><description>Recent content in Cloud-Native on Datayurei Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 14 Sep 2026 15:27:00 +0800</lastBuildDate><atom:link href="https://blog.datayurei.com/en/categories/cloud-native/index.xml" rel="self" type="application/rss+xml"/><item><title>Understand how does CRD server work when going though issue#130235</title><link>https://blog.datayurei.com/en/posts/k8s-issue-130235/</link><pubDate>Mon, 14 Sep 2026 15:27:00 +0800</pubDate><guid>https://blog.datayurei.com/en/posts/k8s-issue-130235/</guid><description>&lt;p&gt;This issue is relate to the controller and handler, which is the part of code I am not familiar.
Therefore it consumes me days to understand how does it work inside the rcd server.&lt;/p&gt;
&lt;p&gt;CRD server(maybe it is not precise?) is contained inside the api-server and is called as apiextension-server
actually in code. It handles CRD request and events when the event arrives, which is sent by a shared Informer. Here I
want to add some about Informer: it&amp;rsquo;s a specialized component for syncing, draining and dispatching event to its destination.&lt;/p&gt;</description></item><item><title>Something I learned about kubernetes api-server watch mechanism when try solving issue#131721</title><link>https://blog.datayurei.com/en/posts/k8s-issue-131721/</link><pubDate>Fri, 04 Sep 2026 23:45:00 +0800</pubDate><guid>https://blog.datayurei.com/en/posts/k8s-issue-131721/</guid><description>Something about the Cache machanism I learn when I solving issue 131721 in k8s</description></item></channel></rss>