{{- end }} {{- if .Values.extraSecret }} - name: extra-secret mountPath: "/tmp/minio-config-env" {{- end }} {{- include "minio.tlsKeysVolumeMount" . | indent 12 }} {{- if .Values.extraVolumeMounts }} {{- toYaml .Values.extraVolumeMounts | nindent 12 }} {{- end }} ports: - name: {{ $scheme }} containerPort: {{ .Values.minioAPIPort }} - name: {{ $scheme }}-console containerPort: {{ .Values.minioConsolePort }} env: - name: MINIO_ROOT_USER valueFrom: secretKeyRef: name: {{ template "minio.secretName" ....

 * things like environment, system properties, extensions etc. are loaded only once. It is caller duty to ensure
 * that subsequent call is right for the resident instance (ie no env change or different extension needed).
 * This implementation "pre-populates" MavenContext with pre-existing stuff (except for very first call)
 * and does not let DI container to be closed.
 */

{{- end }} {{- if .Values.extraSecret }} - name: extra-secret mountPath: "/tmp/minio-config-env" {{- end }} {{- include "minio.tlsKeysVolumeMount" . | indent 12 }} {{- if .Values.extraVolumeMounts }} {{- toYaml .Values.extraVolumeMounts | nindent 12 }} {{- end }} ports: - name: {{ $scheme }} containerPort: {{ .Values.minioAPIPort }} - name: {{ $scheme }}-console containerPort: {{ .Values.minioConsolePort }} env: - name: MINIO_ROOT_USER valueFrom: secretKeyRef: name: {{ template "minio.secretName" ....

{{- end }} {{- if .Values.extraSecret }} - name: extra-secret mountPath: "/tmp/minio-config-env" {{- end }} {{- include "minio.tlsKeysVolumeMount" . | indent 12 }} {{- if .Values.extraVolumeMounts }} {{- toYaml .Values.extraVolumeMounts | nindent 12 }} {{- end }} ports: - name: {{ $scheme }} containerPort: {{ .Values.minioAPIPort }} - name: {{ $scheme }}-console containerPort: {{ .Values.minioConsolePort }} env: - name: MINIO_ROOT_USER valueFrom: secretKeyRef: name: {{ template "minio.secretName" ....

# 環境變數 { #environment-variables }

/// tip

如果你已經知道什麼是「環境變數」並且知道如何使用它們，你可以放心跳過這一部分。

///

環境變數（也稱為「**env var**」）是一個獨立於 Python 程式碼**之外**的變數，它存在於**作業系統**中，可以被你的 Python 程式碼（或其他程式）讀取。

環境變數對於處理應用程式**設定**（作為 Python **安裝**的一部分等方面）非常有用。

## 建立和使用環境變數 { #create-and-use-env-vars }

你在 **shell（終端機）**中就可以**建立**和使用環境變數，並不需要用到 Python：

//// tab | Linux, macOS, Windows Bash

<div class="termy">

```console

        uses: actions/setup-java@v5
        with:
          distribution: temurin
          java-version: 17
      - name: Clone gradle/ci-health repository
        run: |
          git clone https://${{ env.BOT_GRADLE_GITHUB_TOKEN }}@github.com/gradle/ci-health.git /tmp/gradle-ci-health
      - name: Generate test class runtime JSON
        run: |
          cd /tmp/gradle-ci-health

                param("JdkProviderEnabled", "false")
                // should be the same version we run TeamCity with
                param("env.JAVA_HOME", javaHome(DefaultJvm(JvmVersion.JAVA_21, JvmVendor.OPENJDK), os))
            }

            steps {
                script {
                    name = "CHECK_USED_WRAPPER"
                    scriptContent =

{{- end }} {{- if .Values.extraSecret }} - name: extra-secret mountPath: "/tmp/minio-config-env" {{- end }} {{- include "minio.tlsKeysVolumeMount" . | indent 12 }} {{- if .Values.extraVolumeMounts }} {{- toYaml .Values.extraVolumeMounts | nindent 12 }} {{- end }} ports: - name: {{ $scheme }} containerPort: {{ .Values.minioAPIPort }} - name: {{ $scheme }}-console containerPort: {{ .Values.minioConsolePort }} env: - name: MINIO_ROOT_USER valueFrom: secretKeyRef: name: {{ template "minio.secretName" ....

	"encoding/json"
	"fmt"
	"net/http"
	"slices"
	"strings"
	"sync"

	"github.com/minio/minio/internal/config"
	"github.com/minio/minio/internal/mcontext"
	"github.com/minio/mux"
	"github.com/minio/pkg/v3/env"
	"github.com/prometheus/client_golang/prometheus"
	"github.com/prometheus/client_golang/prometheus/promhttp"
)

type promLogger struct{}

func (p promLogger) Println(v ...any) {

You can either use KES - together with an external KMS - or, much simpler,
set the env. variable `MINIO_KMS_SECRET_KEY` and start/restart the MinIO server. For more details about KES and how
to set it up refer to our [KMS Guide](https://github.com/minio/minio/blob/master/docs/kms/README.md).

Instead of configuring an external KMS you can start with a single key by
setting the env. variable `MINIO_KMS_SECRET_KEY`. It expects the following
format:

```sh