docs/source/includes/k8s/file-transfer-protocol-k8s.rst at bfdb0c00d9b2955b29fe1aa439475ebf924cfe54

minio/docs

mirror of https://github.com/minio/docs.git synced 2025-12-07 08:22:13 +03:00

Files

Ravind Kumar 571f188a4e Attempting to reduce docs to single platform (#1258 )

##

We are going to make the following changes to the Object Store docs as
part of a larger QC/Content pass:

### Left Navigation

We want to modify the left navigation flow to be a natural progression
from a basic setup to more advanced.

For example:

- Core Concepts
  - Deployment Architecture
  - Availability and Resiliency
  - Erasure Coding and Object Healing
  - Object Scanner
  - Site Replication and Failover
  - Thresholds and Limits
- Installation
  - Deployment Checklist
  - Deploy MinIO on Kubernetes
  - Deploy MinIO on Red Hat Linux
  - Deploy MinIO on Ubuntu Linux
  - Deploy MinIO for Development (MacOS, Windows, Container)
- Security and Encryption (Conceptual Overview)
  - Network Encryption (TLS) (Conceptual overview)
    - Enable Network Encryption using Single Domain
    - Enable Network Encryption using Multiple Domains
    - Enable Network Encryption using certmanager (Kubernetes only)
  - Data Encryption (SSE) (Conceptual overview)
    - Enable SSE using AIStor Key Management Server
    - Enable SSE using KES (Summary page + linkouts)
  - External Identity Management (Conceptual Overview)
    - Enable External Identity management using OpenID
    - Enable External Identity management using AD/LDAP
- Backup and Recovery
  - Create a Multi-Site Replication Configuration
  - Recovery after Hardware Failure
    - Recover after drive failure
    - Recover after node failure
    - Recover after site failure
- Monitoring and Alerts
  - Metrics and Alerting (v3 reference)
    - Monitoring and Alerting using Prometheus
    - Monitoring and Alerting using InfluxDB
    - Monitoring and Alerting using Grafana
    - Metrics V2 Reference
  - Publish Server and Audit Logs to External Services
  - MinIO Healthcheck API

The Administration, Developer, and Reference sections will remain as-is
for now.

http://192.241.195.202:9000/staging/singleplat/mindocs/index.html

# Goals

Maintaining multiple platforms is getting to be too much, and based on
analytics the actual number of users taking advantage of it is minimal.

Furthermore, the majority of traffic is to installation pages.

Therefore we're going to try to collapse back into a single MinIO Object
Storage product, and use simple navigation and on-page selectors to
handle Baremetal vs Kubernetes.

This may also help to eventually stage us to migrate to Hugo + Markdown

---------

Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Rushan <rushenn@minio.io>
Co-authored-by: rushenn <rushenn123@gmail.com>

2025-07-30 12:33:02 -04:00

2.8 KiB

Raw Blame History

Enable SFTP for the desired Tenant:

Use the following Kubectl command to edit the Tenant YAML configuration:
```
kubectl edit tenants/my-tenant -n my-tenant-ns
```
Replace my-tenant and my-tenant-ns with the desired Tenant and namespace.
In the features: section, set the value of enableSFTP to true:
```
spec:
   configuration:
      name: my-tenant-env-configuration
   credsSecret:
      name: my-tenant-secret
   exposeServices:
      console: true
      minio: true
   features:
      enableSFTP: true
```
Kubectl restarts MinIO to apply the change.

You may also set enableSFTP in your Helm chart or Kustomize configuration to enable SFTP for newly created Tenants.
If needed, configure ingress for the SFTP port according to your local policies.
Validate the configuration

The following kubectl get command uses yq to display the value of enableSFTP, indicating whether SFTP is enabled:
```
kubectl get tenants/my-tenant -n my-tenant-ns -o yaml | yq '.spec.features'
```
Replace my-tenant and my-tenant-ns with the desired Tenant and namespace.

If SFTP is enabled, the output resembles the following:
```
enableSFTP: true
```
Use your preferred SFTP client to connect to the MinIO deployment. You must connect as a user whose policies <minio-policy> allow access to the desired buckets and objects.

The specifics of connecting to the MinIO deployment depend on your SFTP client. Refer to the documentation for your client.

The following example connects to the MinIO Tenant SFTP server forwarded to the local host system, and lists the contents of a bucket named runner.
```
> sftp -P 8022 minio@localhost
minio@localhost's password:
Connected to localhost.
sftp> ls runner/
chunkdocs  testdir
```

The following kubectl get command uses yq to display the value of enableSFTP, indicating whether SFTP is enabled:

kubectl get tenants/my-tenant -n my-tenant-ns -o yaml | yq '.spec.features'

Replace my-tenant and my-tenant-ns with the desired Tenant and namespace.

If SFTP is enabled, the output resembles the following:

enableSFTP: true

2.8 KiB Raw Blame History

2.8 KiB

Raw Blame History