-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant configure backup without credentialsSecret #1687
Comments
@ItielOlenick as you can see, this error is connected with your storage name. Try to use e.g. aws-s3 like a storage name:
|
@hors Not really.
It clearly tries to extract the secretref from a secret named |
@ItielOlenick yes, you are right. I have reproduced it. We will fix it in the next release under https://perconadev.atlassian.net/browse/K8SPXC-1382 task. |
@hors Thank you! Any chance you can have a look at https://perconadev.atlassian.net/browse/PXB-3270 while you are at it?
That is not quite true. The supported feature is the instance profile credentials retrieval through IMDS and not though IRSA, which makes it somewhat useless in EKS. |
I too would love to see support for IRSA, i.e. authentication via |
Report
When not providing credentialsSecret in the s3 section of the deploy/cr.yaml backups can't be taken.
More about the problem
Documentation states:
When trying to drop s3.credentialsSecret the operator logs show the following errors:
cr.yaml:
Steps to reproduce
Versions
Anything else?
No response
The text was updated successfully, but these errors were encountered: