Pod [page]deterministic

`apiVersion: v1`

`import "k8s.io/api/core/v1"`

## Pod {#Pod}

Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.

<hr>

<table> <thead><tr><th>Field</th><th>Description</th></tr></thead> <tbody> <tr> <td><code>apiVersion</code><br/><em>string</em></td> <td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</td> </tr> <tr> <td><code>kind</code><br/><em>string</em></td> <td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</td> </tr> <tr> <td><code>metadata</code><br/><em><a href="">ObjectMeta</a></em></td> <td>Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</td> </tr> <tr> <td><code>spec</code><br/><em><a href="">PodSpec</a></em></td> <td>Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</td> </tr> <tr> <td><code>status</code><br/><em><a href="">PodStatus</a></em></td> <td>Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</td> </tr> </tbody> </table>

## PodSpec {#PodSpec}

PodSpec is a description of a pod.

<hr>

<table> <thead><tr><th>Field</th><th>Description</th></tr></thead> <tbody> <tr> <td><code>activeDeadlineSeconds</code><br/><em>integer</em></td> <td>Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.</td> </tr> <tr> <td><code>affinity</code><br/><em><a href="">Affinity</a></em></td> <td>If specified, the pod's scheduling constraints</td> </tr> <tr> <td><code>automountServiceAccountToken</code><br/><em>boolean</em></td> <td>AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.</td> </tr> <tr> <td><code>containers</code>&nbsp;<strong>*</strong><br/><em><a href="">Container array</a></em><br/><em>patch strategy: merge on key <code>name</code></em></td> <td>List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.</td> </tr> <tr> <td><code>dnsConfig</code><br/><em><a href="">PodDNSConfig</a></em></td> <td>Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.</td> </tr> <tr> <td><code>dnsPolicy</code><br/><em>string</em></td> <td>Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'.<br/><br/>Possible enum values:<br/> - `"ClusterFirst"` indicates that the pod should use cluster DNS first unless hostNetwork is true, if it is available, then fall back on the default (as determined by kubelet) DNS settings.<br/> - `"ClusterFirstWithHost …(trimmed)