Many applications rely on configuration which is used during either application initialization or runtime. Most times, there is a requirement to adjust values assigned to configuration parameters. ConfigMaps are a Kubernetes mechanism that let you inject configuration data into application pods. The ConfigMap concept allow you to decouple configuration artifacts from image content to keep containerized applications portable. For example, you can download and run the same container image to spin up containers for the purposes of local development, system test, or running a live end-user workload.

This page explains how to add versioning information to CustomResourceDefinitions, to indicate the stability level of your CustomResourceDefinitions or advance your API to a new version with conversion between API representations. It also describes how to upgrade an object from one version to another. 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.

FEATURE STATE: Kubernetes v1.35 [stable](enabled by default) This page shows you how to allocate devices to your Pods by using dynamic resource allocation (DRA). These instructions are for workload operators. Before reading this page, familiarize yourself with how DRA works and with DRA terminology like ResourceClaims and ResourceClaimTemplates. For more information, see Dynamic Resource Allocation (DRA). About device allocation with DRA As a workload operator, you can claim devices for your workloads by creating ResourceClaims or ResourceClaimTemplates.

This page shows how to run a replicated stateful application using a StatefulSet. This application is a replicated MySQL database. The example topology has a single primary server and multiple replicas, using asynchronous row-based replication. Note:This is not a production configuration. MySQL settings remain on insecure defaults to keep the focus on general patterns for running stateful applications in 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.

This page shows how a Pod can use a downwardAPI volume, to expose information about itself to containers running in the Pod. A downwardAPI volume can expose Pod fields and container fields. In Kubernetes, there are two ways to expose Pod and container fields to a running container: Environment variables Volume files, as explained in this task Together, these two ways of exposing Pod and container fields are called the downward API.

Skip to main content Back to top Ctrl + K Choose version GitHub X Mastodon What’s new in 3.0.0 (January 21, 2026) # T...

Skip to main content Back to top Ctrl + K Choose version GitHub X Mastodon What’s new in 2.0.0 (April 3, 2023) # Thes...

"h2o" March 12, 2026 Contents h2o-package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...

Docs » Module code » h2o.frame Source code for h2o.frame # -*- encoding: utf-8 -*- """ H2O...

Java Platform, Standard Edition Java Management Extensions Guide Release 16 E95075-04 April 2023 Java Platform, Standard Edition Java Management Extensions Guide, Release 16 E95075-04 Copyright © 1...