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
Existing Issue
Please see the issue: #1668
It is marked resolved but I see the same behaviour in xpkg.upbound.io/crossplane-contrib/provider-aws:v0.43.1
Behaviour
I have created a global cluster and a primary region with 1 writer instance has been added under it.
When I try to create a secondary region, I am getting an error with message
message: 'create failed: pre-create failed: neither a masterUserPasswordSecretRef
is given, nor password autogeneration was enabled, not a restore is performed'
reason: ReconcileError
Expected behaviour
I was expecting that while adding the secondary region, we should not be required to provide masterUserPasswordSecretRef or enable autogeneration. That is the expecation in cloud formation as well.
Work-around
As a work-around, I provided a secret for masterUserPasswordSecretRef and used a key which does not exist in the secret data.
Found the work-around here: #1225
CR for Secondary DB cluster
Following CR was submitted for creating the secondary cluster:
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
Existing Issue
Please see the issue: #1668
It is marked resolved but I see the same behaviour in xpkg.upbound.io/crossplane-contrib/provider-aws:v0.43.1
Behaviour
I have created a global cluster and a primary region with 1 writer instance has been added under it.
When I try to create a secondary region, I am getting an error with message
Expected behaviour
I was expecting that while adding the secondary region, we should not be required to provide masterUserPasswordSecretRef or enable autogeneration. That is the expecation in cloud formation as well.
Work-around
As a work-around, I provided a secret for masterUserPasswordSecretRef and used a key which does not exist in the secret data.
Found the work-around here: #1225
CR for Secondary DB cluster
Following CR was submitted for creating the secondary cluster:
Versions
Crossplane version: 1.13.2
provider-aws version :v0.43.1
helm version: v3.14.4
kubectl version: v1.28.9
The text was updated successfully, but these errors were encountered: