Bug: CacheCluster Status Lacks cacheNodes Information

[edwanyoike]

Describe the bug
The status object of the elasticache.services.k8s.aws/v1alpha1 CacheCluster custom resource does not include the cacheNodes key. According to the CRD, this key is expected to be present in the status to provide information about the individual cache nodes within the cluster [1]

[1] https://github.com/aws-controllers-k8s/elasticache-controller/blob/v0.2.3/helm/crds/elasticache.services.k8s.aws_cacheclusters.yaml#L595

Steps to reproduce

1. Apply a CacheCluster manifest to create an ElastiCache cluster using the ACK controller.

2. Once the CacheCluster resource is created and reconciled 3. , inspect the status of the resource using kubectl get cachecluster xxxxx -o yaml or kubectl describe cachecluster xxxxx

3. Observe that the status object does not contain the cacheNodes key.

Expected outcome

The status object of the CacheCluster resource should include a cacheNodes key containing an array of objects, where each object represents a cache node and includes details such as its endpoint, port, and status, as defined in the CRD.

Environment

Kubernetes version: 1.32

Using EKS (yes/no), if so version?: yes, eks.9

AWS service targeted (S3, RDS, etc.): ElastiCache

ElastiCache ACK version: 0.2.4

[github-actions]

Hello @edwanyoike 👋 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.

[rushmash91]

This was resolved as part of the v1.2.1 patch for the elasticache-controller. Feel free to reopen if you still encounter this issue 🙂

/close

[ack-prow]

@rushmash91: Closing this issue.

In response to this:

This was resolved as part of the v1.2.1 patch for the elasticache-controller. Feel free to reopen if you still encounter this issue 🙂

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.