Mysql operator S3 innodbcluster backup SECRET CONFIG

[ERROR] [backup] Backup failed with an exception: Util.dump_instance: Argument #2: The AWS access and secret keys were not found in: environment variables    


mysql do not provide a good documentation about mysql operator. ORACLE WANT YOU TO USE OCI! USE OCI cmon. 

mysql operator wants aws "cretentials" file down the "/mysqlsh/.aws folder, it does this in pod through VolumeMount the secret file, nothing about to worry about. 


PS: If you are trying to backup to an s3 endpoint with self signed or with private ca certificate, loose all hopes. I do not find a solution about that. 

cat secret  

[default]  
aws_access_key_id=REDACTED
aws_secret_access_key=REDACTED

cat secret | base64 -w 0


W2RlZmF1bHRdIAphd3NfYWNjZXNzX2tleV9pZD1SRURBQ1RFRAphd3Nfc2VjcmV0X2FjY2Vzc19rZXk9UkVEQUNURUQKCg==                                                                                                                                                                             

apiVersion: v1
kind: Secret
metadata:
 name: s3-secret
type: Opaque
data:
 credentials: W2RlZmF1bHRdIAphd3NfYWNjZXNzX2tleV9pZD1SRURBQ1RFRAphd3Nfc2VjcmV0X2FjY2Vzc19rZXk9UkVEQUNURUQKCg==


then, use the "s3-secret" in :

backupProfiles:
- dumpInstance:
storage:
s3:
bucketName: test
config: s3-secret
endpoint: https://ENDPOINT
prefix: /path/whereyouwant/
profile: ""

Commenti

Post popolari in questo blog

Teams Incoming Webhook deprecated: Use PowerAutomate - Workflow

Fedora - KVM - qemu - Windows 11 guest. error: swtpm at /usr/bin/swtpm does not support TPM 2