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

FEATURE STATE: Kubernetes v1.26 [stable] Starting from Kubernetes v1.20, the kubelet can dynamically retrieve credentials for a container image registry using exec plugins. The kubelet and the exec plugin communicate through stdio (stdin, stdout, and stderr) using Kubernetes versioned APIs. These plugins allow the kubelet to request credentials for a container registry dynamically as opposed to storing static credentials on disk. For example, the plugin may talk to a local metadata server to retrieve short-lived credentials for an image that is being pulled by the kubelet.

This page shows how to configure Pods so that they will be assigned particular Quality of Service (QoS) classes. Kubernetes uses QoS classes to make decisions about evicting Pods when Node resources are exceeded. When Kubernetes creates a Pod it assigns one of these QoS classes to the Pod: Guaranteed Burstable BestEffort Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.

All of the APIs in Kubernetes that let you write persistent API resource data support at-rest encryption. For example, you can enable at-rest encryption for Secrets. This at-rest encryption is additional to any system-level encryption for the etcd cluster or for the filesystem(s) on hosts where you are running the kube-apiserver. This page shows how to switch from encryption of API data at rest, so that API data are stored unencrypted.

This page shows how to specify extended resources for a Node. Extended resources allow cluster administrators to advertise node-level resources that would otherwise be unknown to Kubernetes. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts.

This page shows a couple of quick ways to create a Calico cluster on Kubernetes. Before you begin Decide whether you want to deploy a cloud or local cluster. Creating a Calico cluster with Google Kubernetes Engine (GKE) Prerequisite: gcloud. To launch a GKE cluster with Calico, include the --enable-network-policy flag. Syntax gcloud container clusters create [CLUSTER_NAME] --enable-network-policy Example gcloud container clusters create my-calico-cluster --enable-network-policy To verify the deployment, use the following command.

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

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...