Tag: #쿠버네티스

← All posts

• When the documentation still puts spec.running, deprecated 2 years ago, on the very first line: How a KubeVirt user guide PR was merged in ten days

  The VirtualMachine field spec.running in KubeVirt has been deprecated since v1.4.0 (merged in September 2024), and the API server returns a warning every time a VM containing this field is created or modified. However, t

  2026-10-28 · 14 min read #오픈소스#오픈소스 기여#KubeVirt#쿠버네티스#문서

• The operator that searched for an unused webhook every 6 seconds: How the KubeVirt upstream PR was merged in 2 days and 16 hours

  Counting the requests sent by virt-operator in the TT Lab cluster to the API server over 59 days as the operator's own metrics revealed 843,995 GET requests looking for a non-existent webhook, all resulting in 404. This

  2026-10-28 · 16 min read #오픈소스#오픈소스 기여#KubeVirt#쿠버네티스#오퍼레이터

• Rook-Ceph Guide 3: Reading the values of rook-ceph and rook-ceph-cluster charts 1.21.1

  When installing Rook with Helm, what you actually decide are a few dozen lines in values.yaml. We directly opened the rook-ceph chart (245 lines) and rook-ceph-cluster chart (844 lines) of the v1.21.1 tag and organized i

  2026-10-28 · 35 min read #Rook#Ceph#Helm#쿠버네티스#스토리지

• Rook-Ceph Guide 2: What the Rook Operator Does and Does Not Do

  Rook is an operator that runs Ceph on Kubernetes. By directly opening the source code and official documentation of the v1.21.1 tag, we examine what the frequently used CRDs actually create during a reconcile, how mons a

  2026-10-28 · 33 min read #Rook#Ceph#쿠버네티스#오퍼레이터#CSI

• Rook-Ceph Explanations Part 1: Where and How Ceph Places Data

  Ceph provides block, file, and object storage within a single system. At its core is a distributed object store called RADOS, and there is no central catalog recording data locations. Clients receive a cluster map from a

  2026-10-28 · 25 min read #Ceph#Rook#스토리지#분산 스토리지#쿠버네티스