Managed Resources

By default, the Carts component in the sample application uses a DynamoDB local instance running as a pod in the EKS cluster called carts-dynamodb. In this section of the lab, we'll provision an Amazon DynamoDB cloud-based table for our application using Crossplane managed resources and configure the Carts deployment to use the newly provisioned DynamoDB table instead of the local copy.

Let's explore how we'll create the DynamoDB table via a Crossplane managed resource manifest:

~/environment/eks-workshop/modules/automation/controlplanes/crossplane/managed/table.yaml

apiVersion: dynamodb.aws.upbound.io/v1beta1
kind: Table
metadata:
  name: "${EKS_CLUSTER_NAME}-carts-crossplane"
  labels:
    testing.upbound.io/example-name: dynamodb
  annotations:
    crossplane.io/external-name: "${EKS_CLUSTER_NAME}-carts-crossplane"
spec:
  forProvider:
    attribute:
      - name: id
        type: S
      - name: customerId
        type: S
    hashKey: id
    billingMode: PAY_PER_REQUEST
    globalSecondaryIndex:
      - hashKey: customerId
        name: idx_global_customerId
        projectionType: ALL
    region: ""
    tags:
      namespace: carts
  providerConfigRef:
    name: aws-provider-config

A

Uses Upbound's AWS DynamoDB provider

B

Creates a DynamoDB table resource

C

Specify Kubernetes object with cluster-prefixed name and external name annotation

D

Defines id and customerId as string (S) type attributes

E

Sets id as the primary partition key

F

Specifies the On-demand pricing model

G

Creates global secondary index on customerId with all attributes projected

H

References the AWS provider configuration for authentication

Now, we can create the configuration for the DynamoDB table using a dynamodb.aws.upbound.io resource.

~$kubectl kustomize ~/environment/eks-workshop/modules/automation/controlplanes/crossplane/managed \

| envsubst | kubectl apply -f-

table.dynamodb.aws.upbound.io/eks-workshop-carts-crossplane created

~$kubectl wait tables.dynamodb.aws.upbound.io ${EKS_CLUSTER_NAME}-carts-crossplane \

--for=condition=Ready --timeout=5m

It takes some time to provision AWS managed services, in the case of DynamoDB up to 2 minutes. Crossplane will report the status of the reconciliation in the status field of the Kubernetes custom resources.

~$kubectl get tables.dynamodb.aws.upbound.io

NAME                                        READY  SYNCED   EXTERNAL-NAME                   AGE

eks-workshop-carts-crossplane               True   True     eks-workshop-carts-crossplane   6s

With this configuration applied, Crossplane will create a DynamoDB table in AWS, which can then be used by our application. In the next section, we'll update the application to use this newly created table.