Difference between revisions of "Kubernetes resources:"
Jump to navigation
Jump to search
m (Ant moved page Resources: (Kubernetes) to Kubernetes resources:) |
|||
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
resources: | resources: | ||
| − | requests: | + | [[requests:]] |
[[memory:]] "64Mi" | [[memory:]] "64Mi" | ||
[[cpu:]] "250m" | [[cpu:]] "250m" | ||
| − | limits: | + | [[limits:]] |
[[memory:]] "128Mi" | [[memory:]] "128Mi" | ||
[[cpu:]] "500m" | [[cpu:]] "500m" | ||
Revision as of 19:06, 21 December 2022
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
Related
autoScaler:restartPolicy:Xmx- CKA Understand how resource limits can affect Pod scheduling
- kubectl describe nodes (conditions:)
See also
- Kubernetes restartPolicy,
resources:, autoScaler: - 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:
