No option to configure S3 Credentials in CR

[abhi2303237]

Currently, the CRD doesn't provide an option to configure S3 identities — we can only enable or disable S3 support.

seaweedfs-operator/config/crd/bases/seaweed.seaweedfs.com_seaweeds.yaml

Line 2299 in 5912584

s3:

It would be great if we could extend the S3 configuration to allow setting identities directly or a ref to the file containing the identity JSON. This would make the setup much more flexible. I will try to contribute.

[abhi2303237]

@chrislusf Could u please have a look.

Thanks

[chrislusf]

please address the gemini review comments.

[Auxburger]

@chrislusf @abhi2303237 does this actually work for you? I am trying it out right now, used the latest master but always get AccessDenied messages. The s3.json is mounted correctly:

{
  "identities": [
    {
      "name": "admin",
      "actions": ["Admin"], 
      "credentials": [
        {
          "accessKey": "accessKey",
          "secretKey": "secretKey"
        }
      ]
    }
  ]
}

But when trying to connect with the s3 endpoint using basic auth it does not allow to read or create anything.

[abhi2303237]

@Auxburger I tested it using aws cli.

[Auxburger]

@chrislusf do you already know when there will be an official release? 😊