Please refer to the Vault ESS Guide . Either the step is missing due to doc error in specifying provider creds for provider pods(providerconfig config is missing) or the implementation has some gap, since following this guide in verbatim fails to provision cloud resources in the first place.
How can we reproduce it?
Follow the doc to provision any cloud resource (e.g. AWS RDS DB) without provider config configuration , expect consistent provisioning failure
What happened?
Please refer to the Vault ESS Guide . Either the step is missing due to doc error in specifying provider creds for provider pods(providerconfig config is missing) or the implementation has some gap, since following this guide in verbatim fails to provision cloud resources in the first place.
How can we reproduce it?
Follow the doc to provision any cloud resource (e.g. AWS RDS DB) without provider config configuration , expect consistent provisioning failure
What environment did it happen in?
Crossplane version: 1.15.2