How to add a S3 snapshot repository via values.yaml?

[mame-leadec]

Hello,

i want to add a S3 snapshot repo via helm chart values. The S3 storage is MinIO pod which resides in the same namespace as the OpenSearchCluster. The bucket "default-bucket" is already configured/created.

My values.yaml look like this:

opensearchCluster:
  .....

  general:
    keystore:
    - secret:
        name: my-secret
      keyMappings:
        # Renames key accessKey in secret to s3.client.default.access_key in keystore
        username: s3.client.default.access_key
        password: s3.client.default.secret_key
    pluginsList: ["repository-s3"]
    snapshotRepositories:
      - name: my_s3_repository_1
        type: s3
        settings:
          bucket: default-bucket
          endpoint: http://minio-0.minio-svc.opensearch.svc.cluster.local:9000
          path_style_access: true

When the OpenSearch Cluster is up and running no snapshot repository is configured. Am i missing something?

If i try later via REST API i can configure the snapshot repository and use it.:

curl -k -u admin:admin -X PUT "https://localhost:9200/_snapshot/my_s3_repository_1" -H 'Content-Type: application/json' -d'
{
 "type": "s3",
 "settings": {
   "bucket": "default-bucket",
   "endpoint": "http://minio-0.minio-svc.opensearch.svc.cluster.local:9000",
   "path_style_access": true
 }
}
'

So it seems the config parameter like bucket name and URL are correct.

[swoehrl-mw]

Hi @mame-leadec. Your values.yaml looks correct.
Can you please verify (with a kubectl describe opensearchcluster) if the repo config is part of the CR or if there are any events related to snapshots (they disappear after some time so you might need to check with a new cluster), either an error or a report that a repo was created?

Also, are you using at least version 2.6.0 of the operator? There were some changes in the handling of snapshot repos in that version.

[mame-leadec]

Hi @swoehrl-mw
unfortunatly iam not using the OpenSearch Operator anymore. For our usecase we stick to the plain OpenSearch helm charts and do the configuration via REST API. Still a cumbersome workaround. But it works. ;)

Thanks for your help.