ServerlessCache is the Schema for the ServerlessCaches API. Provides an ElastiCache Serverless Cache resource.
Type
CRD
Group
elasticache.aws.upbound.io
Version
v1beta1
apiVersion: elasticache.aws.upbound.io/v1beta1
kind: ServerlessCache
ServerlessCacheSpec defines the desired state of ServerlessCache
No description provided.
Sets the cache usage limits for storage and ElastiCache Processing Units for the cache. See configuration below.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
References to SecurityGroup in ec2 to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroupIds.
Policies for selection.
A list of the one or more VPC security groups to be associated with the serverless cache. The security group will authorize traffic access for the VPC end-point (private-link). If no other information is given this will be the VPC’s Default Security Group that is associated with the cluster VPC end-point.
The list of ARN(s) of the snapshot that the new serverless cache will be created from. Available for Redis only.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
– A list of the identifiers of the subnets where the VPC endpoint for the serverless cache will be deployed. All the subnetIds must belong to the same VPC.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Sets the cache usage limits for storage and ElastiCache Processing Units for the cache. See configuration below.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
References to SecurityGroup in ec2 to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroupIds.
Policies for selection.
A list of the one or more VPC security groups to be associated with the serverless cache. The security group will authorize traffic access for the VPC end-point (private-link). If no other information is given this will be the VPC’s Default Security Group that is associated with the cluster VPC end-point.
The list of ARN(s) of the snapshot that the new serverless cache will be created from. Available for Redis only.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
– A list of the identifiers of the subnets where the VPC endpoint for the serverless cache will be deployed. All the subnetIds must belong to the same VPC.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
ServerlessCacheStatus defines the observed state of ServerlessCache.
No description provided.
Sets the cache usage limits for storage and ElastiCache Processing Units for the cache. See configuration below.
A list of the one or more VPC security groups to be associated with the serverless cache. The security group will authorize traffic access for the VPC end-point (private-link). If no other information is given this will be the VPC’s Default Security Group that is associated with the cluster VPC end-point.
The list of ARN(s) of the snapshot that the new serverless cache will be created from. Available for Redis only.
– A list of the identifiers of the subnets where the VPC endpoint for the serverless cache will be deployed. All the subnetIds must belong to the same VPC.
Conditions of the resource.
example-${Rand.RFC1123Subdomain}
apiVersion: elasticache.aws.upbound.io/v1beta1
kind: ServerlessCache
metadata:
annotations:
meta.upbound.io/example-id: elasticache/v1beta1/serverlesscache
labels:
testing.upbound.io/example-name: example
name: example-${Rand.RFC1123Subdomain}
spec:
forProvider:
cacheUsageLimits:
- dataStorage:
- maximum: 10
unit: GB
ecpuPerSecond:
- maximum: 5000
description: Test Server
engine: memcached
majorEngineVersion: "1.6"
region: us-west-1
securityGroupIdSelector:
matchLabels:
testing.upbound.io/example-name: example
subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: example
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.