From 417f77a6030e8fba6ccbbb663e0f3f1e7884e5b5 Mon Sep 17 00:00:00 2001 From: Allan Roger Reid Date: Wed, 13 Mar 2024 14:57:56 -0700 Subject: [PATCH] Custom deployments are required to edit YAML manually (#1156) Custom deployments are required to edit YAML manually to fulfill certain requirements or limitations such as those on resource requests. Fixes https://github.com/minio/operator/issues/1204 --------- Co-authored-by: Ravind Kumar --- .../common/common-install-operator-kubectl-plugin.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/includes/common/common-install-operator-kubectl-plugin.rst b/source/includes/common/common-install-operator-kubectl-plugin.rst index b4814689..cc23a0df 100644 --- a/source/includes/common/common-install-operator-kubectl-plugin.rst +++ b/source/includes/common/common-install-operator-kubectl-plugin.rst @@ -27,6 +27,14 @@ The command initializes the MinIO Operator with the following default settings: different :kube-docs:`cluster domain ` value. + +The Operator deploys with certain default settings and resource requests. +To modify these settings, do the following: + +1. Append the ``kubectl minio init -o > operator.yaml`` to save the YAML configuration to file +2. Modify settings as-needed to fit your deployment +3. Run ``kubectl apply -f operator.yaml`` to apply the customized Operator deployment. + .. important:: Document all arguments used when initializing the MinIO Operator.