第 4 步：将应用程序部署到 Amazon EKS 并将数据写入您的 Amazon Keyspaces 表 - Amazon Keyspaces（Apache Cassandra 兼容）
Amazon Web Services 文档中描述的 Amazon Web Services 服务或功能可能因区域而异。要查看适用于中国区域的差异，请参阅 中国的 Amazon Web Services 服务入门 (PDF)。

本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。

第 4 步：将应用程序部署到 Amazon EKS 并将数据写入您的 Amazon Keyspaces 表

在本教程的这一步中，您将为您的应用程序配置 Amazon EKS 部署，并确认应用程序正在运行并且可以连接到 Amazon Keyspaces。

要将应用程序部署到 Amazon EKS，您需要在名为的文件中配置所有相关设置deployment.yaml。然后，Amazon EKS 将使用此文件来部署应用程序。文件中的元数据应包含以下信息：

  • 应用程序名称应用程序的名称。在本教程中，我们使用my-keyspaces-app。

  • Kubernetes 命名空间是 Amazon EKS 集群的命名空间。在本教程中，我们使用my-eks-namespace。

  • 亚马逊 EKS 服务账户命名亚马逊 EKS 服务账户的名称。在本教程中，我们使用my-eks-serviceaccount。

  • 图像名称应用程序映像的名称。在本教程中，我们使用my-keyspaces-app。

  • 图片 URI 来自亚马逊 ECR 的 Docker 镜像 URI。

  • Amazon 账户 ID 您的 Amazon 账户 ID。

  • IAM 角色 ARN 为服务账户创建的 IAM 角色的 ARN。在本教程中，我们使用my-iam-role。

  • Amazon Web Services 区域 在 Amazon Web Services 区域 你创建 Amazon EKS 集群的 Amazon EKS 集群中。

在此步骤中，您将部署并运行连接到 Amazon Keyspaces 并将数据写入表的应用程序。

  1. 配置 deployment.yaml 文件。您需要替换以下值：

    • name

    • namespace

    • serviceAccountName

    • image

    • AWS_ROLE_ARN value

    • The Amazon Web Services 区域 in CASSANDRA_HOST

    • AWS_REGION

    你可以使用以下文件作为示例。

    apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-keyspaces-app
  namespace: my-eks-namespace
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-keyspaces-app
  template:
    metadata:
      labels:
        app: my-keyspaces-app
    spec:
      serviceAccountName: my-eks-serviceaccount
      containers:
      - name: my-keyspaces-app
        image: 111122223333.dkr.ecr.aws-region.amazonaws.com/my-ecr-repository:latest
        ports:
        - containerPort: 8080
        env:
        - name: CASSANDRA_HOST
          value: "cassandra.aws-region.amazonaws.com:9142"
        - name: CASSANDRA_DC
          value: "aws-region"
        - name: AWS_WEB_IDENTITY_TOKEN_FILE
          value: /var/run/secrets/eks.amazonaws.com/serviceaccount/token
        - name: AWS_ROLE_ARN
          value: "arn:aws:iam::111122223333:role/my-iam-role"
        - name: AWS_REGION
          value: "aws-region"

  2. 部署 deployment.yaml。

    kubectl apply -f deployment.yaml

    输出应如下所示：

    deployment.apps/my-keyspaces-app created

  3. 检查您的 Amazon EKS 集群命名空间中 Pod 的状态。

    kubectl get pods -n my-eks-namespace

    输出应类似于以下示例：

    NAME                    READY STATUS RESTARTS AGE
my-keyspaces-app-123abcde4f-g5hij 1/1 Running 0 75s

    要了解更多详细信息，您可以使用以下命令。

    kubectl describe pod my-keyspaces-app-123abcde4f-g5hij -n my-eks-namespace
    Name:                 my-keyspaces-app-123abcde4f-g5hij
Namespace:            my-eks-namespace
Priority:             2000001000
Priority Class Name:  system-node-critical
Service Account:      my-eks-serviceaccount
Node:                 fargate-ip-192-168-102-209.ec2.internal/192.168.102.209
Start Time:           Thu, 23 Nov 2023 12:15:43 +0000
Labels:               app=my-keyspaces-app
                      eks.amazonaws.com/fargate-profile=my-fargate-profile
                      pod-template-hash=6c56fccc56
Annotations:          CapacityProvisioned: 0.25vCPU 0.5GB
                      Logging: LoggingDisabled: LOGGING_CONFIGMAP_NOT_FOUND
Status:               Running
IP:                   192.168.102.209
IPs:
  IP:           192.168.102.209
Controlled By:  ReplicaSet/my-keyspaces-app-6c56fccc56
Containers:
  my-keyspaces-app:
    Container ID:   containerd://41ff7811d33ae4bc398755800abcdc132335d51d74f218ba81da0700a6f8c67b
    Image:          111122223333.dkr.ecr.aws-region.amazonaws.com/my_eks_repository:latest
    Image ID:       111122223333.dkr.ecr.aws-region.amazonaws.com/my_eks_repository@sha256:fd3c6430fc5251661efce99741c72c1b4b03061474940200d0524b84a951439c
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Thu, 23 Nov 2023 12:15:19 +0000
      Finished:     Thu, 23 Nov 2023 12:16:17 +0000
    Ready:          True
    Restart Count:  1
    Environment:
      CASSANDRA_HOST:               cassandra.aws-region.amazonaws.com:9142
      CASSANDRA_DC:                 aws-region
      AWS_WEB_IDENTITY_TOKEN_FILE:  /var/run/secrets/eks.amazonaws.com/serviceaccount/token
      AWS_ROLE_ARN:                 arn:aws:iam::111122223333:role/my-iam-role
      AWS_REGION:                   aws-region
      AWS_STS_REGIONAL_ENDPOINTS:   regional
    Mounts:
      /var/run/secrets/eks.amazonaws.com/serviceaccount from aws-iam-token (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-fssbf (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  aws-iam-token:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  86400
  kube-api-access-fssbf:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason           Age                From               Message
  ----     ------           ----               ----               -------
  Warning  LoggingDisabled  2m13s              fargate-scheduler  Disabled logging because aws-logging configmap was not found. configmap "aws-logging" not found
  Normal   Scheduled        89s                fargate-scheduler  Successfully assigned my-eks-namespace/my-keyspaces-app-6c56fccc56-mgs2m to fargate-ip-192-168-102-209.ec2.internal
  Normal   Pulled           75s                kubelet            Successfully pulled image "111122223333.dkr.ecr.aws-region.amazonaws.com/my_eks_repository:latest" in 13.027s (13.027s including waiting)
  Normal   Pulling          54s (x2 over 88s)  kubelet            Pulling image "111122223333.dkr.ecr.aws-region.amazonaws.com/my_eks_repository:latest"
  Normal   Created          54s (x2 over 75s)  kubelet            Created container my-keyspaces-app
  Normal   Pulled           54s                kubelet            Successfully pulled image "111122223333.dkr.ecr.aws-region.amazonaws.com/my_eks_repository:latest" in 222ms (222ms including waiting)
  Normal   Started          53s (x2 over 75s)  kubelet            Started container my-keyspaces-app

  4. 查看 Pod 的日志，确认您的应用程序正在运行并且可以连接到您的 Amazon Keyspaces 表。您可以使用以下命令执行此操作。请务必替换您的部署名称。

    kubectl logs -f my-keyspaces-app-123abcde4f-g5hij -n my-eks-namespace

    您应该能够看到确认与 Amazon Keyspaces 连接的应用程序日志条目，如下例所示。

    2:47:20.553 [s0-admin-0] DEBUG c.d.o.d.i.c.metadata.MetadataManager - [s0] Adding initial contact points [Node(endPoint=cassandra.aws-region.amazonaws.com/1.222.333.44:9142, hostId=null, hashCode=e750d92)]
22:47:20.562 [s0-admin-1] DEBUG c.d.o.d.i.c.c.ControlConnection - [s0] Initializing with event types [SCHEMA_CHANGE, STATUS_CHANGE, TOPOLOGY_CHANGE]
22:47:20.564 [s0-admin-1] DEBUG c.d.o.d.i.core.context.EventBus - [s0] Registering com.datastax.oss.driver.internal.core.metadata.LoadBalancingPolicyWrapper$$Lambda$812/0x0000000801105e88@769afb95 for class com.datastax.oss.driver.internal.core.metadata.NodeStateEvent
22:47:20.566 [s0-admin-1] DEBUG c.d.o.d.i.c.c.ControlConnection - [s0] Trying to establish a connection to Node(endPoint=cassandra.us-east-1.amazonaws.com/1.222.333.44:9142, hostId=null, hashCode=e750d92)

  5. 对您的 Amazon Keyspaces 表运行以下 CQL 查询，以确认您的表中已写入一行数据：

    SELECT * from aws.user;

    您应看到以下输出：

    fname    | lname | username | last_update_date 
----------+-------+----------+-----------------------------
random    | k     | test     | 2023-12-07 13:58:31.57+0000