Default gitlab installation on the k8s storing terraform states locally instead of S3.

Summary

Default installation on the k8s storing terraform states locally instead of S3.

Steps to reproduce

• Install helm chart with default settings (internal minio)
• Create new project which is using terraform states
• Import or create terraform state
• Check minio bucket - terraform states folder will be empty.

This causing 50% errors in the half of the requests as state is "stored" on the local fs of the pod and will be lost if pod is restarted.

If I am adding

  appConfig:
    terraformState:
      enabled: true

GitLab starting to store states in minio. To me such behavior is very confusing, IMO GitLab should either not allow to save state at all or to store it in minio/

Configuration used

(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))

Default appConfig: block

Current behavior

Terraform states are enabled but stored in the filesystem

Expected behavior

States are either blocked or enabled by default to minio.

Versions

• Chart: 6.7.0
• Platform:
  • Self-hosted: k8s community edition
• Kubernetes: (kubectl version)
  • Client: 1.23
  • Server: 1.23
• Helm: (helm version)
  • Client:v3.9.4
  • Server:v3.9.4