os.TransitionVersionID = info.VersionID
}

// shouldRemoveRemoteObject determines if a transitioned object should be
// removed from remote tier. If remote object is to be deleted, returns the
// corresponding tier deletion journal entry and true. Otherwise returns empty
// jentry value and false.
func (os *objSweeper) shouldRemoveRemoteObject() (jentry, bool) {
	if os.TransitionStatus != lifecycle.TransitionComplete {

	"github.com/minio/minio/internal/event/target"
	"github.com/minio/minio/internal/logger"
	xnet "github.com/minio/pkg/v3/net"
	"github.com/minio/pkg/v3/quick"
)

// Save config file to corresponding backend
func Save(configFile string, data any) error {
	return quick.SaveConfig(data, configFile, globalEtcdClient)
}

// Load config from backend
func Load(configFile string, data any) (quick.Config, error) {

existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed...

existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed...

existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed...

existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed...

                * Serialization: you could return an arbitrary object and the
                    `response_model` would be used to serialize that object into the
                    corresponding JSON.
                * Filtering: the JSON sent to the client will only contain the data
                    (fields) defined in the `response_model`. If you returned an object

two parity drives, 100 MiB file takes only approximately 114 MiB.

Below is a list of data/parity drives and corresponding _approximate_ storage space usage on a 16 drive MinIO deployment. The field _storage
usage ratio_ is simply the drive space used by the file after erasure-encoding, divided by actual file size.

    private static final int HTTP_STATUS_NOT_FOUND = 404;

    /** HTTP status code for OK */
    private static final int HTTP_STATUS_OK = 200;

    /**
     * Cache for client rules mapping client names to their corresponding URL patterns.
     * This cache improves performance by avoiding repeated parsing of client configuration rules.
     * The key is the rule string, and the value is a pair containing the client name and compiled pattern.

existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed...