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
Follow up from #1139 (comment), it appears as though Secrets referenced in spec that do not exist are being treated as a dbinstance terminal error and therefore the ACK controller is not re-reconciling.
Steps to reproduce
Create DBInstance with reference to non-existing secret.
Check status, it shows.
conditions:
- message: kubernetes secret not foundstatus: "True"type: ACK.Terminal
- lastTransitionTime: "2022-06-03T18:25:10Z"message: Resource synced successfullyreason: resource is in terminal conditionstatus: "True"type: ACK.ResourceSynced
Apply secret
Wait for changes. Nothing changes
Expected outcome
I expected a the controller to re-reconcile and pick up the secret.
Environment
EKS using 0.0.24 of ACK RDS Operator
Kubernetes version: v1.21.12-eks-a64ea69
Using EKS: Yes (eks.7)
AWS service targeted (S3, RDS, etc.) RDS
The text was updated successfully, but these errors were encountered:
Samze
changed the title
DBInstance (and other resources) do not retry when a spec defined Secret is missing.
DBInstance (and other resources) do not re-reconcile when a spec defined Secret is missing.
Jun 3, 2022
Samze
changed the title
DBInstance (and other resources) do not re-reconcile when a spec defined Secret is missing.
DBInstance (and other resources) do not re-reconcile when a spec defined Secret is missing
Jun 3, 2022
Fixesaws-controllers-k8s/community#1318
Description of changes:
If an ACK resource is evaluated before a secret becomes available, the controller should attempt to retry (with exponential backoff) until the secret exists. This pull request ensures that any error returned by `SecretValueFromReference` is retried by the controller.
Note: I chose not to update the error values in `SecretValueFromReference` because I thought it was more appropriate that the SDK logic chose the requeue action, not the secret fetching method.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Describe the bug
Follow up from #1139 (comment), it appears as though Secrets referenced in spec that do not exist are being treated as a dbinstance terminal error and therefore the ACK controller is not re-reconciling.
Steps to reproduce
Expected outcome
I expected a the controller to re-reconcile and pick up the secret.
Environment
EKS using 0.0.24 of ACK RDS Operator
The text was updated successfully, but these errors were encountered: