Yatai customize DNS domain for internal components about yatai HOT 3 CLOSED

I finally managed to install a MinIO gateway to Azure Blob Storage.
As this feature is deprecated by MinIO, here is the last usable version for Azure Gateway:

HELM REPO:    https://charts.min.io/
HELM VERSION: 11.2.15
APP_VERSION:  2022.4.29

Helm custom values should look like:

persistence:
  enabled: false

gateway:
  enabled: true
  type: azure
  replicaCount: 1
  auth:
    azure:
      accessKey: <YATAI_ACCESS_KEY>
      secretKey: <YATAI_SECRET_KEY>
      serviceEndpoint: <STORAGE_ACCOUNT_ENDPOINT>
      storageAccountName: <STORAGE_ACCOUNT_NAME>
      storageAccountKey: <STORAGE_ACCOUNT_ACCESS_KEY>

On my side, this issue can be closed as the new nginx annotation is available: yatai.ai/enable-ssl

from yatai.

@mts-dyt Thanks for the feedback!

The default minio component is intended to be used in a test environment, you can specify external S3 during installation so that minio will not be installed.

It is designed to work out of the box, and we automatically generate the domain name and certificate to save users valuable time from having to manually configure it themselves.

If you really want to use our minio installation, you can do so by modifying the yatai-minio ingress resource under the yatai-components namespace, but of course, yatai will remove the logic to automatically install minio and docker-registry later

from yatai.

@yetone , when customizing the Yatai ingress with my own domain without SSL, the bento push command still refers to https:

Error: [cli] `push` failed: request failed with status code 400: {"error":"pre sign s3 upload url: get bucket yatai exist: Get \"https://minio-yatai-infra-cluster.<domain>.io/yatai/?location=\": x509: certificate is valid for ingress.local, not minio-yatai-infra-cluster.lychee.<domain>.io"}

update: This is fixed in v0.3.11 with the annotation yatai.ai/enable-ssl: false

from yatai.