如果只用一句话描述 Kubernetes，可以这样说：
Kubernetes 是一个以声明式 API 为核心的集群控制系统：你声明舰队应该长成什么样，它持续把现实世界拉回那个样子。
你真正需要建立的，不是“对象背诵表”，而是这套顺序感：
- 先理解 Pod 是什么，为什么它是短暂的
- 再理解为什么日常要用 Deployment，而不是裸 Pod
- 再理解 Service 为什么存在，它在给谁稳定
- 然后理解 ConfigMap / Secret 是如何把“镜像”和“环境”分开
- 再看 Ingress 如何接住外部流量
- 最后看 Scheduler、自愈、扩缩容，明白 Kubernetes 为什么像一个“活着的控制系统”
当你形成这套顺序，Kubernetes 就不再是一堆 YAML 名词，而是一支有指挥部、有母舰、有任务舱、有总机、有关口、会自动补兵的星际舰队。
#官方来源链接清单
- https://kubernetes.io/docs/home/
- https://kubernetes.io/docs/concepts/overview/working-with-objects/
- https://kubernetes.io/docs/concepts/architecture/
- https://kubernetes.io/docs/concepts/architecture/nodes/
- https://kubernetes.io/docs/concepts/workloads/pods/
- https://kubernetes.io/docs/concepts/workloads/controllers/deployment/
- https://kubernetes.io/docs/concepts/services-networking/service/
- https://kubernetes.io/docs/concepts/configuration/configmap/
- https://kubernetes.io/docs/concepts/configuration/secret/
- https://kubernetes.io/docs/concepts/services-networking/ingress/
- https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
- https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
- https://kubernetes.io/docs/concepts/architecture/self-healing/
- https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/
- https://kubernetes.io/docs/concepts/cluster-administration/node-autoscaling/
- https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/