English ▾ English Français Português (Brasil) 简体中文 Topics ▾ Setup and Config git config help bugreport Credential hel...

English ▾ English Français Português (Brasil) 简体中文 Topics ▾ Setup and Config git config help bugreport Credential hel...

FastAPI framework, high performance, easy to learn, fast to code, ready for production

Your workload can discover Services within your cluster using DNS; this page explains how that works.

Storage capacity is limited and may vary depending on the node on which a pod runs: network-attached storage might not be accessible by all nodes, or storage is local to a node to begin with. FEATURE STATE: Kubernetes v1.24 [stable] This page describes how Kubernetes keeps track of storage capacity and how the scheduler uses that information to schedule Pods onto nodes that have access to enough storage capacity for the remaining missing volumes.

Kubernetes has various types of probes: Liveness probe Readiness probe Startup probe Liveness probe Liveness probes determine when to restart a container. For example, liveness probes could catch a deadlock when an application is running but unable to make progress. If a container fails its liveness probe repeatedly, the kubelet restarts the container. Liveness probes do not wait for readiness probes to succeed. If you want to wait before executing a liveness probe, you can either define initialDelaySeconds or use a startup probe.

FastAPI framework, high performance, easy to learn, fast to code, ready for production

FastAPI framework, high performance, easy to learn, fast to code, ready for production

FastAPI framework, high performance, easy to learn, fast to code, ready for production

FastAPI framework, high performance, easy to learn, fast to code, ready for production