You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've updated the provided manifest and the template we use with the 'identifier' specification, but ArgoCD is not able to sync and apply the 'identifier'.
What happened?
The newly created RDS instance is created with 'terraform-20240816071534381600000036' 'DB Identifier':
ArgoCD is not able to sync the identifier:
In the CRD, the 'identifier' is visible only under kubectl.kubernetes.io/last-applied-configuration annotation, but it's not shown under the spec section.
Relevant Error Output Snippet
No response
Crossplane Version
1.14.2
Provider Version
1.0.0
Kubernetes Version
1.29
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Affected Resource(s)
rds.aws.upbound.io/v1beta2
- InstanceResource MRs required to reproduce the bug
Steps to Reproduce
I've updated the provided manifest and the template we use with the '
identifier
' specification, but ArgoCD is not able to sync and apply the'identifier'
.What happened?
The newly created RDS instance is created with
'terraform-20240816071534381600000036'
'DB Identifier':ArgoCD is not able to sync the identifier:
In the CRD, the
'identifier'
is visible only underkubectl.kubernetes.io/last-applied-configuration
annotation, but it's not shown under thespec
section.Relevant Error Output Snippet
No response
Crossplane Version
1.14.2
Provider Version
1.0.0
Kubernetes Version
1.29
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered: