<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>K8s - 分类 - Qzai&#39;s Blog</title>
        <link>https://example.com/categories/k8s/</link>
        <description>K8s - 分类 - Qzai&#39;s Blog</description>
        <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>ixiaoqiang0011@gmail.com (Qzai)</managingEditor>
            <webMaster>ixiaoqiang0011@gmail.com (Qzai)</webMaster><lastBuildDate>Thu, 27 Feb 2025 00:00:00 &#43;0000</lastBuildDate><atom:link href="https://example.com/categories/k8s/" rel="self" type="application/rss+xml" /><item>
    <title>k8s 运维与故障排查</title>
    <link>https://example.com/posts/container/k8s-11-operations-and-troubleshooting/</link>
    <pubDate>Thu, 27 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-11-operations-and-troubleshooting/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729163059260.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>生产级集群的稳定性依赖成熟的运维手段与可复用的排障路径。本文覆盖集群升级策略、etcd 与 Velero 备份恢复、分层故障诊断方法论，以及 kubectl debug 临时容器等实战技能。掌握这些内容，能在事故发生时快速定位根因并恢复服务。</p>]]></description>
</item>
<item>
    <title>k8s 托管平台与生产部署</title>
    <link>https://example.com/posts/container/k8s-10-managed-platforms-and-deployment/</link>
    <pubDate>Sat, 22 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-10-managed-platforms-and-deployment/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729163058852.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Kubernetes 集群的运维成本集中在控制平面与底层组件的升级、证书轮转、etcd 备份等环节，托管平台将这些负担转移给云厂商，让团队聚焦业务负载的编排与发布。选型的核心矛盾在于控制权与运维成本的权衡，不同规模和合规要求的团队会走向截然不同的方案。本文梳理自建与托管的技术边界，对比国际云、国内云、私有化 PaaS 三类平台的特性差异，并给出从本地集群迁移到生产托管的实操路径。</p>]]></description>
</item>
<item>
    <title>k8s 可观测性</title>
    <link>https://example.com/posts/container/k8s-09-observability/</link>
    <pubDate>Mon, 17 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-09-observability/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729163058484.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Kubernetes 集群中工作负载动态调度、频繁更迭，传统的登录节点排障方式已无法跟上节奏。可观测性通过日志、指标、链路三个维度，将集群内部状态转化为可查询、可告警的数据。本文围绕三支柱模型展开，覆盖日志采集、Prometheus 监控栈、Event 查询、链路追踪与告警体系的实战配置。</p>]]></description>
</item>
<item>
    <title>k8s 安全与认证授权</title>
    <link>https://example.com/posts/container/k8s-08-security-rbac/</link>
    <pubDate>Wed, 12 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-08-security-rbac/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729163057645.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Kubernetes 的安全模型由认证、授权、准入控制三道关卡串联组成，任何一个 API 请求都要依次通过这三层校验才能写入 etcd。ServiceAccount 是 Pod 在集群中的身份凭证，RBAC 则定义了这个身份能操作哪些资源。掌握这套链路，才能在多租户和生产环境中精准控制权限边界。</p>]]></description>
</item>
<item>
    <title>k8s 调度与自动伸缩</title>
    <link>https://example.com/posts/container/k8s-07-scheduling-and-autoscaling/</link>
    <pubDate>Fri, 07 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-07-scheduling-and-autoscaling/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729161625804.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Kubernetes 把 Pod 放到哪个节点上运行，由调度器决定；Pod 数量随负载增减，则由自动伸缩机制负责。调度和伸缩是集群资源利用率的两个核心杠杆，前者决定资源分配的合理性，后者决定系统面对流量波动的弹性能力。掌握这两层机制，才能在成本与稳定性之间找到平衡点。</p>]]></description>
</item>
<item>
    <title>k8s 配置与密钥管理</title>
    <link>https://example.com/posts/container/k8s-06-config-and-secrets/</link>
    <pubDate>Sat, 01 Feb 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-06-config-and-secrets/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729161625390.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>将配置和凭据从镜像中剥离，是云原生部署的基础能力。Kubernetes 提供 ConfigMap 和 Secret 两类对象，分别承载普通配置与敏感数据，通过环境变量或 Volume 两条途径注入容器。掌握它们的注入差异、热更新边界以及与镜像解耦的实践模式，才能写出可跨环境复用的部署清单。</p>]]></description>
</item>
<item>
    <title>k8s 存储管理</title>
    <link>https://example.com/posts/container/k8s-05-storage-management/</link>
    <pubDate>Mon, 27 Jan 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-05-storage-management/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729161624260.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>容器文件系统随 Pod 销毁而消失，有状态应用需要数据持久化才能正常运行。K8s 通过 Volume 机制把外部存储挂载进容器，又以 PV/PVC/StorageClass 三层抽象解耦存储供给与消费，让应用开发者无需关心底层存储实现。本篇梳理 Volume 类型与持久化抽象、静态与动态供给差异、Pod 挂载全流程，以及 CSI 插件机制与主流存储后端。</p>]]></description>
</item>
<item>
    <title>k8s 服务发现与网络</title>
    <link>https://example.com/posts/container/k8s-04-service-discovery-and-networking/</link>
    <pubDate>Wed, 22 Jan 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-04-service-discovery-and-networking/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729160522461.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Pod 的 IP 随销毁重建而变化，直接以 Pod IP 通信在滚动更新等场景下会立即断裂。Service 在 Pod 之上提供稳定的虚拟 IP 和 DNS 名称，将流量分发到一组后端 Pod，是 K8s 内部服务间通信的基石。本篇拆解 Service 四种类型、kube-proxy 转发链路、Ingress 七层路由与 NetworkPolicy 隔离策略，并给出可直接复制的实操 YAML。</p>]]></description>
</item>
<item>
    <title>k8s 工作负载管理</title>
    <link>https://example.com/posts/container/k8s-03-workload-management/</link>
    <pubDate>Fri, 17 Jan 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-03-workload-management/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729160522034.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>Pod 是 Kubernetes 中最小的调度单元，但直接管理零散的 Pod 既无法保证副本数量，也难以应对滚动更新与故障恢复。工作负载控制器在 Pod 之上抽象出一层管理逻辑，把&quot;期望状态&quot;与&quot;实际状态&quot;的调和交给控制平面完成。掌握 Deployment、StatefulSet、DaemonSet、Job 四种核心控制器的适用边界与协作机制，是在生产集群中稳定运行业务的前提。</p>]]></description>
</item>
<item>
    <title>k8s 集群搭建与 kubectl 实操</title>
    <link>https://example.com/posts/container/k8s-02-cluster-setup-and-kubectl/</link>
    <pubDate>Sun, 12 Jan 2025 00:00:00 &#43;0000</pubDate>
    <author>ixiaoqiang0011@gmail.com (Qzai)</author>
    <guid>https://example.com/posts/container/k8s-02-cluster-setup-and-kubectl/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="https://img.zhaojq.top/20260729160521026.jpg" referrerpolicy="no-referrer">
            </div><h2 id="导读">导读</h2>
<p>本篇解决本地 K8s 学习链路上的三个核心问题：用什么工具在单机上拉起一个可用的集群、kubectl 命令体系如何覆盖日常运维动作、怎样把一个 nginx Deployment 跑起来并从本机访问到它。选型上以 kind 为主力，因为它启动快、资源占用低，且能直接复用本机已有的 Docker 环境。</p>]]></description>
</item>
</channel>
</rss>
