Skip to content

DynamoDB controller cannot update any Table information if provisionedThroughput contains the original values #1067

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rbranche opened this issue Nov 15, 2021 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@rbranche
Copy link

Describe the bug
DynamoDB controller cannot update any Table information if provisionedThroughput contains the original values

Steps to reproduce

  1. Create Table object
apiVersion: dynamodb.services.k8s.aws/v1alpha1
kind: Table
metadata:
  name: mytable
spec:
  tableName: mytable
  attributeDefinitions:
    - attributeName: field
      attributeType: S
  keySchema:
    - attributeName: field
      keyType: HASH
  provisionedThroughput:
    readCapacityUnits: 25
    writeCapacityUnits: 25
  1. Try to add new Global Secondary Indexes to Table object
apiVersion: dynamodb.services.k8s.aws/v1alpha1
kind: Table
metadata:
  name: mytable
spec:
  tableName: mytable
  attributeDefinitions:
    - attributeName: field
      attributeType: S
  globalSecondaryIndexes:
    - indexName: field-index
      keySchema:
        - attributeName: field
          keyType: HASH
      projection:
        projectionType: KEYS_ONLY
      provisionedThroughput:
        readCapacityUnits: 25
        writeCapacityUnits: 25
  keySchema:
    - attributeName: field
      keyType: HASH
  provisionedThroughput:
    readCapacityUnits: 25
    writeCapacityUnits: 25
  1. Controller fails to update Table with new GSI because spec.provisionedThroughput values didn't change
│     Message:            ValidationException: The provisioned throughput for the table will not change. The requested value equals the current value. Current ReadCapacityUnits provisioned for the tab │
│ le: 25. Requested ReadCapacityUnits: 25. Current WriteCapacityUnits provisioned for the table: 25. Requested WriteCapacityUnits: 25. Refer to the Amazon DynamoDB Developer Guide for current limits a │
│ nd how to request higher limits.                                                                                                                                                                       │
│                         status code: 400, request id: EFUN8JOS0NKP1NCISHIMPGHR07VV4KQNSO5AEMVJF66Q9ASUAAJG

Expected outcome
GSI for Table is created properly

Environment

  • Kubernetes version: 1.21
  • Using EKS (yes/no), if so version? 2
  • AWS service targeted (S3, RDS, etc.) DynamoDB
@rbranche rbranche added the kind/bug Categorizes issue or PR as related to a bug. label Nov 15, 2021
@a-hilaly
Copy link
Member

Hey @rbranche, this is currently part of #1029 - all the fields will support updates once it's closed

@rbranche
Copy link
Author

Thanks @a-hilaly. Duplicate of #1029.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants