Difference between revisions of "Kubernetes Downward API"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
** <code>[[metadata.name]]</code> | ** <code>[[metadata.name]]</code> | ||
** <code>[[metadata.namespace]]</code> | ** <code>[[metadata.namespace]]</code> | ||
| + | ** <code>[[metadata.uid]]</code> | ||
| + | ** <code>[[metadata.annotations['<KEY>']</code> | ||
| + | |||
| + | |||
* <code>[[resourceFieldRef]]</code> | * <code>[[resourceFieldRef]]</code> | ||
** [[resource: limits.cpu]] | ** [[resource: limits.cpu]] | ||
Revision as of 11:08, 8 December 2022
fieldRef:metadata.namemetadata.namespacemetadata.uid[[metadata.annotations['<KEY>']
Related
- Read Expose Pod Information to Containers Through Files, https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/
Kubernetes, env:
See also
- Kubernetes: distributions, tools, CKA, CKS, Kubernetes interfaces: CSI, CNI, installation, workloads, networking,
kubeadm,Kubernetes API, Kubernetes API Server,kubectl, kubeadm, kubelet, kube-proxy, Cloud services: EKS, GKE, TKE, DKS, Helm, Kubernetes RBAC, Kubernetes deployments, Minikube, Rancher, OpenShift, Charmed Kubernetes, Ingress, Kubernetes scheduler, Kubernetes Finalizers, logging, Kubernetes operator, Orka,kind:, Kubernetes namespaces, Kubernetes dashboard, Kubernetes Metrics Server, Field Selectors, CoreDNS, CRI, Kubernetes Topology Manager, Kubernetes governance: (SIG, KEP), Kustomize, controllers,ReadinessProbe, LivenessProbe, KOPS, K9s, Kui, k3s, ImagePullBackOff, PDB, EndPoints, Kots, metadata, Karpenter, Replicated.com, Kubernetes Authenticating, Kubernetes timeline, Changelog/Versions, service accounts, Kubernetes Pod Lifecycle, Kubernetes Conformance Certified, Kubernetes backup, Kubernetes Pod Security Admission, tEKS, Kubernetes events, Kubernetes ports, Kubernetes policies, Connect, addons, DoKC, Kubernetes control plane, Kubernetes Federation, Kubernetes info, Kubetest2, Sidecar (Kubernetes)
Advertising:
