CapacityReservation (ec2.services.k8s.aws/v1alpha1)

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/sig-architecture/api-conventions.md#metadata

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/sig-architecture/api-conventions.md#metadata

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 may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.

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 return a 409.

Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency

Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" 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: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces

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/sig-architecture/api-conventions.md#concurrency-control-and-consistency

Required for future-dated Capacity Reservations only. To create a Capacity
Reservation for immediate use, omit this parameter.

Specify a commitment duration, in seconds, for the future-dated Capacity
Reservation.

The commitment duration is a minimum duration for which you commit to having
the future-dated Capacity Reservation in the active state in your account
after it has been delivered.

For more information, see Commitment duration (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cr-concepts.html#cr-commitment-duration).

Required for future-dated Capacity Reservations only. To create a Capacity
Reservation for immediate use, omit this parameter.

Indicates that the requested capacity will be delivered in addition to any
running instances or reserved capacity that you have in your account at the
requested date and time.

The only supported value is incremental.

Indicates whether the Capacity Reservation supports EBS-optimized instances.
This optimization provides dedicated throughput to Amazon EBS and an optimized
configuration stack to provide optimal I/O performance. This optimization
isn't available with all instance types. Additional usage charges apply when
using an EBS- optimized instance.

The date and time at which the Capacity Reservation expires. When a Capacity
Reservation expires, the reserved capacity is released and you can no longer
launch instances into it. The Capacity Reservation's state changes to expired
when it reaches its end date and time.

You must provide an EndDate value if EndDateType is limited. Omit EndDate
if EndDateType is unlimited.

If the EndDateType is limited, the Capacity Reservation is cancelled within
an hour from the specified time. For example, if you specify 5/31/2019, 13:30:55,
the Capacity Reservation is guaranteed to end between 13:30:55 and 14:30:55
on 5/31/2019.

If you are requesting a future-dated Capacity Reservation, you can't specify
an end date and time that is within the commitment duration.

Indicates the way in which the Capacity Reservation ends. A Capacity Reservation
can have one of the following end types:

• unlimited - The Capacity Reservation remains active until you explicitly
  cancel it. Do not provide an EndDate if the EndDateType is unlimited.

• limited - The Capacity Reservation expires automatically at a specified
  date and time. You must provide an EndDate value if the EndDateType value
  is limited.

The number of instances for which to reserve capacity.

You can request future-dated Capacity Reservations for an instance count
with a minimum of 32 vCPUs. For example, if you request a future-dated Capacity
Reservation for m5.xlarge instances, you must request at least 8 instances
(8 * m5.xlarge = 32 vCPUs).

Valid range: 1 - 1000

Indicates the type of instance launches that the Capacity Reservation accepts.
The options include:

• open - The Capacity Reservation automatically matches all instances
  that have matching attributes (instance type, platform, and Availability
  Zone). Instances that have matching attributes run in the Capacity Reservation
  automatically without specifying any additional parameters.

• targeted - The Capacity Reservation only accepts instances that have
  matching attributes (instance type, platform, and Availability Zone),
  and explicitly target the Capacity Reservation. This ensures that only
  permitted instances can use the reserved capacity.

If you are requesting a future-dated Capacity Reservation, you must specify
targeted.

Default: open

The instance type for which to reserve capacity.

You can request future-dated Capacity Reservations for instance types in
the C, M, R, I, T, and G instance families only.

For more information, see Instance types (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html)
in the Amazon EC2 User Guide.

Not supported for future-dated Capacity Reservations.

The Amazon Resource Name (ARN) of the Outpost on which to create the Capacity
Reservation.

Regex Pattern: ^arn:aws([a-z-]+)?:outposts:[a-z\d-]+:\d{12}:outpost/op-[a-f0-9]{17}$

Not supported for future-dated Capacity Reservations.

The Amazon Resource Name (ARN) of the cluster placement group in which to
create the Capacity Reservation. For more information, see Capacity Reservations
for cluster placement groups (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cr-cpg.html)
in the Amazon EC2 User Guide.

Regex Pattern: ^arn:aws([a-z-]+)?:ec2:[a-z\d-]+:\d{12}:placement-group/^.{1,255}$

Required for future-dated Capacity Reservations only. To create a Capacity
Reservation for immediate use, omit this parameter.

The date and time at which the future-dated Capacity Reservation should become
available for use, in the ISO8601 format in the UTC time zone (YYYY-MM-DDThh:mm:ss.sssZ).

You can request a future-dated Capacity Reservation between 5 and 120 days
in advance.

Indicates the tenancy of the Capacity Reservation. A Capacity Reservation
can have one of the following tenancy settings:

• default - The Capacity Reservation is created on hardware that is shared
  with other Amazon Web Services accounts.

• dedicated - The Capacity Reservation is created on single-tenant hardware
  that is dedicated to a single Amazon Web Services account.

The current state of the Capacity Reservation. A Capacity Reservation can
be in one of the following states:

• active - The capacity is available for use.

• expired - The Capacity Reservation expired automatically at the date
  and time specified in your reservation request. The reserved capacity
  is no longer available for your use.

• cancelled - The Capacity Reservation was canceled. The reserved capacity
  is no longer available for your use.

• pending - The Capacity Reservation request was successful but the capacity
  provisioning is still pending.

• failed - The Capacity Reservation request has failed. A request can
  fail due to request parameters that are not valid, capacity constraints,
  or instance limit constraints. You can view a failed request for 60 minutes.

• scheduled - (Future-dated Capacity Reservations) The future-dated Capacity
  Reservation request was approved and the Capacity Reservation is scheduled
  for delivery on the requested start date.

• payment-pending - (Capacity Blocks) The upfront payment has not been
  processed yet.

• payment-failed - (Capacity Blocks) The upfront payment was not processed
  in the 12-hour time frame. Your Capacity Block was released.

• assessing - (Future-dated Capacity Reservations) Amazon EC2 is assessing
  your request for a future-dated Capacity Reservation.

• delayed - (Future-dated Capacity Reservations) Amazon EC2 encountered
  a delay in provisioning the requested future-dated Capacity Reservation.
  Amazon EC2 is unable to deliver the requested capacity by the requested
  start date and time.

• unsupported - (Future-dated Capacity Reservations) Amazon EC2 can't
  support the future-dated Capacity Reservation request due to capacity
  constraints. You can view unsupported requests for 30 days. The Capacity
  Reservation will not be delivered.