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

helm: tenant: Regression on tenant.configSecret.existingConfiguration #2297

Closed
ClemaX opened this issue Aug 28, 2024 · 1 comment · Fixed by #2299
Closed

helm: tenant: Regression on tenant.configSecret.existingConfiguration #2297

ClemaX opened this issue Aug 28, 2024 · 1 comment · Fixed by #2299

Comments

@ClemaX
Copy link

ClemaX commented Aug 28, 2024

Setting tenant.configSecret.existingConfiguration to true has no effect.

Expected Behavior

The default myminio-env-configuration should not be created if the existingConfiguration parameter is true

Current Behavior

The default myminio-env-configuration is created.

Possible Solution

Add an if condition to create the secret unless the parameter is set.

Steps to Reproduce (for bugs)

  1. Create values.yaml
cat > values.yaml <<EOF
tenant:
  configuration:
    name: custom-minio-env
  configSecret:
    name: custom-minio-env
    existingSecret: true
EOF
  1. Install with dry-run
helm install \
  -n minio --create-namespace \
  --values values.yaml \
  minio-test minio-operator/tenant \
  --dry-run
  1. Inspect the output

You can see that the Secret is part of the output:

# Source: tenant/templates/tenant-configuration.yaml
apiVersion: v1
kind: Secret
metadata:
  name: custom-minio-env
type: Opaque
stringData:
  config.env: |-
    export MINIO_ROOT_USER="minio"
    export MINIO_ROOT_PASSWORD="minio123"

Context

Providing a custom preexisting secret.

Regression

Regression from #2265

Your Environment

  • Version used (minio-operator): 6.0.3
@ramondeklein
Copy link
Contributor

Duplicate of #2298.

@ramondeklein ramondeklein linked a pull request Aug 28, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants