= v1beta2.DaemonSet
{product-author}
{product-version}
:data-uri:
:icons:
:toc: macro
:toc-title:
:toclevels: 2

toc::[]

== Description
[%hardbreaks]
DEPRECATED - This group version of DaemonSet is deprecated by apps/v1/DaemonSet. See the release notes for more information. DaemonSet represents the configuration of a daemon set.

== Object Schema
Expand or mouse-over a field for more information about it.

++++
<pre>
<div style="margin-left:13px;"><span title="(string) 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/api-conventions.md#resources">apiVersion</span>:
</div><div style="margin-left:13px;"><span title="(string) 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/api-conventions.md#types-kinds">kind</span>:
</div><details open><summary><span title="(v1.ObjectMeta) Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">metadata</span>:
</summary><details><summary>  <span title="(object) Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations">annotations</span>:
</summary><div style="margin-left:13px;">    <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">  <span title="(string) The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.">clusterName</span>:
</div><div style="margin-left:13px;">  <span title="(v1.Time) CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.

Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">creationTimestamp</span>:
</div><div style="margin-left:13px;">  <span title="(integer) Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.">deletionGracePeriodSeconds</span>:
</div><div style="margin-left:13px;">  <span title="(v1.Time) DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.

Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">deletionTimestamp</span>:
</div><details><summary>  <span title="(array) Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.">finalizers</span>:
</summary><div style="margin-left:13px;">  - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">  <span title="(string) GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.

If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).

Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency">generateName</span>:
</div><div style="margin-left:13px;">  <span title="(integer) A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.">generation</span>:
</div><details><summary>  <span title="(v1.Initializers) An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven&#39;t explicitly asked to observe uninitialized objects.

When an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user.">initializers</span>:
</summary><details><summary>    <span title="(array) Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients.">pending</span>:
</summary><div style="margin-left:13px;">    - <span title="(string) name of the process that is responsible for initializing this object.">name</span>:
</div></details><details><summary>    <span title="(v1.Status) If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion.">result</span>:
</summary><div style="margin-left:13px;">      <span title="(string) 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/api-conventions.md#resources">apiVersion</span>:
</div><div style="margin-left:13px;">      <span title="(integer) Suggested HTTP return code for this status, 0 if not set.">code</span>:
</div><details><summary>      <span title="(v1.StatusDetails) Extended data associated with the reason.  Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.">details</span>:
</summary><details><summary>        <span title="(array) The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.">causes</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed.  Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.

Examples:
  &#34;name&#34; - the field &#34;name&#34; on the current resource
  &#34;items[0].name&#34; - the field &#34;name&#34; on the first array entry in &#34;items&#34;">field</span>:
</div><div style="margin-left:13px;">          <span title="(string) A human-readable description of the cause of the error.  This field may be presented as-is to a reader.">message</span>:
</div><div style="margin-left:13px;">          <span title="(string) A machine-readable description of the cause of the error. If this value is empty there is no information available.">reason</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) The group attribute of the resource associated with the status StatusReason.">group</span>:
</div><div style="margin-left:13px;">        <span title="(string) The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">        <span title="(string) The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).">name</span>:
</div><div style="margin-left:13px;">        <span title="(integer) If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.">retryAfterSeconds</span>:
</div><div style="margin-left:13px;">        <span title="(string) UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) 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/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">      <span title="(string) A human-readable description of the status of this operation.">message</span>:
</div><details><summary>      <span title="(v1.ListMeta) Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">metadata</span>:
</summary><div style="margin-left:13px;">        <span title="(string) continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.">continue</span>:
</div><div style="margin-left:13px;">        <span title="(string) String that identifies the server&#39;s internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency">resourceVersion</span>:
</div><div style="margin-left:13px;">        <span title="(string) selfLink is a URL representing this object. Populated by the system. Read-only.">selfLink</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) A machine-readable description of why this operation is in the &#34;Failure&#34; status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.">reason</span>:
</div><div style="margin-left:13px;">      <span title="(string) Status of the operation. One of: &#34;Success&#34; or &#34;Failure&#34;. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status">status</span>:
</div></details></details><details><summary>  <span title="(object) Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels">labels</span>:
</summary><div style="margin-left:13px;">    <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">  <span title="(string) Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names">name</span>:
</div><div style="margin-left:13px;">  <span title="(string) Namespace defines the space within each name must be unique. An empty namespace is equivalent to the &#34;default&#34; namespace, but &#34;default&#34; is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.

Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces">namespace</span>:
</div><details><summary>  <span title="(array) List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.">ownerReferences</span>:
</summary><div style="margin-left:13px;">  - <span title="(string) API version of the referent.">apiVersion</span>:
</div><div style="margin-left:13px;">    <span title="(boolean) If true, AND if the owner has the &#34;foregroundDeletion&#34; finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs &#34;delete&#34; permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.">blockOwnerDeletion</span>:
</div><div style="margin-left:13px;">    <span title="(boolean) If true, this reference points to the managing controller.">controller</span>:
</div><div style="margin-left:13px;">    <span title="(string) Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">    <span title="(string) Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names">name</span>:
</div><div style="margin-left:13px;">    <span title="(string) UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><div style="margin-left:13px;">  <span title="(string) An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.

Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency">resourceVersion</span>:
</div><div style="margin-left:13px;">  <span title="(string) SelfLink is a URL representing this object. Populated by the system. Read-only.">selfLink</span>:
</div><div style="margin-left:13px;">  <span title="(string) UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.

Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><details open><summary><span title="(v1beta2.DaemonSetSpec) The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status">spec</span>:
</summary><div style="margin-left:13px;">  <span title="(integer) The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).">minReadySeconds</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.">revisionHistoryLimit</span>:
</div><details><summary>  <span title="(v1.LabelSelector) A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors">selector</span>:
</summary><details><summary>    <span title="(array) matchExpressions is a list of label selector requirements. The requirements are ANDed.">matchExpressions</span>:
</summary><div style="margin-left:13px;">    - <span title="(string) key is the label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">      <span title="(string) operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.">operator</span>:
</div><details><summary>      <span title="(array) values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">      - <span title="(string)">[string]</span>:
</div></details></details><details><summary>    <span title="(object) matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.">matchLabels</span>:
</summary><div style="margin-left:13px;">      <span title="(string)">[string]</span>:
</div></details></details><details><summary>  <span title="(v1.PodTemplateSpec) An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template&#39;s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template">template</span>:
</summary><details><summary>    <span title="(v1.ObjectMeta) Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">metadata</span>:
</summary><details><summary>      <span title="(object) Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations">annotations</span>:
</summary><div style="margin-left:13px;">        <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.">clusterName</span>:
</div><div style="margin-left:13px;">      <span title="(v1.Time) CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.

Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">creationTimestamp</span>:
</div><div style="margin-left:13px;">      <span title="(integer) Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.">deletionGracePeriodSeconds</span>:
</div><div style="margin-left:13px;">      <span title="(v1.Time) DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested.

Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata">deletionTimestamp</span>:
</div><details><summary>      <span title="(array) Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.">finalizers</span>:
</summary><div style="margin-left:13px;">      - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server.

If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).

Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency">generateName</span>:
</div><div style="margin-left:13px;">      <span title="(integer) A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.">generation</span>:
</div><details><summary>      <span title="(v1.Initializers) An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven&#39;t explicitly asked to observe uninitialized objects.

When an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user.">initializers</span>:
</summary><details><summary>        <span title="(array) Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients.">pending</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) name of the process that is responsible for initializing this object.">name</span>:
</div></details><details><summary>        <span title="(v1.Status) If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion.">result</span>:
</summary><div style="margin-left:13px;">          <span title="(string) 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/api-conventions.md#resources">apiVersion</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Suggested HTTP return code for this status, 0 if not set.">code</span>:
</div><details><summary>          <span title="(v1.StatusDetails) Extended data associated with the reason.  Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.">details</span>:
</summary><details><summary>            <span title="(array) The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.">causes</span>:
</summary><div style="margin-left:13px;">            - <span title="(string) The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed.  Fields may appear more than once in an array of causes due to fields having multiple errors. Optional.

Examples:
  &#34;name&#34; - the field &#34;name&#34; on the current resource
  &#34;items[0].name&#34; - the field &#34;name&#34; on the first array entry in &#34;items&#34;">field</span>:
</div><div style="margin-left:13px;">              <span title="(string) A human-readable description of the cause of the error.  This field may be presented as-is to a reader.">message</span>:
</div><div style="margin-left:13px;">              <span title="(string) A machine-readable description of the cause of the error. If this value is empty there is no information available.">reason</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) The group attribute of the resource associated with the status StatusReason.">group</span>:
</div><div style="margin-left:13px;">            <span title="(string) The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">            <span title="(string) The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).">name</span>:
</div><div style="margin-left:13px;">            <span title="(integer) If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.">retryAfterSeconds</span>:
</div><div style="margin-left:13px;">            <span title="(string) UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) 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/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">          <span title="(string) A human-readable description of the status of this operation.">message</span>:
</div><details><summary>          <span title="(v1.ListMeta) Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">metadata</span>:
</summary><div style="margin-left:13px;">            <span title="(string) continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.">continue</span>:
</div><div style="margin-left:13px;">            <span title="(string) String that identifies the server&#39;s internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency">resourceVersion</span>:
</div><div style="margin-left:13px;">            <span title="(string) selfLink is a URL representing this object. Populated by the system. Read-only.">selfLink</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) A machine-readable description of why this operation is in the &#34;Failure&#34; status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.">reason</span>:
</div><div style="margin-left:13px;">          <span title="(string) Status of the operation. One of: &#34;Success&#34; or &#34;Failure&#34;. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status">status</span>:
</div></details></details><details><summary>      <span title="(object) Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels">labels</span>:
</summary><div style="margin-left:13px;">        <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names">name</span>:
</div><div style="margin-left:13px;">      <span title="(string) Namespace defines the space within each name must be unique. An empty namespace is equivalent to the &#34;default&#34; namespace, but &#34;default&#34; is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty.

Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces">namespace</span>:
</div><details><summary>      <span title="(array) List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.">ownerReferences</span>:
</summary><div style="margin-left:13px;">      - <span title="(string) API version of the referent.">apiVersion</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) If true, AND if the owner has the &#34;foregroundDeletion&#34; finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs &#34;delete&#34; permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.">blockOwnerDeletion</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) If true, this reference points to the managing controller.">controller</span>:
</div><div style="margin-left:13px;">        <span title="(string) Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds">kind</span>:
</div><div style="margin-left:13px;">        <span title="(string) Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names">name</span>:
</div><div style="margin-left:13px;">        <span title="(string) UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources.

Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency">resourceVersion</span>:
</div><div style="margin-left:13px;">      <span title="(string) SelfLink is a URL representing this object. Populated by the system. Read-only.">selfLink</span>:
</div><div style="margin-left:13px;">      <span title="(string) UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations.

Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids">uid</span>:
</div></details><details><summary>    <span title="(v1.PodSpec) Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status">spec</span>:
</summary><div style="margin-left:13px;">      <span title="(integer) 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.">activeDeadlineSeconds</span>:
</div><details><summary>      <span title="(v1.Affinity) If specified, the pod&#39;s scheduling constraints">affinity</span>:
</summary><details><summary>        <span title="(v1.NodeAffinity) Describes node affinity scheduling rules for the pod.">nodeAffinity</span>:
</summary><details><summary>          <span title="(array) The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.">preferredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>          - <span title="(v1.NodeSelectorTerm) A node selector term, associated with the corresponding weight.">preference</span>:
</summary><details><summary>          -   <span title="(array) A list of node selector requirements by node&#39;s labels.">matchExpressions</span>:
</summary><div style="margin-left:13px;">          -   - <span title="(string) The label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.">operator</span>:
</div><details><summary>                <span title="(array) An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(array) A list of node selector requirements by node&#39;s fields.">matchFields</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.">operator</span>:
</div><details><summary>                <span title="(array) An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details></details><div style="margin-left:13px;">            <span title="(integer) Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.">weight</span>:
</div></details><details><summary>          <span title="(v1.NodeSelector) If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.">requiredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>            <span title="(array) Required. A list of node selector terms. The terms are ORed.">nodeSelectorTerms</span>:
</summary><details><summary>            - <span title="(array) A list of node selector requirements by node&#39;s labels.">matchExpressions</span>:
</summary><div style="margin-left:13px;">            - - <span title="(string) The label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.">operator</span>:
</div><details><summary>                <span title="(array) An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(array) A list of node selector requirements by node&#39;s fields.">matchFields</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.">operator</span>:
</div><details><summary>                <span title="(array) An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details></details></details></details><details><summary>        <span title="(v1.PodAffinity) Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).">podAffinity</span>:
</summary><details><summary>          <span title="(array) The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.">preferredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>          - <span title="(v1.PodAffinityTerm) Required. A pod affinity term, associated with the corresponding weight.">podAffinityTerm</span>:
</summary><details><summary>          -   <span title="(v1.LabelSelector) A label query over a set of resources, in this case pods.">labelSelector</span>:
</summary><details><summary>          -     <span title="(array) matchExpressions is a list of label selector requirements. The requirements are ANDed.">matchExpressions</span>:
</summary><div style="margin-left:13px;">          -     - <span title="(string) key is the label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                  <span title="(string) operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.">operator</span>:
</div><details><summary>                  <span title="(array) values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                  - <span title="(string)">[string]</span>:
</div></details></details><details><summary>                <span title="(object) matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.">matchLabels</span>:
</summary><div style="margin-left:13px;">                  <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(array) namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means &#34;this pod&#39;s namespace&#34;">namespaces</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.">topologyKey</span>:
</div></details><div style="margin-left:13px;">            <span title="(integer) weight associated with matching the corresponding podAffinityTerm, in the range 1-100.">weight</span>:
</div></details><details><summary>          <span title="(array) If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.">requiredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>          - <span title="(v1.LabelSelector) A label query over a set of resources, in this case pods.">labelSelector</span>:
</summary><details><summary>          -   <span title="(array) matchExpressions is a list of label selector requirements. The requirements are ANDed.">matchExpressions</span>:
</summary><div style="margin-left:13px;">          -   - <span title="(string) key is the label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.">operator</span>:
</div><details><summary>                <span title="(array) values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(object) matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.">matchLabels</span>:
</summary><div style="margin-left:13px;">                <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(array) namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means &#34;this pod&#39;s namespace&#34;">namespaces</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.">topologyKey</span>:
</div></details></details><details><summary>        <span title="(v1.PodAntiAffinity) Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).">podAntiAffinity</span>:
</summary><details><summary>          <span title="(array) The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.">preferredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>          - <span title="(v1.PodAffinityTerm) Required. A pod affinity term, associated with the corresponding weight.">podAffinityTerm</span>:
</summary><details><summary>          -   <span title="(v1.LabelSelector) A label query over a set of resources, in this case pods.">labelSelector</span>:
</summary><details><summary>          -     <span title="(array) matchExpressions is a list of label selector requirements. The requirements are ANDed.">matchExpressions</span>:
</summary><div style="margin-left:13px;">          -     - <span title="(string) key is the label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                  <span title="(string) operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.">operator</span>:
</div><details><summary>                  <span title="(array) values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                  - <span title="(string)">[string]</span>:
</div></details></details><details><summary>                <span title="(object) matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.">matchLabels</span>:
</summary><div style="margin-left:13px;">                  <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(array) namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means &#34;this pod&#39;s namespace&#34;">namespaces</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.">topologyKey</span>:
</div></details><div style="margin-left:13px;">            <span title="(integer) weight associated with matching the corresponding podAffinityTerm, in the range 1-100.">weight</span>:
</div></details><details><summary>          <span title="(array) If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.">requiredDuringSchedulingIgnoredDuringExecution</span>:
</summary><details><summary>          - <span title="(v1.LabelSelector) A label query over a set of resources, in this case pods.">labelSelector</span>:
</summary><details><summary>          -   <span title="(array) matchExpressions is a list of label selector requirements. The requirements are ANDed.">matchExpressions</span>:
</summary><div style="margin-left:13px;">          -   - <span title="(string) key is the label key that the selector applies to.">key</span>:
</div><div style="margin-left:13px;">                <span title="(string) operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.">operator</span>:
</div><details><summary>                <span title="(array) values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.">values</span>:
</summary><div style="margin-left:13px;">                - <span title="(string)">[string]</span>:
</div></details></details><details><summary>              <span title="(object) matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.">matchLabels</span>:
</summary><div style="margin-left:13px;">                <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(array) namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means &#34;this pod&#39;s namespace&#34;">namespaces</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.">topologyKey</span>:
</div></details></details></details><div style="margin-left:13px;">      <span title="(boolean) AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.">automountServiceAccountToken</span>:
</div><details><summary>      <span title="(array) 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.">containers</span>:
</summary><details><summary>      - <span title="(array) Arguments to the entrypoint. The docker image&#39;s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell">args</span>:
</summary><div style="margin-left:13px;">      - - <span title="(string)">[string]</span>:
</div></details><details><summary>        <span title="(array) Entrypoint array. Not executed within a shell. The docker image&#39;s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell">command</span>:
</summary><div style="margin-left:13px;">        - <span title="(string)">[string]</span>:
</div></details><details><summary>        <span title="(array) List of environment variables to set in the container. Cannot be updated.">env</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Name of the environment variable. Must be a C_IDENTIFIER.">name</span>:
</div><div style="margin-left:13px;">          <span title="(string) Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to &#34;&#34;.">value</span>:
</div><details><summary>          <span title="(v1.EnvVarSource) Source for the environment variable&#39;s value. Cannot be used if value is not empty.">valueFrom</span>:
</summary><details><summary>            <span title="(v1.ConfigMapKeySelector) Selects a key of a ConfigMap.">configMapKeyRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) The key to select.">key</span>:
</div><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the ConfigMap or it&#39;s key must be defined">optional</span>:
</div></details><details><summary>            <span title="(v1.ObjectFieldSelector) Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.">fieldRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.">apiVersion</span>:
</div><div style="margin-left:13px;">              <span title="(string) Path of the field to select in the specified API version.">fieldPath</span>:
</div></details><details><summary>            <span title="(v1.ResourceFieldSelector) Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.">resourceFieldRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Container name: required for volumes, optional for env vars">containerName</span>:
</div><div style="margin-left:13px;">              <span title="(resource.Quantity) Specifies the output format of the exposed resources, defaults to &#34;1&#34;">divisor</span>:
</div><div style="margin-left:13px;">              <span title="(string) Required: resource to select">resource</span>:
</div></details><details><summary>            <span title="(v1.SecretKeySelector) Selects a key of a secret in the pod&#39;s namespace">secretKeyRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) The key of the secret to select from.  Must be a valid secret key.">key</span>:
</div><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the Secret or it&#39;s key must be defined">optional</span>:
</div></details></details></details><details><summary>        <span title="(array) List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.">envFrom</span>:
</summary><details><summary>        - <span title="(v1.ConfigMapEnvSource) The ConfigMap to select from">configMapRef</span>:
</summary><div style="margin-left:13px;">        -   <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">            <span title="(boolean) Specify whether the ConfigMap must be defined">optional</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.">prefix</span>:
</div><details><summary>          <span title="(v1.SecretEnvSource) The Secret to select from">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">            <span title="(boolean) Specify whether the Secret must be defined">optional</span>:
</div></details></details><div style="margin-left:13px;">        <span title="(string) Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.">image</span>:
</div><div style="margin-left:13px;">        <span title="(string) Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images">imagePullPolicy</span>:
</div><details><summary>        <span title="(v1.Lifecycle) Actions that the management system should take in response to container lifecycle events. Cannot be updated.">lifecycle</span>:
</summary><details><summary>          <span title="(v1.Handler) PostStart is called immediately after a container is created. If the handler fails, the container is terminated and restarted according to its restart policy. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks">postStart</span>:
</summary><details><summary>            <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>              <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>              <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">                <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">              <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><details><summary>            <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details></details><details><summary>          <span title="(v1.Handler) PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks">preStop</span>:
</summary><details><summary>            <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>              <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>              <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">                <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">              <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><details><summary>            <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details></details></details><details><summary>        <span title="(v1.Probe) Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">livenessProbe</span>:
</summary><details><summary>          <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>            <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.">failureThreshold</span>:
</div><details><summary>          <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>            <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">            - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">              <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">            <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">initialDelaySeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.">periodSeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.">successThreshold</span>:
</div><details><summary>          <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">timeoutSeconds</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.">name</span>:
</div><details><summary>        <span title="(array) List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default &#34;0.0.0.0&#34; address inside a container will be accessible from the network. Cannot be updated.">ports</span>:
</summary><div style="margin-left:13px;">        - <span title="(integer) Number of port to expose on the pod&#39;s IP address. This must be a valid port number, 0 &lt; x &lt; 65536.">containerPort</span>:
</div><div style="margin-left:13px;">          <span title="(string) What host IP to bind the external port to.">hostIP</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Number of port to expose on the host. If specified, this must be a valid port number, 0 &lt; x &lt; 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.">hostPort</span>:
</div><div style="margin-left:13px;">          <span title="(string) If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.">name</span>:
</div><div style="margin-left:13px;">          <span title="(string) Protocol for port. Must be UDP or TCP. Defaults to &#34;TCP&#34;.">protocol</span>:
</div></details><details><summary>        <span title="(v1.Probe) Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">readinessProbe</span>:
</summary><details><summary>          <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>            <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.">failureThreshold</span>:
</div><details><summary>          <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>            <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">            - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">              <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">            <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">initialDelaySeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.">periodSeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.">successThreshold</span>:
</div><details><summary>          <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">timeoutSeconds</span>:
</div></details><details><summary>        <span title="(v1.ResourceRequirements) Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources">resources</span>:
</summary><details><summary>          <span title="(object) Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/">limits</span>:
</summary><div style="margin-left:13px;">            <span title="(string)">[string]</span>:
</div></details><details><summary>          <span title="(object) Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/">requests</span>:
</summary><div style="margin-left:13px;">            <span title="(string)">[string]</span>:
</div></details></details><details><summary>        <span title="(v1.SecurityContext) Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/">securityContext</span>:
</summary><div style="margin-left:13px;">          <span title="(boolean) AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN">allowPrivilegeEscalation</span>:
</div><details><summary>          <span title="(v1.Capabilities) The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime.">capabilities</span>:
</summary><details><summary>            <span title="(array) Added capabilities">add</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details><details><summary>            <span title="(array) Removed capabilities">drop</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(boolean) Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false.">privileged</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Whether this container has a read-only root filesystem. Default is false.">readOnlyRootFilesystem</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsGroup</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsNonRoot</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsUser</span>:
</div><details><summary>          <span title="(v1.SELinuxOptions) The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">seLinuxOptions</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Level is SELinux level label that applies to the container.">level</span>:
</div><div style="margin-left:13px;">            <span title="(string) Role is a SELinux role label that applies to the container.">role</span>:
</div><div style="margin-left:13px;">            <span title="(string) Type is a SELinux type label that applies to the container.">type</span>:
</div><div style="margin-left:13px;">            <span title="(string) User is a SELinux user label that applies to the container.">user</span>:
</div></details></details><div style="margin-left:13px;">        <span title="(boolean) Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.">stdin</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false">stdinOnce</span>:
</div><div style="margin-left:13px;">        <span title="(string) Optional: Path at which the file to which the container&#39;s termination message will be written is mounted into the container&#39;s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.">terminationMessagePath</span>:
</div><div style="margin-left:13px;">        <span title="(string) Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.">terminationMessagePolicy</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) Whether this container should allocate a TTY for itself, also requires &#39;stdin&#39; to be true. Default is false.">tty</span>:
</div><details><summary>        <span title="(array) volumeDevices is the list of block devices to be used by the container. This is an alpha feature and may change in the future.">volumeDevices</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) devicePath is the path inside of the container that the device will be mapped to.">devicePath</span>:
</div><div style="margin-left:13px;">          <span title="(string) name must match the name of a persistentVolumeClaim in the pod">name</span>:
</div></details><details><summary>        <span title="(array) Pod volumes to mount into the container&#39;s filesystem. Cannot be updated.">volumeMounts</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Path within the container at which the volume should be mounted.  Must not contain &#39;:&#39;.">mountPath</span>:
</div><div style="margin-left:13px;">          <span title="(string) mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationNone is used. This field is beta in 1.10.">mountPropagation</span>:
</div><div style="margin-left:13px;">          <span title="(string) This must match the Name of a Volume.">name</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Path within the volume from which the container&#39;s volume should be mounted. Defaults to &#34;&#34; (volume&#39;s root).">subPath</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) Container&#39;s working directory. If not specified, the container runtime&#39;s default will be used, which might be configured in the container image. Cannot be updated.">workingDir</span>:
</div></details><details><summary>      <span title="(v1.PodDNSConfig) Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.">dnsConfig</span>:
</summary><details><summary>        <span title="(array) A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.">nameservers</span>:
</summary><div style="margin-left:13px;">        - <span title="(string)">[string]</span>:
</div></details><details><summary>        <span title="(array) A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.">options</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Required.">name</span>:
</div><div style="margin-left:13px;">          <span title="(string)">value</span>:
</div></details><details><summary>        <span title="(array) A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.">searches</span>:
</summary><div style="margin-left:13px;">        - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">      <span title="(string) Set DNS policy for the pod. Defaults to &#34;ClusterFirst&#34;. Valid values are &#39;ClusterFirstWithHostNet&#39;, &#39;ClusterFirst&#39;, &#39;Default&#39; or &#39;None&#39;. 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 &#39;ClusterFirstWithHostNet&#39;.">dnsPolicy</span>:
</div><details><summary>      <span title="(array) HostAliases is an optional list of hosts and IPs that will be injected into the pod&#39;s hosts file if specified. This is only valid for non-hostNetwork pods.">hostAliases</span>:
</summary><details><summary>      - <span title="(array) Hostnames for the above IP address.">hostnames</span>:
</summary><div style="margin-left:13px;">      - - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) IP address of the host file entry.">ip</span>:
</div></details><div style="margin-left:13px;">      <span title="(boolean) Use the host&#39;s ipc namespace. Optional: Default to false.">hostIPC</span>:
</div><div style="margin-left:13px;">      <span title="(boolean) Host networking requested for this pod. Use the host&#39;s network namespace. If this option is set, the ports that will be used must be specified. Default to false.">hostNetwork</span>:
</div><div style="margin-left:13px;">      <span title="(boolean) Use the host&#39;s pid namespace. Optional: Default to false.">hostPID</span>:
</div><div style="margin-left:13px;">      <span title="(string) Specifies the hostname of the Pod If not specified, the pod&#39;s hostname will be set to a system-defined value.">hostname</span>:
</div><details><summary>      <span title="(array) ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod">imagePullSecrets</span>:
</summary><div style="margin-left:13px;">      - <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><details><summary>      <span title="(array) List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, or Liveness probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/">initContainers</span>:
</summary><details><summary>      - <span title="(array) Arguments to the entrypoint. The docker image&#39;s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell">args</span>:
</summary><div style="margin-left:13px;">      - - <span title="(string)">[string]</span>:
</div></details><details><summary>        <span title="(array) Entrypoint array. Not executed within a shell. The docker image&#39;s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell">command</span>:
</summary><div style="margin-left:13px;">        - <span title="(string)">[string]</span>:
</div></details><details><summary>        <span title="(array) List of environment variables to set in the container. Cannot be updated.">env</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Name of the environment variable. Must be a C_IDENTIFIER.">name</span>:
</div><div style="margin-left:13px;">          <span title="(string) Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to &#34;&#34;.">value</span>:
</div><details><summary>          <span title="(v1.EnvVarSource) Source for the environment variable&#39;s value. Cannot be used if value is not empty.">valueFrom</span>:
</summary><details><summary>            <span title="(v1.ConfigMapKeySelector) Selects a key of a ConfigMap.">configMapKeyRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) The key to select.">key</span>:
</div><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the ConfigMap or it&#39;s key must be defined">optional</span>:
</div></details><details><summary>            <span title="(v1.ObjectFieldSelector) Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.">fieldRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.">apiVersion</span>:
</div><div style="margin-left:13px;">              <span title="(string) Path of the field to select in the specified API version.">fieldPath</span>:
</div></details><details><summary>            <span title="(v1.ResourceFieldSelector) Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.">resourceFieldRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Container name: required for volumes, optional for env vars">containerName</span>:
</div><div style="margin-left:13px;">              <span title="(resource.Quantity) Specifies the output format of the exposed resources, defaults to &#34;1&#34;">divisor</span>:
</div><div style="margin-left:13px;">              <span title="(string) Required: resource to select">resource</span>:
</div></details><details><summary>            <span title="(v1.SecretKeySelector) Selects a key of a secret in the pod&#39;s namespace">secretKeyRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) The key of the secret to select from.  Must be a valid secret key.">key</span>:
</div><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the Secret or it&#39;s key must be defined">optional</span>:
</div></details></details></details><details><summary>        <span title="(array) List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.">envFrom</span>:
</summary><details><summary>        - <span title="(v1.ConfigMapEnvSource) The ConfigMap to select from">configMapRef</span>:
</summary><div style="margin-left:13px;">        -   <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">            <span title="(boolean) Specify whether the ConfigMap must be defined">optional</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.">prefix</span>:
</div><details><summary>          <span title="(v1.SecretEnvSource) The Secret to select from">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">            <span title="(boolean) Specify whether the Secret must be defined">optional</span>:
</div></details></details><div style="margin-left:13px;">        <span title="(string) Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.">image</span>:
</div><div style="margin-left:13px;">        <span title="(string) Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images">imagePullPolicy</span>:
</div><details><summary>        <span title="(v1.Lifecycle) Actions that the management system should take in response to container lifecycle events. Cannot be updated.">lifecycle</span>:
</summary><details><summary>          <span title="(v1.Handler) PostStart is called immediately after a container is created. If the handler fails, the container is terminated and restarted according to its restart policy. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks">postStart</span>:
</summary><details><summary>            <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>              <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>              <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">                <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">              <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><details><summary>            <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details></details><details><summary>          <span title="(v1.Handler) PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks">preStop</span>:
</summary><details><summary>            <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>              <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">              - <span title="(string)">[string]</span>:
</div></details></details><details><summary>            <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>              <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">                <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">              <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><details><summary>            <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">              <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details></details></details><details><summary>        <span title="(v1.Probe) Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">livenessProbe</span>:
</summary><details><summary>          <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>            <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.">failureThreshold</span>:
</div><details><summary>          <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>            <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">            - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">              <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">            <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">initialDelaySeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.">periodSeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.">successThreshold</span>:
</div><details><summary>          <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">timeoutSeconds</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.">name</span>:
</div><details><summary>        <span title="(array) List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default &#34;0.0.0.0&#34; address inside a container will be accessible from the network. Cannot be updated.">ports</span>:
</summary><div style="margin-left:13px;">        - <span title="(integer) Number of port to expose on the pod&#39;s IP address. This must be a valid port number, 0 &lt; x &lt; 65536.">containerPort</span>:
</div><div style="margin-left:13px;">          <span title="(string) What host IP to bind the external port to.">hostIP</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Number of port to expose on the host. If specified, this must be a valid port number, 0 &lt; x &lt; 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.">hostPort</span>:
</div><div style="margin-left:13px;">          <span title="(string) If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.">name</span>:
</div><div style="margin-left:13px;">          <span title="(string) Protocol for port. Must be UDP or TCP. Defaults to &#34;TCP&#34;.">protocol</span>:
</div></details><details><summary>        <span title="(v1.Probe) Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">readinessProbe</span>:
</summary><details><summary>          <span title="(v1.ExecAction) One and only one of the following should be specified. Exec specifies the action to take.">exec</span>:
</summary><details><summary>            <span title="(array) Command is the command line to execute inside the container, the working directory for the command  is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.">command</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.">failureThreshold</span>:
</div><details><summary>          <span title="(v1.HTTPGetAction) HTTPGet specifies the http request to perform.">httpGet</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.">host</span>:
</div><details><summary>            <span title="(array) Custom headers to set in the request. HTTP allows repeated headers.">httpHeaders</span>:
</summary><div style="margin-left:13px;">            - <span title="(string) The header field name">name</span>:
</div><div style="margin-left:13px;">              <span title="(string) The header field value">value</span>:
</div></details><div style="margin-left:13px;">            <span title="(string) Path to access on the HTTP server.">path</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div><div style="margin-left:13px;">            <span title="(string) Scheme to use for connecting to the host. Defaults to HTTP.">scheme</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">initialDelaySeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.">periodSeconds</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.">successThreshold</span>:
</div><details><summary>          <span title="(v1.TCPSocketAction) TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported">tcpSocket</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Optional: Host name to connect to, defaults to the pod IP.">host</span>:
</div><div style="margin-left:13px;">            <span title="(intstr.IntOrString) Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.">port</span>:
</div></details><div style="margin-left:13px;">          <span title="(integer) Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes">timeoutSeconds</span>:
</div></details><details><summary>        <span title="(v1.ResourceRequirements) Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources">resources</span>:
</summary><details><summary>          <span title="(object) Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/">limits</span>:
</summary><div style="margin-left:13px;">            <span title="(string)">[string]</span>:
</div></details><details><summary>          <span title="(object) Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/">requests</span>:
</summary><div style="margin-left:13px;">            <span title="(string)">[string]</span>:
</div></details></details><details><summary>        <span title="(v1.SecurityContext) Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/">securityContext</span>:
</summary><div style="margin-left:13px;">          <span title="(boolean) AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN">allowPrivilegeEscalation</span>:
</div><details><summary>          <span title="(v1.Capabilities) The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime.">capabilities</span>:
</summary><details><summary>            <span title="(array) Added capabilities">add</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details><details><summary>            <span title="(array) Removed capabilities">drop</span>:
</summary><div style="margin-left:13px;">            - <span title="(string)">[string]</span>:
</div></details></details><div style="margin-left:13px;">          <span title="(boolean) Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false.">privileged</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Whether this container has a read-only root filesystem. Default is false.">readOnlyRootFilesystem</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsGroup</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsNonRoot</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsUser</span>:
</div><details><summary>          <span title="(v1.SELinuxOptions) The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in PodSecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">seLinuxOptions</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Level is SELinux level label that applies to the container.">level</span>:
</div><div style="margin-left:13px;">            <span title="(string) Role is a SELinux role label that applies to the container.">role</span>:
</div><div style="margin-left:13px;">            <span title="(string) Type is a SELinux type label that applies to the container.">type</span>:
</div><div style="margin-left:13px;">            <span title="(string) User is a SELinux user label that applies to the container.">user</span>:
</div></details></details><div style="margin-left:13px;">        <span title="(boolean) Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.">stdin</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false">stdinOnce</span>:
</div><div style="margin-left:13px;">        <span title="(string) Optional: Path at which the file to which the container&#39;s termination message will be written is mounted into the container&#39;s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.">terminationMessagePath</span>:
</div><div style="margin-left:13px;">        <span title="(string) Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.">terminationMessagePolicy</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) Whether this container should allocate a TTY for itself, also requires &#39;stdin&#39; to be true. Default is false.">tty</span>:
</div><details><summary>        <span title="(array) volumeDevices is the list of block devices to be used by the container. This is an alpha feature and may change in the future.">volumeDevices</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) devicePath is the path inside of the container that the device will be mapped to.">devicePath</span>:
</div><div style="margin-left:13px;">          <span title="(string) name must match the name of a persistentVolumeClaim in the pod">name</span>:
</div></details><details><summary>        <span title="(array) Pod volumes to mount into the container&#39;s filesystem. Cannot be updated.">volumeMounts</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Path within the container at which the volume should be mounted.  Must not contain &#39;:&#39;.">mountPath</span>:
</div><div style="margin-left:13px;">          <span title="(string) mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationNone is used. This field is beta in 1.10.">mountPropagation</span>:
</div><div style="margin-left:13px;">          <span title="(string) This must match the Name of a Volume.">name</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Path within the volume from which the container&#39;s volume should be mounted. Defaults to &#34;&#34; (volume&#39;s root).">subPath</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) Container&#39;s working directory. If not specified, the container runtime&#39;s default will be used, which might be configured in the container image. Cannot be updated.">workingDir</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.">nodeName</span>:
</div><details><summary>      <span title="(object) NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node&#39;s labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/">nodeSelector</span>:
</summary><div style="margin-left:13px;">        <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">      <span title="(integer) The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.">priority</span>:
</div><div style="margin-left:13px;">      <span title="(string) If specified, indicates the pod&#39;s priority. &#34;system-node-critical&#34; and &#34;system-cluster-critical&#34; are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.">priorityClassName</span>:
</div><details><summary>      <span title="(array) If specified, all readiness gates will be evaluated for pod readiness. A pod is ready when all its containers are ready AND all conditions specified in the readiness gates have status equal to &#34;True&#34; More info: https://github.com/kubernetes/community/blob/master/keps/sig-network/0007-pod-ready%2B%2B.md">readinessGates</span>:
</summary><div style="margin-left:13px;">      - <span title="(string) ConditionType refers to a condition in the pod&#39;s condition list with matching type.">conditionType</span>:
</div></details><div style="margin-left:13px;">      <span title="(string) Restart policy for all containers within the pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy">restartPolicy</span>:
</div><div style="margin-left:13px;">      <span title="(string) If specified, the pod will be dispatched by specified scheduler. If not specified, the pod will be dispatched by default scheduler.">schedulerName</span>:
</div><details><summary>      <span title="(v1.PodSecurityContext) SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty.  See type description for default values of each field.">securityContext</span>:
</summary><div style="margin-left:13px;">        <span title="(integer) A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod:

1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR&#39;d with rw-rw----

If unset, the Kubelet will not modify the ownership and permissions of any volume.">fsGroup</span>:
</div><div style="margin-left:13px;">        <span title="(integer) The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.">runAsGroup</span>:
</div><div style="margin-left:13px;">        <span title="(boolean) Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.">runAsNonRoot</span>:
</div><div style="margin-left:13px;">        <span title="(integer) The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.">runAsUser</span>:
</div><details><summary>        <span title="(v1.SELinuxOptions) The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container.  May also be set in SecurityContext.  If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.">seLinuxOptions</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Level is SELinux level label that applies to the container.">level</span>:
</div><div style="margin-left:13px;">          <span title="(string) Role is a SELinux role label that applies to the container.">role</span>:
</div><div style="margin-left:13px;">          <span title="(string) Type is a SELinux type label that applies to the container.">type</span>:
</div><div style="margin-left:13px;">          <span title="(string) User is a SELinux user label that applies to the container.">user</span>:
</div></details><details><summary>        <span title="(array) A list of groups applied to the first process run in each container, in addition to the container&#39;s primary GID.  If unspecified, no groups will be added to any container.">supplementalGroups</span>:
</summary><div style="margin-left:13px;">        - <span title="(integer)">[integer]</span>:
</div></details><details><summary>        <span title="(array) Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch.">sysctls</span>:
</summary><div style="margin-left:13px;">        - <span title="(string) Name of a property to set">name</span>:
</div><div style="margin-left:13px;">          <span title="(string) Value of a property to set">value</span>:
</div></details></details><div style="margin-left:13px;">      <span title="(string) DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.">serviceAccount</span>:
</div><div style="margin-left:13px;">      <span title="(string) ServiceAccountName is the name of the ServiceAccount to use to run this pod. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/">serviceAccountName</span>:
</div><div style="margin-left:13px;">      <span title="(boolean) Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false. This field is alpha-level and is honored only by servers that enable the PodShareProcessNamespace feature.">shareProcessNamespace</span>:
</div><div style="margin-left:13px;">      <span title="(string) If specified, the fully qualified Pod hostname will be &#34;&lt;hostname&gt;.&lt;subdomain&gt;.&lt;pod namespace&gt;.svc.&lt;cluster domain&gt;&#34;. If not specified, the pod will not have a domainname at all.">subdomain</span>:
</div><div style="margin-left:13px;">      <span title="(integer) Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.">terminationGracePeriodSeconds</span>:
</div><details><summary>      <span title="(array) If specified, the pod&#39;s tolerations.">tolerations</span>:
</summary><div style="margin-left:13px;">      - <span title="(string) Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.">effect</span>:
</div><div style="margin-left:13px;">        <span title="(string) Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.">key</span>:
</div><div style="margin-left:13px;">        <span title="(string) Operator represents a key&#39;s relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.">operator</span>:
</div><div style="margin-left:13px;">        <span title="(integer) TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.">tolerationSeconds</span>:
</div><div style="margin-left:13px;">        <span title="(string) Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.">value</span>:
</div></details><details><summary>      <span title="(array) List of volumes that can be mounted by containers belonging to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes">volumes</span>:
</summary><details><summary>      - <span title="(v1.AWSElasticBlockStoreVolumeSource) AWSElasticBlockStore represents an AWS Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore">awsElasticBlockStore</span>:
</summary><div style="margin-left:13px;">      -   <span title="(string) Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty).">partition</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Specify &#34;true&#34; to force and set the ReadOnly property in VolumeMounts to &#34;true&#34;. If omitted, the default is &#34;false&#34;. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore">volumeID</span>:
</div></details><details><summary>        <span title="(v1.AzureDiskVolumeSource) AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.">azureDisk</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Host Caching mode: None, Read Only, Read Write.">cachingMode</span>:
</div><div style="margin-left:13px;">          <span title="(string) The Name of the data disk in the blob storage">diskName</span>:
</div><div style="margin-left:13px;">          <span title="(string) The URI the data disk in the blob storage">diskURI</span>:
</div><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) Expected values Shared: multiple blob disks per storage account  Dedicated: single blob disk per storage account  Managed: azure managed data disk (only in managed availability set). defaults to shared">kind</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div></details><details><summary>        <span title="(v1.AzureFileVolumeSource) AzureFile represents an Azure File Service mount on the host and bind mount to the pod.">azureFile</span>:
</summary><div style="margin-left:13px;">          <span title="(boolean) Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) the name of secret that contains Azure Storage Account Name and Key">secretName</span>:
</div><div style="margin-left:13px;">          <span title="(string) Share Name">shareName</span>:
</div></details><details><summary>        <span title="(v1.CephFSVolumeSource) CephFS represents a Ceph FS mount on the host that shares a pod&#39;s lifetime">cephfs</span>:
</summary><details><summary>          <span title="(array) Required: Monitors is a collection of Ceph monitors More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it">monitors</span>:
</summary><div style="margin-left:13px;">          - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) Optional: Used as the mounted root, rather than the full Ceph tree, default is /">path</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it">secretFile</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) Optional: User is the rados user name, default is admin More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it">user</span>:
</div></details><details><summary>        <span title="(v1.CinderVolumeSource) Cinder represents a cinder volume attached and mounted on kubelets host machine More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md">cinder</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) Optional: points to a secret object containing parameters used to connect to OpenStack.">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) volume id used to identify the volume in cinder More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md">volumeID</span>:
</div></details><details><summary>        <span title="(v1.ConfigMapVolumeSource) ConfigMap represents a configMap that should populate this volume">configMap</span>:
</summary><div style="margin-left:13px;">          <span title="(integer) Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">defaultMode</span>:
</div><details><summary>          <span title="(array) If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.">items</span>:
</summary><div style="margin-left:13px;">          - <span title="(string) The key to project.">key</span>:
</div><div style="margin-left:13px;">            <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">            <span title="(string) The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.">path</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Specify whether the ConfigMap or it&#39;s keys must be defined">optional</span>:
</div></details><details><summary>        <span title="(v1.DownwardAPIVolumeSource) DownwardAPI represents downward API about the pod that should populate this volume">downwardAPI</span>:
</summary><div style="margin-left:13px;">          <span title="(integer) Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">defaultMode</span>:
</div><details><summary>          <span title="(array) Items is a list of downward API volume file">items</span>:
</summary><details><summary>          - <span title="(v1.ObjectFieldSelector) Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.">fieldRef</span>:
</summary><div style="margin-left:13px;">          -   <span title="(string) Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.">apiVersion</span>:
</div><div style="margin-left:13px;">              <span title="(string) Path of the field to select in the specified API version.">fieldPath</span>:
</div></details><div style="margin-left:13px;">            <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">            <span title="(string) Required: Path is  the relative path name of the file to be created. Must not be absolute or contain the &#39;..&#39; path. Must be utf-8 encoded. The first item of the relative path must not start with &#39;..&#39;">path</span>:
</div><details><summary>            <span title="(v1.ResourceFieldSelector) Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.">resourceFieldRef</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Container name: required for volumes, optional for env vars">containerName</span>:
</div><div style="margin-left:13px;">              <span title="(resource.Quantity) Specifies the output format of the exposed resources, defaults to &#34;1&#34;">divisor</span>:
</div><div style="margin-left:13px;">              <span title="(string) Required: resource to select">resource</span>:
</div></details></details></details><details><summary>        <span title="(v1.EmptyDirVolumeSource) EmptyDir represents a temporary directory that shares a pod&#39;s lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir">emptyDir</span>:
</summary><div style="margin-left:13px;">          <span title="(string) What type of storage medium should back this directory. The default is &#34;&#34; which means to use the node&#39;s default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir">medium</span>:
</div><div style="margin-left:13px;">          <span title="(resource.Quantity) Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir">sizeLimit</span>:
</div></details><details><summary>        <span title="(v1.FCVolumeSource) FC represents a Fibre Channel resource that is attached to a kubelet&#39;s host machine and then exposed to the pod.">fc</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(integer) Optional: FC target lun number">lun</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><details><summary>          <span title="(array) Optional: FC target worldwide names (WWNs)">targetWWNs</span>:
</summary><div style="margin-left:13px;">          - <span title="(string)">[string]</span>:
</div></details><details><summary>          <span title="(array) Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.">wwids</span>:
</summary><div style="margin-left:13px;">          - <span title="(string)">[string]</span>:
</div></details></details><details><summary>        <span title="(v1.FlexVolumeSource) FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.">flexVolume</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Driver is the name of the driver to use for this volume.">driver</span>:
</div><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default filesystem depends on FlexVolume script.">fsType</span>:
</div><details><summary>          <span title="(object) Optional: Extra command options if any.">options</span>:
</summary><div style="margin-left:13px;">            <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">          <span title="(boolean) Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details></details><details><summary>        <span title="(v1.FlockerVolumeSource) Flocker represents a Flocker volume attached to a kubelet&#39;s host machine. This depends on the Flocker control service being running">flocker</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Name of the dataset stored as metadata -&gt; name on the dataset for Flocker should be considered as deprecated">datasetName</span>:
</div><div style="margin-left:13px;">          <span title="(string) UUID of the dataset. This is unique identifier of a Flocker dataset">datasetUUID</span>:
</div></details><details><summary>        <span title="(v1.GCEPersistentDiskVolumeSource) GCEPersistentDisk represents a GCE Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk">gcePersistentDisk</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(integer) The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk">partition</span>:
</div><div style="margin-left:13px;">          <span title="(string) Unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk">pdName</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk">readOnly</span>:
</div></details><details><summary>        <span title="(v1.GitRepoVolumeSource) GitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod&#39;s container.">gitRepo</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Target directory name. Must not contain or start with &#39;..&#39;.  If &#39;.&#39; is supplied, the volume directory will be the git repository.  Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.">directory</span>:
</div><div style="margin-left:13px;">          <span title="(string) Repository URL">repository</span>:
</div><div style="margin-left:13px;">          <span title="(string) Commit hash for the specified revision.">revision</span>:
</div></details><details><summary>        <span title="(v1.GlusterfsVolumeSource) Glusterfs represents a Glusterfs mount on the host that shares a pod&#39;s lifetime. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md">glusterfs</span>:
</summary><div style="margin-left:13px;">          <span title="(string) EndpointsName is the endpoint name that details Glusterfs topology. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod">endpoints</span>:
</div><div style="margin-left:13px;">          <span title="(string) Path is the Glusterfs volume path. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod">path</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod">readOnly</span>:
</div></details><details><summary>        <span title="(v1.HostPathVolumeSource) HostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath">hostPath</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath">path</span>:
</div><div style="margin-left:13px;">          <span title="(string) Type for HostPath Volume Defaults to &#34;&#34; More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath">type</span>:
</div></details><details><summary>        <span title="(v1.ISCSIVolumeSource) ISCSI represents an ISCSI Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://releases.k8s.io/HEAD/examples/volumes/iscsi/README.md">iscsi</span>:
</summary><div style="margin-left:13px;">          <span title="(boolean) whether support iSCSI Discovery CHAP authentication">chapAuthDiscovery</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) whether support iSCSI Session CHAP authentication">chapAuthSession</span>:
</div><div style="margin-left:13px;">          <span title="(string) Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface &lt;target portal&gt;:&lt;volume name&gt; will be created for the connection.">initiatorName</span>:
</div><div style="margin-left:13px;">          <span title="(string) Target iSCSI Qualified Name.">iqn</span>:
</div><div style="margin-left:13px;">          <span title="(string) iSCSI Interface Name that uses an iSCSI transport. Defaults to &#39;default&#39; (tcp).">iscsiInterface</span>:
</div><div style="margin-left:13px;">          <span title="(integer) iSCSI Target Lun number.">lun</span>:
</div><details><summary>          <span title="(array) iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).">portals</span>:
</summary><div style="margin-left:13px;">          - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) CHAP Secret for iSCSI target and initiator authentication">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).">targetPortal</span>:
</div></details><div style="margin-left:13px;">        <span title="(string) Volume&#39;s name. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><details><summary>        <span title="(v1.NFSVolumeSource) NFS represents an NFS mount on the host that shares a pod&#39;s lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs">nfs</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs">path</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs">server</span>:
</div></details><details><summary>        <span title="(v1.PersistentVolumeClaimVolumeSource) PersistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims">persistentVolumeClaim</span>:
</summary><div style="margin-left:13px;">          <span title="(string) ClaimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims">claimName</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Will force the ReadOnly setting in VolumeMounts. Default false.">readOnly</span>:
</div></details><details><summary>        <span title="(v1.PhotonPersistentDiskVolumeSource) PhotonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine">photonPersistentDisk</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) ID that identifies Photon Controller persistent disk">pdID</span>:
</div></details><details><summary>        <span title="(v1.PortworxVolumeSource) PortworxVolume represents a portworx volume attached and mounted on kubelets host machine">portworxVolume</span>:
</summary><div style="margin-left:13px;">          <span title="(string) FSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) VolumeID uniquely identifies a Portworx volume">volumeID</span>:
</div></details><details><summary>        <span title="(v1.ProjectedVolumeSource) Items for all in one resources secrets, configmaps, and downward API">projected</span>:
</summary><div style="margin-left:13px;">          <span title="(integer) Mode bits to use on created files by default. Must be a value between 0 and 0777. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">defaultMode</span>:
</div><details><summary>          <span title="(array) list of volume projections">sources</span>:
</summary><details><summary>          - <span title="(v1.ConfigMapProjection) information about the configMap data to project">configMap</span>:
</summary><details><summary>          -   <span title="(array) If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.">items</span>:
</summary><div style="margin-left:13px;">          -   - <span title="(string) The key to project.">key</span>:
</div><div style="margin-left:13px;">                <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">                <span title="(string) The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.">path</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the ConfigMap or it&#39;s keys must be defined">optional</span>:
</div></details><details><summary>            <span title="(v1.DownwardAPIProjection) information about the downwardAPI data to project">downwardAPI</span>:
</summary><details><summary>              <span title="(array) Items is a list of DownwardAPIVolume file">items</span>:
</summary><details><summary>              - <span title="(v1.ObjectFieldSelector) Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.">fieldRef</span>:
</summary><div style="margin-left:13px;">              -   <span title="(string) Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.">apiVersion</span>:
</div><div style="margin-left:13px;">                  <span title="(string) Path of the field to select in the specified API version.">fieldPath</span>:
</div></details><div style="margin-left:13px;">                <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">                <span title="(string) Required: Path is  the relative path name of the file to be created. Must not be absolute or contain the &#39;..&#39; path. Must be utf-8 encoded. The first item of the relative path must not start with &#39;..&#39;">path</span>:
</div><details><summary>                <span title="(v1.ResourceFieldSelector) Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.">resourceFieldRef</span>:
</summary><div style="margin-left:13px;">                  <span title="(string) Container name: required for volumes, optional for env vars">containerName</span>:
</div><div style="margin-left:13px;">                  <span title="(resource.Quantity) Specifies the output format of the exposed resources, defaults to &#34;1&#34;">divisor</span>:
</div><div style="margin-left:13px;">                  <span title="(string) Required: resource to select">resource</span>:
</div></details></details></details><details><summary>            <span title="(v1.SecretProjection) information about the secret data to project">secret</span>:
</summary><details><summary>              <span title="(array) If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.">items</span>:
</summary><div style="margin-left:13px;">              - <span title="(string) The key to project.">key</span>:
</div><div style="margin-left:13px;">                <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">                <span title="(string) The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.">path</span>:
</div></details><div style="margin-left:13px;">              <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div><div style="margin-left:13px;">              <span title="(boolean) Specify whether the Secret or its key must be defined">optional</span>:
</div></details><details><summary>            <span title="(v1.ServiceAccountTokenProjection) information about the serviceAccountToken data to project">serviceAccountToken</span>:
</summary><div style="margin-left:13px;">              <span title="(string) Audience is the intended audience of the token. A recipient of a token must identify itself with an identifier specified in the audience of the token, and otherwise should reject the token. The audience defaults to the identifier of the apiserver.">audience</span>:
</div><div style="margin-left:13px;">              <span title="(integer) ExpirationSeconds is the requested duration of validity of the service account token. As the token approaches expiration, the kubelet volume plugin will proactively rotate the service account token. The kubelet will start trying to rotate the token if the token is older than 80 percent of its time to live or if the token is older than 24 hours.Defaults to 1 hour and must be at least 10 minutes.">expirationSeconds</span>:
</div><div style="margin-left:13px;">              <span title="(string) Path is the path relative to the mount point of the file to project the token into.">path</span>:
</div></details></details></details><details><summary>        <span title="(v1.QuobyteVolumeSource) Quobyte represents a Quobyte mount on the host that shares a pod&#39;s lifetime">quobyte</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Group to map volume access to Default is no group">group</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.">readOnly</span>:
</div><div style="margin-left:13px;">          <span title="(string) Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes">registry</span>:
</div><div style="margin-left:13px;">          <span title="(string) User to map volume access to Defaults to serivceaccount user">user</span>:
</div><div style="margin-left:13px;">          <span title="(string) Volume is a string that references an already created Quobyte volume by name.">volume</span>:
</div></details><details><summary>        <span title="(v1.RBDVolumeSource) RBD represents a Rados Block Device mount on the host that shares a pod&#39;s lifetime. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md">rbd</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) The rados image name. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">image</span>:
</div><div style="margin-left:13px;">          <span title="(string) Keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">keyring</span>:
</div><details><summary>          <span title="(array) A collection of Ceph monitors. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">monitors</span>:
</summary><div style="margin-left:13px;">          - <span title="(string)">[string]</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) The rados pool name. Default is rbd. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">pool</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) SecretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) The rados user name. Default is admin. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it">user</span>:
</div></details><details><summary>        <span title="(v1.ScaleIOVolumeSource) ScaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.">scaleIO</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) The host address of the ScaleIO API Gateway.">gateway</span>:
</div><div style="margin-left:13px;">          <span title="(string) The name of the ScaleIO Protection Domain for the configured storage.">protectionDomain</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) SecretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(boolean) Flag to enable/disable SSL communication with Gateway, default false">sslEnabled</span>:
</div><div style="margin-left:13px;">          <span title="(string) Indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned.">storageMode</span>:
</div><div style="margin-left:13px;">          <span title="(string) The ScaleIO Storage Pool associated with the protection domain.">storagePool</span>:
</div><div style="margin-left:13px;">          <span title="(string) The name of the storage system as configured in ScaleIO.">system</span>:
</div><div style="margin-left:13px;">          <span title="(string) The name of a volume already created in the ScaleIO system that is associated with this volume source.">volumeName</span>:
</div></details><details><summary>        <span title="(v1.SecretVolumeSource) Secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret">secret</span>:
</summary><div style="margin-left:13px;">          <span title="(integer) Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">defaultMode</span>:
</div><details><summary>          <span title="(array) If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.">items</span>:
</summary><div style="margin-left:13px;">          - <span title="(string) The key to project.">key</span>:
</div><div style="margin-left:13px;">            <span title="(integer) Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.">mode</span>:
</div><div style="margin-left:13px;">            <span title="(string) The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.">path</span>:
</div></details><div style="margin-left:13px;">          <span title="(boolean) Specify whether the Secret or it&#39;s keys must be defined">optional</span>:
</div><div style="margin-left:13px;">          <span title="(string) Name of the secret in the pod&#39;s namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret">secretName</span>:
</div></details><details><summary>        <span title="(v1.StorageOSVolumeSource) StorageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.">storageos</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(boolean) Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.">readOnly</span>:
</div><details><summary>          <span title="(v1.LocalObjectReference) SecretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.">secretRef</span>:
</summary><div style="margin-left:13px;">            <span title="(string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names">name</span>:
</div></details><div style="margin-left:13px;">          <span title="(string) VolumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.">volumeName</span>:
</div><div style="margin-left:13px;">          <span title="(string) VolumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod&#39;s namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to &#34;default&#34; if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.">volumeNamespace</span>:
</div></details><details><summary>        <span title="(v1.VsphereVirtualDiskVolumeSource) VsphereVolume represents a vSphere volume attached and mounted on kubelets host machine">vsphereVolume</span>:
</summary><div style="margin-left:13px;">          <span title="(string) Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.">fsType</span>:
</div><div style="margin-left:13px;">          <span title="(string) Storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.">storagePolicyID</span>:
</div><div style="margin-left:13px;">          <span title="(string) Storage Policy Based Management (SPBM) profile name.">storagePolicyName</span>:
</div><div style="margin-left:13px;">          <span title="(string) Path that identifies vSphere volume vmdk">volumePath</span>:
</div></details></details></details></details><details><summary>  <span title="(v1beta2.DaemonSetUpdateStrategy) An update strategy to replace existing DaemonSet pods with new pods.">updateStrategy</span>:
</summary><details><summary>    <span title="(v1beta2.RollingUpdateDaemonSet) Rolling update config params. Present only if type = &#34;RollingUpdate&#34;.">rollingUpdate</span>:
</summary><div style="margin-left:13px;">      <span title="(intstr.IntOrString) The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.">maxUnavailable</span>:
</div></details><div style="margin-left:13px;">    <span title="(string) Type of daemon set update. Can be &#34;RollingUpdate&#34; or &#34;OnDelete&#34;. Default is RollingUpdate.">type</span>:
</div></details></details><details><summary><span title="(v1beta2.DaemonSetStatus) The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status">status</span>:
</summary><div style="margin-left:13px;">  <span title="(integer) Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.">collisionCount</span>:
</div><details><summary>  <span title="(array) Represents the latest available observations of a DaemonSet&#39;s current state.">conditions</span>:
</summary><div style="margin-left:13px;">  - <span title="(v1.Time) Last time the condition transitioned from one status to another.">lastTransitionTime</span>:
</div><div style="margin-left:13px;">    <span title="(string) A human readable message indicating details about the transition.">message</span>:
</div><div style="margin-left:13px;">    <span title="(string) The reason for the condition&#39;s last transition.">reason</span>:
</div><div style="margin-left:13px;">    <span title="(string) Status of the condition, one of True, False, Unknown.">status</span>:
</div><div style="margin-left:13px;">    <span title="(string) Type of DaemonSet condition.">type</span>:
</div></details><div style="margin-left:13px;">  <span title="(integer) The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/">currentNumberScheduled</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/">desiredNumberScheduled</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)">numberAvailable</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/">numberMisscheduled</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.">numberReady</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)">numberUnavailable</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The most recent generation observed by the daemon set controller.">observedGeneration</span>:
</div><div style="margin-left:13px;">  <span title="(integer) The total number of nodes that are running updated daemon pod">updatedNumberScheduled</span>:
</div></details>
</pre>
++++

== Operations

[[Post-apis-apps-v1beta2-namespaces-namespace-daemonsets]]
=== Create a DaemonSet in a namespace
Create a DaemonSet

==== HTTP request
----
POST /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}

----

==== Curl request
----
$ curl -k \
    -X POST \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets <<'EOF'
{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1beta2.DaemonSet
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|201 Created|v1beta2.DaemonSet
|202 Accepted|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Get-apis-apps-v1beta2-namespaces-namespace-daemonsets-name]]
=== Get a DaemonSet in a namespace
Read the specified DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|exact|Should the export be exact.  Exact export maintains cluster-specific fields like 'Namespace'.
|export|Should this value be exported.  Export strips fields that a user can not specify.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Get-apis-apps-v1beta2-daemonsets]]
=== Get all DaemonSets
List or watch objects of kind DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/daemonsets
----

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|pretty|If 'true', then the output is pretty printed.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSetList
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf
* application/json;stream=watch
* application/vnd.kubernetes.protobuf;stream=watch


[[Get-apis-apps-v1beta2-namespaces-namespace-daemonsets]]
=== Get all DaemonSets in a namespace
List or watch objects of kind DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSetList
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf
* application/json;stream=watch
* application/vnd.kubernetes.protobuf;stream=watch


[[Get-apis-apps-v1beta2-watch-namespaces-namespace-daemonsets-name]]
=== Watch a DaemonSet in a namespace
Watch changes to an object of kind DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/watch/namespaces/$NAMESPACE/daemonsets/$NAME HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/watch/namespaces/$NAMESPACE/daemonsets/$NAME
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|pretty|If 'true', then the output is pretty printed.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1.WatchEvent
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf
* application/json;stream=watch
* application/vnd.kubernetes.protobuf;stream=watch


[[Get-apis-apps-v1beta2-watch-daemonsets]]
=== Watch all DaemonSets
Watch individual changes to a list of DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/watch/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/watch/daemonsets
----

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|pretty|If 'true', then the output is pretty printed.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1.WatchEvent
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf
* application/json;stream=watch
* application/vnd.kubernetes.protobuf;stream=watch


[[Get-apis-apps-v1beta2-watch-namespaces-namespace-daemonsets]]
=== Watch all DaemonSets in a namespace
Watch individual changes to a list of DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/watch/namespaces/$NAMESPACE/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/watch/namespaces/$NAMESPACE/daemonsets
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|pretty|If 'true', then the output is pretty printed.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1.WatchEvent
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf
* application/json;stream=watch
* application/vnd.kubernetes.protobuf;stream=watch


[[Put-apis-apps-v1beta2-namespaces-namespace-daemonsets-name]]
=== Update a DaemonSet in a namespace
Replace the specified DaemonSet

==== HTTP request
----
PUT /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}

----

==== Curl request
----
$ curl -k \
    -X PUT \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME <<'EOF'
{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1beta2.DaemonSet
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|201 Created|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Patch-apis-apps-v1beta2-namespaces-namespace-daemonsets-name]]
=== Patch a DaemonSet in a namespace
Partially update the specified DaemonSet

