<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>分类：kubernetes - GodOne</title><link>https://blog.godone.top/categories/kubernetes</link><atom:link href="https://blog.godone.top/categories/kubernetes/feed/categories/kubernetes.xml" rel="self" type="application/rss+xml"/><description>GodOne</description><generator>Halo v2.27.1</generator><language>zh-cn</language><lastBuildDate>Mon, 16 Nov 2026 13:12:13 GMT</lastBuildDate><item><title><![CDATA[kubectl-污点策略]]></title><link>https://blog.godone.top/archives/%E6%B1%A1%E7%82%B9%E7%AD%96%E7%95%A5</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E6%B1%A1%E7%82%B9%E7%AD%96%E7%95%A5&amp;url=/archives/%E6%B1%A1%E7%82%B9%E7%AD%96%E7%95%A5" width="1" height="1" alt="" style="opacity:0;">创建资源时，默认会将资源分布部署在所有node节点上，如果需要在某node节点上部署更多资源或尽量不部署资源，可以用污点策略来达到需求 污点标签 NoSchedule 不会被调度 PreferNoSchedule 尽量不调度 NoExecute 驱逐节点（会对正在运行的容器生效） 查看污点标签 ku]]></description><guid isPermaLink="false">/archives/%E6%B1%A1%E7%82%B9%E7%AD%96%E7%95%A5</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:08 GMT</pubDate></item><item><title><![CDATA[kubectl-标签管理]]></title><link>https://blog.godone.top/archives/%E6%A0%87%E7%AD%BE%E7%AE%A1%E7%90%86</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E6%A0%87%E7%AD%BE%E7%AE%A1%E7%90%86&amp;url=/archives/%E6%A0%87%E7%AD%BE%E7%AE%A1%E7%90%86" width="1" height="1" alt="" style="opacity:0;">查看标签 kubectl get [资源类型] --show-labels [root@k8s-master k8s-ymls]# kubectl get pods --show-labels NAME READY STATU]]></description><guid isPermaLink="false">/archives/%E6%A0%87%E7%AD%BE%E7%AE%A1%E7%90%86</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:08 GMT</pubDate></item><item><title><![CDATA[kubectl-集群调度]]></title><link>https://blog.godone.top/archives/%E9%9B%86%E7%BE%A4%E8%B0%83%E5%BA%A6</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E9%9B%86%E7%BE%A4%E8%B0%83%E5%BA%A6&amp;url=/archives/%E9%9B%86%E7%BE%A4%E8%B0%83%E5%BA%A6" width="1" height="1" alt="" style="opacity:0;">扩容与缩减 kubectl scale deployment [deployment名称] --relicas=[副本数量] ## 查看deployment名称 [root@k8s-master k8s-ymls]# kubectl get deployments.apps NAME]]></description><guid isPermaLink="false">/archives/%E9%9B%86%E7%BE%A4%E8%B0%83%E5%BA%A6</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-资源监控]]></title><link>https://blog.godone.top/archives/%E8%B5%84%E6%BA%90%E7%9B%91%E6%8E%A7</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E8%B5%84%E6%BA%90%E7%9B%91%E6%8E%A7&amp;url=/archives/%E8%B5%84%E6%BA%90%E7%9B%91%E6%8E%A7" width="1" height="1" alt="" style="opacity:0;">metrics metrics是什么 metrics是一个监控系统资源使用的插件，可以监控node节点上的cpu、内存的使用率，或pod对资源的占用率，通过对资源占用的了解，可以更加合理的部署容器应用 metrics从kubernetes 1.8开始，资源使用情况的监控可以通过Metrics Api]]></description><guid isPermaLink="false">/archives/%E8%B5%84%E6%BA%90%E7%9B%91%E6%8E%A7</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-hostPath]]></title><link>https://blog.godone.top/archives/hostPath</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-hostPath&amp;url=/archives/hostPath" width="1" height="1" alt="" style="opacity:0;">hostPath可以把node节点的目录映射到容器内指定路径上，相当于Docker里的 -v 参数 --- apiVersion: apps/v1 kind: Deployment metadata: name: webnginx-deployment annotations: ku]]></description><guid isPermaLink="false">/archives/hostPath</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-PV／PVC]]></title><link>https://blog.godone.top/archives/PV%EF%BC%8FPVC</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-PV%EF%BC%8FPVC&amp;url=/archives/PV%EF%BC%8FPVC" width="1" height="1" alt="" style="opacity:0;">PV/PVC是什么 PersistentVolume（持久卷，简称PV） PV是资源的提供者，根据集群的基础设施变化而变化，由K8S集群管理员配置 Persistent VolumeClaim（持久卷声明，简称PVC） 而PVC是资源的使用者，根据业务服务的需求变化来配置 PV/PVC的引入使K8S]]></description><guid isPermaLink="false">/archives/PV%EF%BC%8FPVC</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-NFS]]></title><link>https://blog.godone.top/archives/NFS</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-NFS&amp;url=/archives/NFS" width="1" height="1" alt="" style="opacity:0;">在生产环境中经常需要多个Pod中共享数据，而这些应用又在不同的机器的不同Pod中，NFS可以来解决这个问题。 Kubernetes中通过简单的配置就可以挂载NFS到Pod中，而NFS中的数据是可以永久保存的，同时NFS支持并发写操作。 搭建NFS服务器 具体操作可见👉NFS服务器 创建PV/PVC资]]></description><guid isPermaLink="false">/archives/NFS</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-emptyDir]]></title><link>https://blog.godone.top/archives/emptyDir</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-emptyDir&amp;url=/archives/emptyDir" width="1" height="1" alt="" style="opacity:0;">emptyDir是最基础的Volume类型，用于存储临时数据的简单空目录。如果Pod设置了emptyDir类型的Volume，Pod被分配到Node上的时候，会创建emptyDir，只要Pod运行在Node上，emptyDir都会存在（包括容器挂掉的时候），但如果Pod从Node上被删除（Pod被删]]></description><guid isPermaLink="false">/archives/emptyDir</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-ConfigMap]]></title><link>https://blog.godone.top/archives/ConfigMap</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-ConfigMap&amp;url=/archives/ConfigMap" width="1" height="1" alt="" style="opacity:0;">ConfigMap概述 ConfigMap是什么 ConfigMap是在pod中映射（文件、目录）的一种方式，允许将配置文件与镜像文件分离，以使容器化的应用具有可移植性 PS ：ConfigMap的文件大小最大为1MB ConfigMap的作用 在日常工作中经常要修改各种配置文件的参数、数据库的地址]]></description><guid isPermaLink="false">/archives/ConfigMap</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-临时卷]]></title><link>https://blog.godone.top/archives/%E4%B8%B4%E6%97%B6%E5%8D%B7</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E4%B8%B4%E6%97%B6%E5%8D%B7&amp;url=/archives/%E4%B8%B4%E6%97%B6%E5%8D%B7" width="1" height="1" alt="" style="opacity:0;">有些应用程序需要额外的存储，但并不关心数据在重启后仍然可用，及是否被持久化存储。]]></description><guid isPermaLink="false">/archives/%E4%B8%B4%E6%97%B6%E5%8D%B7</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-NodePort]]></title><link>https://blog.godone.top/archives/NodePort</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-NodePort&amp;url=/archives/NodePort" width="1" height="1" alt="" style="opacity:0;">NodePort的本质为ipvs和iptables，所以它工作在第四层，专注与端口服务的发布 创建资源文件 --- kind: Service apiVersion: v1 metadata: name: nodeport-nginx spec: t]]></description><guid isPermaLink="false">/archives/NodePort</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-安装控制器]]></title><link>https://blog.godone.top/archives/%E5%AE%89%E8%A3%85%E6%8E%A7%E5%88%B6%E5%99%A8</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-%E5%AE%89%E8%A3%85%E6%8E%A7%E5%88%B6%E5%99%A8&amp;url=/archives/%E5%AE%89%E8%A3%85%E6%8E%A7%E5%88%B6%E5%99%A8" width="1" height="1" alt="" style="opacity:0;">导入镜像包，重新打标签 上传镜像到私有仓库 修改资源文件中的镜像地址为私有仓库地址，注释proxy-real-ip-cidr行 --- apiVersion: v1 kind: Namespace metadata: labels: app.kuber]]></description><guid isPermaLink="false">/archives/%E5%AE%89%E8%A3%85%E6%8E%A7%E5%88%B6%E5%99%A8</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:07 GMT</pubDate></item><item><title><![CDATA[kubectl-Ingress]]></title><link>https://blog.godone.top/archives/Ingress</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-Ingress&amp;url=/archives/Ingress" width="1" height="1" alt="" style="opacity:0;">ingress的本质就是nginx+ipvs，与NodePort的区别是，ingress更适用于7层服务（web） 使用ingress需要先安装ingress控制器，导入镜像到私有仓库，修改资源文件中的镜像地址为私有仓库地址后使用资源文件创建 --- apiVersion: networking.k]]></description><guid isPermaLink="false">/archives/Ingress</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-ClusterIP]]></title><link>https://blog.godone.top/archives/ClusterIP</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-ClusterIP&amp;url=/archives/ClusterIP" width="1" height="1" alt="" style="opacity:0;">ClusterIP、Headles创建的service只能在集群内部里访问 --- kind: Service apiVersion: v1 metadata: name: nginx spec: ports: - protocol: TCP port: 80 targe]]></description><guid isPermaLink="false">/archives/ClusterIP</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-service]]></title><link>https://blog.godone.top/archives/service</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-service&amp;url=/archives/service" width="1" height="1" alt="" style="opacity:0;">pod的IP会经常变动不易于访问，我们可以创建一个service，给目标pod绑定一个固定的ClusterIP，访问ClusterIP就会访问目标pod。service默认会启用ipvs负载均衡。 Service允许指定一个Type类型，默认是ClusterIP ClusterIP：通过集群内部IP]]></description><guid isPermaLink="false">/archives/service</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-job]]></title><link>https://blog.godone.top/archives/job</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-job&amp;url=/archives/job" width="1" height="1" alt="" style="opacity:0;">job资源类型用于定义并启动一个批处理任务。Job 负责批量处理短暂的一次性任务，即仅执行一次的任务，执行完成后结束生命周期。 --- apiVersion: batch/v1 kind: Job metadata: name: job-pi spec: template: spec]]></description><guid isPermaLink="false">/archives/job</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-deployment]]></title><link>https://blog.godone.top/archives/deployment</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-deployment&amp;url=/archives/deployment" width="1" height="1" alt="" style="opacity:0;">--- #资源定义起始标准 apiVersion: apps/v1 #当前资源类型版本 kind: Deployment #当前创建资源类型 metadata: #元数据 name: nginx-deployment]]></description><guid isPermaLink="false">/archives/deployment</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-daemonset]]></title><link>https://blog.godone.top/archives/daemonset</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-daemonset&amp;url=/archives/daemonset" width="1" height="1" alt="" style="opacity:0;">daemonset与deployment的区别是daemonset的副本数量不由用户指定，而是有几个node节点就有几个daemonset副本 --- #资源定义起始标准 apiVersion: apps/v1]]></description><guid isPermaLink="false">/archives/daemonset</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-cronjob]]></title><link>https://blog.godone.top/archives/cronjob</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-cronjob&amp;url=/archives/cronjob" width="1" height="1" alt="" style="opacity:0;">cronjob是在job基础上加上了定时执行，每次执行都会新建一个job和pod（默认会保存三个正常副本和一个错误副本） --- apiVersion: batch/v1 kind: CronJob metadata: name: cronjob-pi spec: schedule: "*/]]></description><guid isPermaLink="false">/archives/cronjob</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item><item><title><![CDATA[kubectl-Master／Node 节点重启后会重建容器]]></title><link>https://blog.godone.top/archives/Master%EF%BC%8FNode-%E8%8A%82%E7%82%B9%E9%87%8D%E5%90%AF%E5%90%8E%E4%BC%9A%E9%87%8D%E5%BB%BA%E5%AE%B9%E5%99%A8</link><description><![CDATA[<img src="https://blog.godone.top/plugins/feed/assets/telemetry.gif?title=kubectl-Master%EF%BC%8FNode%20%E8%8A%82%E7%82%B9%E9%87%8D%E5%90%AF%E5%90%8E%E4%BC%9A%E9%87%8D%E5%BB%BA%E5%AE%B9%E5%99%A8&amp;url=/archives/Master%EF%BC%8FNode-%E8%8A%82%E7%82%B9%E9%87%8D%E5%90%AF%E5%90%8E%E4%BC%9A%E9%87%8D%E5%BB%BA%E5%AE%B9%E5%99%A8" width="1" height="1" alt="" style="opacity:0;">当资源文件里的镜像地址指定镜像版本为:latest时，重启master或node节点后，集群会重新拉取镜像来重建容器 如何避免不必要的镜像拉取？ 不要使用:latest 标签，改用指定版本（如 :v1.2.3） 在资源文件内设置imagePullPolicy: IfNotPresent参数 镜像写法]]></description><guid isPermaLink="false">/archives/Master%EF%BC%8FNode-%E8%8A%82%E7%82%B9%E9%87%8D%E5%90%AF%E5%90%8E%E4%BC%9A%E9%87%8D%E5%BB%BA%E5%AE%B9%E5%99%A8</guid><dc:creator>GodOne</dc:creator><category>kubectl</category><category>kubernetes</category><pubDate>Sun, 1 Nov 2026 17:12:06 GMT</pubDate></item></channel></rss>