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
Nothing worked till we actually set it to some base64 representation of a pw.
At first I suspected that the problem is in a way api-machinery checks for NotFound error, which @JaniszM cited. But now it seems the problem is a bit different, since created secret did not solve a problem until it was actually set to something.
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.
What happened?
Using ArgoCD.
Creating a clean DB, without a restoration point, and with the master password being generated.
Got error:
Seems the problem might be the silent error ignorance for missing k8s Secrets (masterUserPasswordSecretRef).
provider-aws/pkg/controller/docdb/dbcluster/setup.go
Line 229 in f759905
(thanks @sysradium for that check)
Creating the secret and the key didn't solve the problem, the password was not generated. I have provided a password by hand.
To get the Instance I had to create the secret and put a valid password over there.
How can we reproduce it?
This can help, my resource params:
What environment did it happen in?
Crossplane version: helm.sh/chart=crossplane-1.13.2
provider-aws: v0.43.1
EKS/k8s: v1.28
The text was updated successfully, but these errors were encountered: