ACK Kinesis Controller- Kinesis Stream status stuck in 'CREATING'

[kalyaninikam1]

Describe the bug
I'm creating a Kinesis stream through ACK kinesis controller but the stream status is stuck in the 'CREATING' state.
There is a discrepancy between Kinesis stream status in the AWS Console (shows as Active) vs Kubernetes custom resource (shows as Creating).

Steps to reproduce
Create a kinesis stream using ACK https://github.com/aws-controllers-k8s/kinesis-controller/blob/8a5a5d44fac610944279a2d16f157851ab4e65ed/test/e2e/resources/stream_simple.yaml and check the status - ' kubectl describe stream <stream_name> '.

Expected outcome
Kinesis stream CR status should be 'ACTIVE'.

• Kubernetes version : v1.31
• AWS service targeted : Kinesis
• ACK Kinesis controller version: 1.0.5

Logs

[github-actions]

Hello @kalyaninikam1 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[kalyaninikam1]

After upgrading a ACK Kinesis controller to version 1.0.7, the Kinesis stream CR status is 'ACTIVE' now.

New Bug
When the shard count value of a CR stream is updated, there is a discrepancy between the open shard count value in the AWS Console vs Kubernetes custom resource.

Logs

[kalyaninikam1]

I'm not able to adopt the existing Kinesis stream in version - 1.0.7. I can adopt stream in previous versions e.g 1.0.5, 1.0.6 .

Logs
Log of a ACK controller pod.

{"level":"info","ts":"2025-04-07T11:45:11.190Z","logger":"adoption.adopted-reconciler","msg":"starting adoption reconciliation","target_group":"kinesis.services.k8s.aws","target_kind":"Stream","namespace":"####","name":"####","generation":1}

To adopt existing stream I'm using following manifest

apiVersion: services.k8s.aws/v1alpha1
kind: AdoptedResource
metadata:
name: "####"
spec:
aws:
nameOrID: "####"
kubernetes:
group: kinesis.services.k8s.aws
kind: Stream

[jlbutler]

@kalyaninikam1 it looks like the initial issue and a second issue are both resolved on this one.

To keep better track of specific issues, I'm going to close this one out. If the adoption issue persists, please try adoption through annotation (https://aws-controllers-k8s.github.io/community/docs/user-docs/features/#resourceadoption).

If that does not work for you, please open a new issue and we'll help out. Thank you!