Adds section to the policy based access control page for supported KMS
action keys.
Refers two existing kms related keys to the preferred `kms:` keys.
Closes#1283
- removes `--logs` flag from `mc support callhome`
- enforces 100 bucket limit for v2 metrics
Closes#1439
Opportunistic fix to remove errant copy/paste for
`--noncurrent-expire-days` flag in `mc ilm rule add`
Closes#1438
This commit removes lengthy discussion of SUBNET from the community
docs. Other affected pages that linked to removed sections also updated.
Also reduces references to Call Home to the remaining mc support pages
and links to those pages.
Hidden env var `_MINIO_BATCH_REPLICATION_WORKERS` is being referred to
in documentation. It needs to be either:
- removed as a hidden variable
- renamed with a leading `_`
- enabled as a regular variable in ~`minio`~ and `eos`, without a
leading `_`
See example the files referred to in the PR and
39df134204/cmd/batch-handlers.go (L398)
Pending review and discussion with @harshavardhana and @poornas
This PR removes documentation references to this variable.
Only applicable for remote tiers that are also MinIO deployments.
Per internal discussion.
Need to verify if this applies to the `edit` command and the
`noncurrent-transition-days` flags.
MinIO uses RFC3339 data and time formatting and not ISO-8601. RFC3339
requires that there be a `T` as part of the data and time separation.
ISO-8601 allows a space.
The documentation also currently refers to using a date in the batch
framework; this should be a RFC3339 date and time.
e.g.
```
mc batch start play expire.yaml
mc: <ERROR> Unable to start job. We encountered an internal error, please try again.: cause(parsing time "2006-01-02 15:04:05.00Z" as "2006-01-02T15:04:05Z07:00": cannot parse " 15:04:05.00Z" as "T").
```
---------
Co-authored-by: Ravind Kumar <ravindk89@gmail.com>
#### Issue
Batch replication requires specific actions to be performable by the
source user, including:
```
"admin:ListBatchJobs",
"admin:DescribeBatchJob",
"admin:StartBatchJob",
"admin:CancelBatchJob"
```
This PR suggests them in the batch replication example provided in the
docs.
@poornas Please correct me if needed. This allowed the documentation to
be followed smoothly, with a resultant successful batch replication job
being spawned.
The page with the event type detail seemed an ok place to put this.
Suggestions for other/additional locations welcome.
Tested on AIStor + EOS with an outbound webhook to an external service.
Since I had a live example, I included it in the page as well.
Fixes https://github.com/minio/docs/issues/1394
# Summary
We removed support for deploying via OpenShift operatorhub / marketplace
a few months back. The burden of maintaining the certifications/process
required was sufficient to pull that feature set out moving forward and
migrate it to AIStor as part of a more complete enterprise offering.
For now we need to remove references to the operator hub / marketplace.
It is possible that the Openshift Kubernetes Engine may work w/ our
stock kubernetes installation paths, but we do not have resources to
test.
So for the immediate term, we're just going to pull whats outdated.
Also throwing in a fixup to the CRDs - I ran into a weird issue where I
had to `pip3 install asciidoc` before the sync-operator-crd-docs job
worked, am looking into that separately.
Staged:
http://192.241.195.202:9000/staging/openshift-fixup/openshift/index.html
Include files for quickstarts had a page title that resulted in a
duplicate H1. This removes the duplicate and moves the links for video
to the index.rst page.
Opportunity fix of an unrelated build error.
Closes#1408
Fixes#1404
Two sets of fixes:
- add conditionals for windows and linux where shared
- search/replace for linux only (MinIO Server reference pages)
Staging server not available, tested/checked locally
Add a clearer callout to `mc` for features not/no longer available in
MinIO Console.
Given that several things were removed, enumerating specific commands
seems impractical? Opinions solicited.
From a community issue: https://github.com/minio/console/issues/3498
Not yet staged.
---------
Co-authored-by: Ravind Kumar <ravind@min.io>
SUBNET no longer supports the uploading of logs.
The flags still exist in the MinIO Client, but no longer function.
Opportunistic fix to clarify that s3v4 is a signature type, not an API.
No issue to link.
## Tenant Namespaces
Adds information for unique tenant namespaces.
Closes#1391
## Changing erasure code parity
Adds information about changes to erasure code to MNMD deploys.
Closes#1365
- Adds missing config settings throughout storage class page.
Closes#1349
- Adds instructions for adding certificates for connecting by sftp.
Closes#1354
- Corrects information about which key to use for self-signed CAs.
Closes#1358
- Moves `context` to optional for batch key rotate jobs.
Closes#1356
- clean up missing ref links causing build warnings.
