As the Kubernetes API evolves, APIs are periodically reorganized or upgraded. When APIs evolve, the old API is deprecated and eventually removed. This page contains information you need to know when migrating from deprecated API versions to newer and more stable API versions. Removed APIs by release v1.32 The v1.32 release will stop serving the following deprecated API versions: Flow control resources The flowcontrol.apiserver.k8s.io/v1beta3 API version of FlowSchema and PriorityLevelConfiguration will no longer be served in v1.

This page provides a real world example of how to configure Redis using a ConfigMap and builds upon the Configure a Pod to Use a ConfigMap task. Objectives Create a ConfigMap with Redis configuration values Create a Redis Pod that mounts and uses the created ConfigMap Verify that the configuration was correctly applied. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.

Stateful Applications StatefulSet Basics Example: Deploying WordPress and MySQL with Persistent Volumes Example: Depl...

Configuration Example: Configuring a Java Microservice Updating Configuration via a ConfigMap Configuring Redis using...

Synopsis Experimental: Check who you are and your attributes (groups, extra). This command is helpful to get yourself aware of the current user attributes, especially when dynamic authentication, e.g., token webhook, auth proxy, or OIDC provider, is enabled in the Kubernetes cluster. kubectl auth whoami Examples # Get your subject attributes. kubectl auth whoami # Get your subject attributes in JSON format. kubectl auth whoami -o json Options --allow-missing-template-keys     Default: true If true, ignore any errors in templates when a field or map key is missing in the template.

When running Kubernetes in an environment with strict network boundaries, such as on-premises datacenter with physical network firewalls or Virtual Networks in Public Cloud, it is useful to be aware of the ports and protocols used by Kubernetes components. Control plane Protocol Direction Port Range Purpose Used By TCP Inbound 6443 Kubernetes API server All TCP Inbound 2379-2380 etcd server client API kube-apiserver, etcd TCP Inbound 10250 Kubelet API Self, Control plane TCP Inbound 10259 kube-scheduler Self TCP Inbound 10257 kube-controller-manager Self Although etcd ports are included in control plane section, you can also host your own etcd cluster externally or on custom ports.

kubectl is the Kubernetes cli version of a swiss army knife, and can do many things. While this Book is focused on using kubectl to declaratively manage applications in Kubernetes, it also covers other kubectl functions. Command Families Most kubectl commands typically fall into one of a few categories: Type Used For Description Declarative Resource Management Deployment and operations (e.g. GitOps) Declaratively manage Kubernetes workloads using resource configuration Imperative Resource Management Development Only Run commands to manage Kubernetes workloads using Command Line arguments and flags Printing Workload State Debugging Print information about workloads Interacting with Containers Debugging Exec, attach, cp, logs Cluster Management Cluster operations Drain and cordon Nodes Declarative Application Management The preferred approach for managing resources is through declarative files called resource configuration used with the kubectl Apply command.

Synopsis Creates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster. Looks up a deployment, replica set, stateful set, or replication controller by name and creates an autoscaler that uses the given resource as a reference. An autoscaler can automatically increase or decrease number of pods deployed within the system as needed. kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] Examples # Auto scale a deployment "foo", with the number of pods between 2 and 10, no target CPU utilization specified so a default autoscaling policy will be used kubectl autoscale deployment foo --min=2 --max=10 # Auto scale a replication controller "foo", with the number of pods between 1 and 5, target CPU utilization at 80% kubectl autoscale rc foo --max=5 --cpu-percent=80 Options --allow-missing-template-keys     Default: true If true, ignore any errors in templates when a field or map key is missing in the template.

This command prints the version of kubeadm. Print the version of kubeadm Synopsis Print the version of kubeadm kubeadm version [flags] Options -h, --help help for version -o, --output string Output format; available options are 'yaml', 'json' and 'short' Options inherited from parent commands --rootfs string [EXPERIMENTAL] The path to the 'real' host root filesystem.

Resource Types CredentialProviderConfig CredentialProviderConfig CredentialProviderConfig is the configuration containing information about each exec credential provider. Kubelet reads this configuration from disk and enables each provider as specified by the CredentialProvider type. FieldDescription apiVersionstringkubelet.config.k8s.io/v1alpha1 kindstringCredentialProviderConfig providers [Required] []CredentialProvider providers is a list of credential provider plugins that will be enabled by the kubelet. Multiple providers may match against a single image, in which case credentials from all providers will be returned to the kubelet.