==== HTTP request
----
PATCH /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json-patch+json'

{
  ...
}

----

==== Curl request
----
$ curl -k \
    -X PATCH \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json-patch+json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME <<'EOF'
{
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1.Patch
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* application/json-patch+json
* application/merge-patch+json
* application/strategic-merge-patch+json

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Delete-apis-apps-v1beta2-namespaces-namespace-daemonsets-name]]
=== Delete a DaemonSet in a namespace
Delete a DaemonSet

==== HTTP request
----
DELETE /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  ...
}

----

==== Curl request
----
$ curl -k \
    -X DELETE \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME <<'EOF'
{
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1.DeleteOptions
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|gracePeriodSeconds|The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
|orphanDependents|Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
|propagationPolicy|Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1.Status
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Delete-apis-apps-v1beta2-namespaces-namespace-daemonsets]]
=== Delete all DaemonSets in a namespace
Delete collection of DaemonSet

==== HTTP request
----
DELETE /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -X DELETE \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|continue|The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
|fieldSelector|A selector to restrict the list of returned objects by their fields. Defaults to everything.
|includeUninitialized|If true, partially initialized resources are included in the response.
|labelSelector|A selector to restrict the list of returned objects by their labels. Defaults to everything.
|limit|limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
|resourceVersion|When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
|timeoutSeconds|Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
|watch|Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1.Status
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Get-apis-apps-v1beta2-namespaces-namespace-daemonsets-name-status]]
=== Get status of a DaemonSet in a namespace
Read status of the specified DaemonSet

==== HTTP request
----
GET /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
----

==== Curl request
----
$ curl -k \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status
----

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Put-apis-apps-v1beta2-namespaces-namespace-daemonsets-name-status]]
=== Update status of a DaemonSet in a namespace
Replace status of the specified DaemonSet

==== HTTP request
----
PUT /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}

----

==== Curl request
----
$ curl -k \
    -X PUT \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status <<'EOF'
{
  "kind": "DaemonSet",
  "apiVersion": "apps/v1beta2",
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1beta2.DaemonSet
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|201 Created|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* \*/*

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf


[[Patch-apis-apps-v1beta2-namespaces-namespace-daemonsets-name-status]]
=== Patch status of a DaemonSet in a namespace
Partially update status of the specified DaemonSet

==== HTTP request
----
PATCH /apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json-patch+json'

{
  ...
}

----

==== Curl request
----
$ curl -k \
    -X PATCH \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json-patch+json' \
    https://$ENDPOINT/apis/apps/v1beta2/namespaces/$NAMESPACE/daemonsets/$NAME/status <<'EOF'
{
  ...
}
EOF
----

==== HTTP body
[cols="1,5", options="header"]
|===
|Parameter|Schema
|body|v1.Patch
|===

==== Path parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|name|name of the DaemonSet
|namespace|object name and auth scope, such as for teams and projects
|===

==== Query parameters
[cols="1,5", options="header"]
|===
|Parameter|Description
|pretty|If 'true', then the output is pretty printed.
|===

==== Responses
[cols="1,5", options="header"]
|===
|HTTP Code|Schema
|200 OK|v1beta2.DaemonSet
|401 Unauthorized|
|===

==== Consumes

* application/json-patch+json
* application/merge-patch+json
* application/strategic-merge-patch+json

==== Produces

* application/json
* application/yaml
* application/vnd.kubernetes.protobuf



