Skip to content
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

minio as object storage and shared storage at the same time #1305

Open
jdongo-aneo opened this issue Jul 24, 2024 · 0 comments
Open

minio as object storage and shared storage at the same time #1305

jdongo-aneo opened this issue Jul 24, 2024 · 0 comments

Comments

@jdongo-aneo
Copy link
Contributor

Describe the bug
When one wants to use minio as an object storage and shared object at the same time, an error occur.
A minio module is created and a second one named minio_s3_fs is attempted to be created. This fails because the secrets created for the minio module have the same name with the one for minio_s3_fs.

To Reproduce
Steps to reproduce the behavior:

  1. In the Onprem deployment, go to 'parameters.tfvars'
  2. Uncomment minio = {} and minio_s3_fs = {}
  3. Deploy Armonik
  4. See error

Expected behavior
The deployment should succeed

Screenshots

image

Infra

  • Target (Local, AWS, Docker compose, etc..) : Onpremise
  • ObjectStorage: minio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant