minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00
Code Activity

DOCS-1021: Adding helm information (#1060)

Browse Source 
Closes #1021 
Closes #1055 
Closes #968 
Closes #943 


---------

Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Pedro Juarez <pjuarezd@users.noreply.github.com>
This commit is contained in:
Ravind Kumar
2023-11-16 12:56:20 -05:00
committed by GitHub
parent 09ce8edb48
commit c770ba9d76
17 changed files with 1577 additions and 230 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
source/includes/k8s/deploy-operator.rst
View File

@ -67,6 +67,10 @@ Prerequisites
Kubernetes Version 1.19.0
~~~~~~~~~~~~~~~~~~~~~~~~~
.. important::
MinIO **strongly recommends** upgrading Production clusters running `End-Of-Life <https://kubernetes.io/releases/patch-releases/#non-active-branch-history>`__ Kubernetes APIs.
Starting with v4.0.0, the MinIO Operator and MinIO Kubernetes Plugin **require** Kubernetes 1.19.0 and later.
The Kubernetes infrastructure *and* the ``kubectl`` CLI tool must have the same version of 1.19.0+.
@ -155,52 +159,6 @@ The output of the example command above may differ from the output in your termi
Alternatively, you can generate x.509 TLS certificates signed by a known and trusted CA and pass those certificates to MinIO Tenants.
See :ref:`minio-tls` for more complete documentation.
Configure MinIO Operator to Trust Custom Certificates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you use custom certificates for your deployment, add the certificate so that MinIO Operator trusts it.
This procedure assumes you have an existing custom certificate.
1. Use the following command to generate a secret from the certificate:
.. code-block:: shell
:class: copyable
kubectl create secret generic MY-CUSTOM-TLS -n MY-CLUSTER-NAMESPACE --from-file=<path/to/public.crt>
Replace the following placeholders in the above command:
- ``MY-CUSTOM-TLS`` with the name of your secrets file
- ``MY-CLUSTER-NAMESPACE`` with your cluster's namespace
- ``<path/to/public.crt>`` with the relative path to the public certificate to use to create the secret
2. Add a volume to the yaml for your cluster under ``.spec.template.spec``
.. code-block:: yaml
:class: copyable
volumes:
- name: tls-certificates
projected:
defaultMode: 420
sources:
- secret:
items:
- key: public.crt
path: CAs/custom-public.crt
name: MY-CUSTOM-TLS
- replace ``MY-CUSTOM-TLS`` with the name of your secrets file.
3. Add a ``volumeMount`` to the yaml for your cluster under ``.spec.template.spec.container[0]``
.. code-block:: yaml
:class: copyable
volumeMounts:
- mountPath: /tmp/certs
name: tls-certificates
Procedure
---------