```

Cross check if the secret is created successfully using

```sh
kubectl get secrets
```

You should see a secret named `tls-ssl-minio`.

## 3. Update deployment yaml file

Whether you are planning to use Kubernetes StatefulSet or Kubernetes Deployment, the steps remain the same.

If you're using certificates provided by a CA, add the below section in your yaml file under `spec.volumes[]`

```yaml
    volumes:

# Развёртывание { #deployment }

Развернуть приложение **FastAPI** довольно просто.

## Что означает развёртывание { #what-does-deployment-mean }

Термин **развёртывание** (приложения) означает выполнение необходимых шагов, чтобы сделать приложение **доступным для пользователей**.

 * under the License.
 */
package org.apache.maven.api.services;

import org.apache.maven.api.annotations.Experimental;

/**
 * An artifact could not correctly being deployed.
 *
 * @since 4.0.0
 */
@Experimental
public class ArtifactDeployerException extends MavenException {

    /**
     * @param message the message of the error
     * @param e {@link Exception}
     */

            <exclude>**/Test*.java</exclude>
          </excludes>
        </configuration>
      </plugin>
    </plugins>
  </build>
  <distributionManagement>
    <status>deployed</status>
  </distributionManagement>

# The table name '$$ALL$$' means all tables are target.
# The table names and column names are treated as case insensitive.
#
# You don't need specify here about table classifications.
# Because table classifications are auto-deployed by relation information.
#
# Specification:
# map: {
#     [table-name or $$ALL$$] = map:{
#         ; [column-name (with hint)]=[classification-name]
#     }
# }
#

# Lasta Di properties, you can set container's options
# _/_/_/_/_/_/_/_/_/_/

# location of smart-deploy mode e.g. maihama_env.properties: lasta_di.smart.deploy.mode
#smart.deploy.mode.location = maihama_env.properties: lasta_di.smart.deploy.mode

# package for smart deploy target e.g. org.docksidestage.app
smart.package1 = org.codelibs.fess.crawler

<img src="/img/deployment/https/https01.drawio.svg">

### Начало TLS-рукопожатия { #tls-handshake-start }

Далее браузер будет общаться с этим IP‑адресом на **порту 443** (порт HTTPS).

Первая часть взаимодействия — установить соединение между клиентом и сервером и договориться о криптографических ключах и т.п.

<img src="/img/deployment/https/https02.drawio.svg">

<img src="/img/deployment/https/https05.drawio.svg">

### Resposta HTTP { #http-response }

A aplicação processaria a solicitação e retornaria uma resposta HTTP básica (não encriptada) para o Proxy de Terminação TLS.

<img src="/img/deployment/https/https06.drawio.svg">

### Resposta HTTPS { #https-response }

	"github.com/minio/cli"
)

var fmtGenFlags = []cli.Flag{
	cli.IntFlag{
		Name:  "parity",
		Usage: "specify erasure code parity",
	},
	cli.StringFlag{
		Name:  "deployment-id",
		Usage: "deployment-id of the MinIO cluster for which format.json is needed",
	},
	cli.StringFlag{
		Name:   "address",
		Value:  ":" + GlobalMinioDefaultPort,

    # If your source is the 'local' alias specified to 'mc batch start', then the 'endpoint' and 'credentials' fields are optional and can be omitted
    # Either the 'source' or 'remote' *must* be the "local" deployment
#    endpoint: "http://127.0.0.1:9000"
#    # path: "on|off|auto" # "on" enables path-style bucket lookup. "off" enables virtual host (DNS)-style bucket lookup. Defaults to "auto"
#    credentials: