ramondeklein
commented
1 month ago Please provide a valid values.yaml file, because the one that you submitted isn't valid:
- Cannot set
secrets:like this, probably meantsecrets: ~instead. - Pools should have a name.
I first applied the following namespace/secret that:
- Creates the namespace
my-minio - Created a MinIO configuration using
minio/minio123 - Provides access key/secret
testtest/testtestfor the user.
apiVersion: v1
kind: Namespace
metadata:
name: my-minio
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: minio-env-configuration
namespace: my-minio
data:
config.env: ZXhwb3J0IE1JTklPX1NUT1JBR0VfQ0xBU1NfU1RBTkRBUkQ9IkVDOjIiCmV4cG9ydCBNSU5JT19CUk9XU0VSPSJvbiIKZXhwb3J0IE1JTklPX1JPT1RfVVNFUj0ibWluaW8iCmV4cG9ydCBNSU5JT19ST09UX1BBU1NXT1JEPSJtaW5pbzEyMyIK
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: minio-user-dev
namespace: my-minio
data:
CONSOLE_ACCESS_KEY: dGVzdHRlc3QK
CONSOLE_SECRET_KEY: dGVzdHRlc3QKThen ran helm install --namespace my-minio --create-namespace my-minio -f tenant.yaml minio-operator/tenant with the following tenant.yaml:
secrets: ~
tenant:
name: minio-test
image:
repository: quay.io/minio/minio
pullPolicy: IfNotPresent
configuration:
name: minio-env-configuration
configSecret:
name: minio-env-configuration
existingSecret: true
pools:
- servers: 4
name: pool-0
metrics:
enabled: false
buckets:
- name: bucket1
- name: bucket2
users:
- name: "minio-user-dev"It creates the tenant, buckets and user.
I'm deploying the tenant using this values.yaml:
However, the cluster does not get fully initialized and throws this event
Users creation failed: The Access Key Id you provided does not exist in our records.Operator logs:
Your Environment
minio-operator): 6.0.2