CacheCluster is the Schema for the CacheClusters API
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
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: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations
Each additional property must conform to the following schema
Type: stringCreationTimestamp 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
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.
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
A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.
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: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels
Each additional property must conform to the following schema
Type: stringManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like "ci-cd". The set of fields is always in the version that the workflow used when modifying the object.
No Additional ItemsManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.
APIVersion defines the version of this resource that this field set applies to. The format is "group/version" just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.
FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: "FieldsV1"
FieldsV1 holds the first JSON version format as described in the "FieldsV1" type.
Manager is an identifier of the workflow managing these fields.
Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are 'Apply' and 'Update'.
Subresource is the name of the subresource used to update that object, or empty string if the object was updated through the main resource. The value of this field is used to distinguish between managers, even if they share the same name. For example, a status update will be distinct from a regular update using the same manager name. Note that the APIVersion field is not related to the Subresource field and it always corresponds to the version of the main resource.
Time is the timestamp of when the ManagedFields entry was added. The timestamp will also be updated if a field is added, the manager changes any of the owned fields value or removes a field. The timestamp does not update when a field is removed from the entry because another manager took it over.
Same definition as creationTimestampName 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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
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
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.
No Additional ItemsOwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.
API version of the referent.
If true, AND if the owner has the "foregroundDeletion" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion for how the garbage collector interacts with this field and enforces the foreground deletion. Defaults to false. To set this field, a user needs "delete" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.
If true, this reference points to the managing controller.
Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
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
Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.
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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
CacheClusterSpec defines the desired state of CacheCluster.
Contains all of the attributes of a specific cluster.
Reserved parameter. The password used to access a password protected server.
Password constraints:
Must be only printable ASCII characters.
Must be at least 16 characters and no more than 128 characters in length.
Key is the key within the secret
name is unique within a namespace to reference a secret resource.
namespace defines the space within which the secret name must be unique.
If you are running Valkey 7.2 and above or Redis OSS engine version 6.0 and
above, set this parameter to yes to opt-in to the next auto minor version
upgrade campaign. This parameter is disabled for previous versions.
Specifies whether the nodes in this Memcached cluster are created in a single
Availability Zone or created across multiple Availability Zones in the cluster's
region.
This parameter is only supported for Memcached clusters.
If the AZMode and PreferredAvailabilityZones are not specified, ElastiCache
assumes single-az mode.
The compute and memory capacity of the nodes in the node group (shard).
The following node types are supported by ElastiCache. Generally speaking,
the current generation types provide more memory and computational power
at lower cost when compared to their equivalent previous generation counterparts.
General purpose: Current generation: M7g node types: cache.m7g.large,
cache.m7g.xlarge, cache.m7g.2xlarge, cache.m7g.4xlarge, cache.m7g.8xlarge,
cache.m7g.12xlarge, cache.m7g.16xlarge For region availability, see Supported
Node Types (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html#CacheNodes.SupportedTypesByRegion)
M6g node types (available only for Redis OSS engine version 5.0.6 onward
and for Memcached engine version 1.5.16 onward): cache.m6g.large, cache.m6g.xlarge,
cache.m6g.2xlarge, cache.m6g.4xlarge, cache.m6g.8xlarge, cache.m6g.12xlarge,
cache.m6g.16xlarge M5 node types: cache.m5.large, cache.m5.xlarge, cache.m5.2xlarge,
cache.m5.4xlarge, cache.m5.12xlarge, cache.m5.24xlarge M4 node types:
cache.m4.large, cache.m4.xlarge, cache.m4.2xlarge, cache.m4.4xlarge, cache.m4.10xlarge
T4g node types (available only for Redis OSS engine version 5.0.6 onward
and Memcached engine version 1.5.16 onward): cache.t4g.micro, cache.t4g.small,
cache.t4g.medium T3 node types: cache.t3.micro, cache.t3.small, cache.t3.medium
T2 node types: cache.t2.micro, cache.t2.small, cache.t2.medium Previous
generation: (not recommended. Existing clusters are still supported but
creation of new clusters is not supported for these types.) T1 node types:
cache.t1.micro M1 node types: cache.m1.small, cache.m1.medium, cache.m1.large,
cache.m1.xlarge M3 node types: cache.m3.medium, cache.m3.large, cache.m3.xlarge,
cache.m3.2xlarge
Compute optimized: Previous generation: (not recommended. Existing clusters
are still supported but creation of new clusters is not supported for
these types.) C1 node types: cache.c1.xlarge
Memory optimized: Current generation: R7g node types: cache.r7g.large,
cache.r7g.xlarge, cache.r7g.2xlarge, cache.r7g.4xlarge, cache.r7g.8xlarge,
cache.r7g.12xlarge, cache.r7g.16xlarge For region availability, see Supported
Node Types (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html#CacheNodes.SupportedTypesByRegion)
R6g node types (available only for Redis OSS engine version 5.0.6 onward
and for Memcached engine version 1.5.16 onward): cache.r6g.large, cache.r6g.xlarge,
cache.r6g.2xlarge, cache.r6g.4xlarge, cache.r6g.8xlarge, cache.r6g.12xlarge,
cache.r6g.16xlarge R5 node types: cache.r5.large, cache.r5.xlarge, cache.r5.2xlarge,
cache.r5.4xlarge, cache.r5.12xlarge, cache.r5.24xlarge R4 node types:
cache.r4.large, cache.r4.xlarge, cache.r4.2xlarge, cache.r4.4xlarge, cache.r4.8xlarge,
cache.r4.16xlarge Previous generation: (not recommended. Existing clusters
are still supported but creation of new clusters is not supported for
these types.) M2 node types: cache.m2.xlarge, cache.m2.2xlarge, cache.m2.4xlarge
R3 node types: cache.r3.large, cache.r3.xlarge, cache.r3.2xlarge, cache.r3.4xlarge,
cache.r3.8xlarge
Additional node type info
All current generation instance types are created in Amazon VPC by default.
Valkey or Redis OSS append-only files (AOF) are not supported for T1
or T2 instances.
Valkey or Redis OSS Multi-AZ with automatic failover is not supported
on T1 instances.
The configuration variables appendonly and appendfsync are not supported
on Valkey, or on Redis OSS version 2.8.22 and later.
The name of the parameter group to associate with this cluster. If this argument
is omitted, the default parameter group for the specified engine is used.
You cannot use any parameter group which has cluster-enabled='yes' when creating
a cluster.
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
A list of security group names to associate with this cluster.
Use this parameter only when you are creating a cluster outside of an Amazon
Virtual Private Cloud (Amazon VPC).
The name of the subnet group to be used for the cluster.
Use this parameter only when you are creating a cluster in an Amazon Virtual
Private Cloud (Amazon VPC).
If you're going to launch your cluster in an Amazon VPC, you need to create
a subnet group before you start creating a cluster. For more information,
see Subnets and Subnet Groups (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/SubnetGroups.html).
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
The name of the cache engine to be used for this cluster.
Valid values for this parameter are: memcached | redis
The version number of the cache engine to be used for this cluster. To view
the supported cache engine versions, use the DescribeCacheEngineVersions
operation.
Important: You can upgrade to a newer engine version (see Selecting a Cache
Engine and Version (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/SelectEngine.html#VersionManagement)),
but you cannot downgrade to an earlier engine version. If you want to use
an earlier engine version, you must delete the existing cluster or replication
group and create it anew with the earlier engine version.
The network type you choose when modifying a cluster, either ipv4 | ipv6.
IPv6 is supported for workloads using Valkey 7.2 and above, Redis OSS engine
version 6.2 to 7.1 and Memcached engine version 1.6.6 and above on all instances
built on the Nitro system (http://aws.amazon.com/ec2/nitro/).
Specifies the destination, format and type of the logs.
No Additional ItemsSpecifies the destination, format and type of the logs.
Configuration details of either a CloudWatch Logs destination or Kinesis
Data Firehose destination.
The configuration details of the CloudWatch Logs destination.
The configuration details of the Kinesis Data Firehose destination.
Must be either ipv4 | ipv6 | dual_stack. IPv6 is supported for workloads
using Valkey 7.2 and above, Redis OSS engine version 6.2 to 7.1 and Memcached
engine version 1.6.6 and above on all instances built on the Nitro system
(http://aws.amazon.com/ec2/nitro/).
The Amazon Resource Name (ARN) of the Amazon Simple Notification Service
(SNS) topic to which notifications are sent.
The Amazon SNS topic owner must be the same as the cluster owner.
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
The initial number of cache nodes that the cluster has.
For clusters running Valkey or Redis OSS, this value must be 1. For clusters
running Memcached, this value must be between 1 and 40.
If you need more than 40 nodes for your Memcached cluster, please fill out
the ElastiCache Limit Increase Request form at http://aws.amazon.com/contact-us/elasticache-node-limit-request/
(http://aws.amazon.com/contact-us/elasticache-node-limit-request/).
Specifies whether the nodes in the cluster are created in a single outpost
or across multiple outposts.
The port number on which each of the cache nodes accepts connections.
A list of the Availability Zones in which cache nodes are created. The order
of the zones in the list is not important.
This option is only supported on Memcached.
If you are creating your cluster in an Amazon VPC (recommended) you can only
locate nodes in Availability Zones that are associated with the subnets in
the selected subnet group.
The number of Availability Zones listed must equal the value of NumCacheNodes.
If you want all the nodes in the same Availability Zone, use PreferredAvailabilityZone
instead, or repeat the Availability Zone multiple times in the list.
Default: System chosen Availability Zones.
Specifies the weekly time range during which maintenance on the cluster is
performed. It is specified as a range in the format ddd:hh24:mi-ddd:hh24:mi
(24H Clock UTC). The minimum maintenance window is a 60 minute period.
The outpost ARN in which the cache cluster is created.
The outpost ARNs in which the cache cluster is created.
No Additional ItemsThe ID of the replication group to which this cluster should belong. If this
parameter is specified, the cluster is added to the specified replication
group as a read replica; otherwise, the cluster is a standalone primary that
is not part of any replication group.
If the specified replication group is Multi-AZ enabled and the Availability
Zone is not specified, the cluster is created in Availability Zones that
provide the best spread of read replicas across Availability Zones.
This parameter is only valid if the Engine parameter is redis.
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
One or more VPC security groups associated with the cluster.
Use this parameter only when you are creating a cluster in an Amazon Virtual
Private Cloud (Amazon VPC).
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
A single-element string list containing an Amazon Resource Name (ARN) that
uniquely identifies a Valkey or Redis OSS RDB snapshot file stored in Amazon
S3. The snapshot file is used to populate the node group (shard). The Amazon
S3 object name in the ARN cannot contain any commas.
This parameter is only valid if the Engine parameter is redis.
Example of an Amazon S3 ARN: arn:aws:s3:::my_bucket/snapshot1.rdb
AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference
type to provide more user friendly syntax for references using 'from' field
Ex:
APIIDRef:
from:
name: my-api
AWSResourceReference provides all the values necessary to reference another
k8s resource for finding the identifier(Id/ARN/Name)
The number of days for which ElastiCache retains automatic snapshots before
deleting them. For example, if you set SnapshotRetentionLimit to 5, a snapshot
taken today is retained for 5 days before being deleted.
This parameter is only valid if the Engine parameter is redis.
Default: 0 (i.e., automatic backups are disabled for this cache cluster).
The daily time range (in UTC) during which ElastiCache begins taking a daily
snapshot of your node group (shard).
Example: 05:00-09:00
If you do not specify this parameter, ElastiCache automatically chooses an
appropriate time range.
This parameter is only valid if the Engine parameter is redis.
A flag that enables in-transit encryption when set to true.
CacheClusterStatus defines the observed state of CacheCluster
All CRs managed by ACK have a common Status.ACKResourceMetadata member
that is used to contain resource sync state, account ownership,
constructed ARN for the resource
ARN is the Amazon Resource Name for the resource. This is a
globally-unique identifier and is set only by the ACK service controller
once the controller has orchestrated the creation of the resource OR
when it has verified that an "adopted" resource (a resource where the
ARN annotation was set by the Kubernetes user on the CR) exists and
matches the supplied CR's Spec field values.
https://github.com/aws/aws-controllers-k8s/issues/270
OwnerAccountID is the AWS Account ID of the account that owns the
backend AWS service API resource.
Partition is the AWS partition in which the resource exists or will exist
Region is the AWS region in which the resource exists or will exist.
A flag that enables encryption at-rest when set to true.
You cannot modify the value of AtRestEncryptionEnabled after the cluster
is created. To enable at-rest encryption on a cluster you must set AtRestEncryptionEnabled
to true when you create a cluster.
Required: Only available when creating a replication group in an Amazon VPC
using Redis OSS version 3.2.6, 4.x or later.
Default: false
A flag that enables using an AuthToken (password) when issuing Valkey or
Redis OSS commands.
Default: false
The date the auth token was last modified
The date and time when the cluster was created.
The current state of this cluster, one of the following values: available,
creating, deleted, deleting, incompatible-network, modifying, rebooting cluster
nodes, restore-failed, or snapshotting.
A list of cache nodes that are members of the cluster.
No Additional ItemsRepresents an individual cache node within a cluster. Each cache node runs
its own instance of the cluster's protocol-compliant caching software - either
Memcached, Valkey or Redis OSS.
The following node types are supported by ElastiCache. Generally speaking,
the current generation types provide more memory and computational power
at lower cost when compared to their equivalent previous generation counterparts.
General purpose: Current generation: M7g node types: cache.m7g.large,
cache.m7g.xlarge, cache.m7g.2xlarge, cache.m7g.4xlarge, cache.m7g.8xlarge,
cache.m7g.12xlarge, cache.m7g.16xlarge For region availability, see Supported
Node Types (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html#CacheNodes.SupportedTypesByRegion)
M6g node types (available only for Redis OSS engine version 5.0.6 onward
and for Memcached engine version 1.5.16 onward): cache.m6g.large, cache.m6g.xlarge,
cache.m6g.2xlarge, cache.m6g.4xlarge, cache.m6g.8xlarge, cache.m6g.12xlarge,
cache.m6g.16xlarge M5 node types: cache.m5.large, cache.m5.xlarge, cache.m5.2xlarge,
cache.m5.4xlarge, cache.m5.12xlarge, cache.m5.24xlarge M4 node types:
cache.m4.large, cache.m4.xlarge, cache.m4.2xlarge, cache.m4.4xlarge, cache.m4.10xlarge
T4g node types (available only for Redis OSS engine version 5.0.6 onward
and Memcached engine version 1.5.16 onward): cache.t4g.micro, cache.t4g.small,
cache.t4g.medium T3 node types: cache.t3.micro, cache.t3.small, cache.t3.medium
T2 node types: cache.t2.micro, cache.t2.small, cache.t2.medium Previous
generation: (not recommended. Existing clusters are still supported but
creation of new clusters is not supported for these types.) T1 node types:
cache.t1.micro M1 node types: cache.m1.small, cache.m1.medium, cache.m1.large,
cache.m1.xlarge M3 node types: cache.m3.medium, cache.m3.large, cache.m3.xlarge,
cache.m3.2xlarge
Compute optimized: Previous generation: (not recommended. Existing clusters
are still supported but creation of new clusters is not supported for
these types.) C1 node types: cache.c1.xlarge
Memory optimized: Current generation: R7g node types: cache.r7g.large,
cache.r7g.xlarge, cache.r7g.2xlarge, cache.r7g.4xlarge, cache.r7g.8xlarge,
cache.r7g.12xlarge, cache.r7g.16xlarge For region availability, see Supported
Node Types (https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html#CacheNodes.SupportedTypesByRegion)
R6g node types (available only for Redis OSS engine version 5.0.6 onward
and for Memcached engine version 1.5.16 onward): cache.r6g.large, cache.r6g.xlarge,
cache.r6g.2xlarge, cache.r6g.4xlarge, cache.r6g.8xlarge, cache.r6g.12xlarge,
cache.r6g.16xlarge R5 node types: cache.r5.large, cache.r5.xlarge, cache.r5.2xlarge,
cache.r5.4xlarge, cache.r5.12xlarge, cache.r5.24xlarge R4 node types:
cache.r4.large, cache.r4.xlarge, cache.r4.2xlarge, cache.r4.4xlarge, cache.r4.8xlarge,
cache.r4.16xlarge Previous generation: (not recommended. Existing clusters
are still supported but creation of new clusters is not supported for
these types.) M2 node types: cache.m2.xlarge, cache.m2.2xlarge, cache.m2.4xlarge
R3 node types: cache.r3.large, cache.r3.xlarge, cache.r3.2xlarge, cache.r3.4xlarge,
cache.r3.8xlarge
Additional node type info
All current generation instance types are created in Amazon VPC by default.
Valkey or Redis OSS append-only files (AOF) are not supported for T1
or T2 instances.
Valkey or Redis OSS Multi-AZ with automatic failover is not supported
on T1 instances.
The configuration variables appendonly and appendfsync are not supported
on Valkey, or on Redis OSS version 2.8.22 and later.
Represents the information required for client programs to connect to a cache
node. This value is read-only.
Status of the cache parameter group.
A list of cache security group elements, composed of name and status sub-elements.
No Additional ItemsRepresents a cluster's status within a particular cache security group.
The URL of the web page where you can download the latest ElastiCache client
library.
All CRs managed by ACK have a common Status.Conditions member that
contains a collection of ackv1alpha1.Condition objects that describe
the various terminal states of the CR and its backend AWS service API
resource
Condition is the common struct used by all CRDs managed by ACK service
controllers to indicate terminal states of the CR and its backend AWS
service API resource
Last time the condition transitioned from one status to another.
A human readable message indicating details about the transition.
The reason for the condition's last transition.
Status of the condition, one of True, False, Unknown.
Type is the type of the Condition
Describes a notification topic and its status. Notification topics are used
for publishing ElastiCache events to subscribers using Amazon Simple Notification
Service (SNS).
A group of settings that are applied to the cluster in the future, or that
are currently being applied.
A boolean value indicating whether log delivery is enabled for the replication
group.
A list of VPC Security Groups associated with the cluster.
No Additional ItemsRepresents a single cache security group and its status.
A setting that allows you to migrate your clients to use in-transit encryption,
with no downtime.