k8s:core:kind
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| k8s:core:kind [2026/05/31 03:49] – phong2018 | k8s:core:kind [2026/05/31 04:07] (current) – [Here's the relationship diagram.] phong2018 | ||
|---|---|---|---|
| Line 357: | Line 357: | ||
| ---- | ---- | ||
| + | |||
| + | ===== Here's the relationship diagram. ===== | ||
| + | Hierarchy flows top-down: | ||
| + | |||
| + | Deployment → ReplicaSet → Pod (Deployment manages replicas, which manage pods) | ||
| + | |||
| + | StatefulSet and DaemonSet go straight to their own Pods | ||
| + | |||
| + | CronJob → Job (CronJob triggers Jobs on a schedule) | ||
| + | |||
| + | Networking routes traffic inward: | ||
| + | |||
| + | Ingress → Service → Pod (external HTTP traffic funneled down to running containers) | ||
| + | |||
| + | NetworkPolicy applies traffic rules at the Pod level | ||
| + | |||
| + | Config and Storage are mounted into Pods: | ||
| + | |||
| + | ConfigMap and Secret are injected as env vars or volume mounts (dashed lines) | ||
| + | |||
| + | PVC (PersistentVolumeClaim) binds to a PV (PersistentVolume) and mounts into Pods | ||
| + | |||
| + | Everything lives inside a `Namespace for isolation. | ||
| + | |||
| + | {{ : | ||
| ===== See Also ===== | ===== See Also ===== | ||
k8s/core/kind.1780199357.txt.gz · Last modified: by phong2018
