0

I've installed the operator, and trying to create the innodb cluster with backup profile which uses S3. There is no mention of S3 in the documentation, but they mentioned in a conference about S3 support. Found little source about the subject, which mentions set up something like this:

Secret:

apiVersion: v1
kind: Secret
metadata:
  name: aws-credentials
type: Opaque
data:
  AWS_ACCESS_KEY_ID: <base64-encoded-access-key-id>
  AWS_SECRET_ACCESS_KEY: <base64-encoded-secret-access-key>

then the cluster definition:

apiVersion: mysql.oracle.com/v1
kind: MySQLCluster
metadata:
  name: my-mysql-cluster
spec:
  replicas: 3
  version: "8.0"
  backupProfiles:
    - name: s3-backup
      storageProvider: s3
      s3:
        region: <aws-region>
        bucketName: <s3-bucket-name>
        credentialsSecret:
          name: aws-credentials

All looks fine, but I'm using EKS cluster with OIDC, and I have service account defined having access to S3 properly. My question is, is there any way to configure S3 backup profile without using the aws secret keys, but using the service account?

Improve this question

1 Answer 1

Reset to default
1

I got the same problem today, not sure about using the same operator version, anyway the problem is the credentials does not need to be passed as literals variables,you need to create a credential file in aws stile inside a secret, check https://sysrestarting.blogspot.com/2024/06/mysql-operator-s3-innodbcluster-backup.html

Improve this answer
New contributor
fatinarambo is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
1
  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
    – Dave M
    Commented yesterday

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .