48d2c03250
Update yaml files to latest version RELEASE.2020-09-17T04-49-20Z
4 years ago
b2536476c9
Update yaml files to latest version RELEASE.2020-09-16T04-22-35Z
4 years ago
9d95937018
update KMS docs indicating deprecation of AUTO_ENCRYPTION env
4 years ago
eb3ded420e
Update yaml files to latest version RELEASE.2020-09-10T22-02-45Z
4 years ago
a966ccd17d
Support nginx LB with docker-compose example ( #10434 )
4 years ago
1dce6918c2
fix sysctl.sh quotes which are incompatible with sysctl ( #10446 )
4 years ago
6019628f7d
Update yaml files to latest version RELEASE.2020-09-08T23-05-18Z
4 years ago
a694ba93d9
update kernel tuning zh_CN document ( #10433 )
4 years ago
a9aaea0d67
Update yaml files to latest version RELEASE.2020-09-05T07-14-49Z
4 years ago
746f1585eb
add debugging zh_CN document. ( #10401 )
4 years ago
b4e3956e69
update KES docs to talk about 'mc encrypt' command ( #10400 )
...
add a deprecation notice for KMS_AUTO_ENCRYPTION
4 years ago
c51229493b
azure docs remove default chunk size example ( #10406 )
4 years ago
650dccfa9e
cache: Only start at high watermark ( #10403 )
...
Currently, cache purges are triggered as soon as the low watermark is exceeded.
To reduce IO this should only be done when reaching the high watermark.
This simplifies checks and reduces all calls for a GC to go through
`dcache.diskSpaceAvailable(size)`. While a comment claims that
`dcache.triggerGC <- struct{}{}` was non-blocking I don't see how
that was possible. Instead, we add a 1 size to the queue channel
and use channel semantics to avoid blocking when a GC has
already been requested.
`bytesToClear` now takes the high watermark into account to it will
not request any bytes to be cleared until that is reached.
4 years ago
d08b4b147d
Update yaml files to latest version RELEASE.2020-09-02T18-19-50Z
4 years ago
4b6585d249
support 'ldap:user' variable replacement properly ( #10391 )
...
also update `ldap.go` examples with latest
minio-go changes
Fixes #10367
4 years ago
cb61e50b51
since its an internal RPC API we do not need to document it. ( #10382 )
4 years ago
cd380251b3
Support custom paths for secret files in docker-entrypoint.sh ( #10344 )
4 years ago
92cd1eed45
Clarify zone example ( #10374 )
4 years ago
db32a24cb6
update kernel tuning docs to indicate sane values
4 years ago
73a6b4ea11
fix typo in replication docs ( #10366 )
4 years ago
c1b88c17cc
Update yaml files to latest version RELEASE.2020-08-27T05-16-20Z
4 years ago
5a974fb10c
Update yaml files to latest version RELEASE.2020-08-26T00-00-49Z
4 years ago
7d50a0cfea
Update yaml files to latest version RELEASE.2020-08-25T00-21-20Z
4 years ago
2a8e40f19f
add chroot zh_CN document ( #10337 )
4 years ago
21e8440423
add compression zh_CN document ( #10330 )
4 years ago
d0c910a6f3
Support https and basic-auth for elasticsearch notification target ( #10332 )
4 years ago
0ff246653b
CN bucket policy document that is no longer needed can be removed, ( #10310 )
...
which is consistent with the English document.
4 years ago
113bcbdb78
update minio limit zh_CN document ( #10320 )
4 years ago
331c517a5b
translate bucket versioning design document to zh_CN ( #10300 )
4 years ago
2eb5f934d8
add bucket versioning zh_CN document ( #10281 )
4 years ago
b43d376a87
Update yaml files to latest version RELEASE.2020-08-18T19-41-00Z
4 years ago
adca28801d
feat: disable Parquet by default (breaking change) ( #9920 )
...
I have built a fuzz test and it crashes heavily in seconds and will OOM shortly after.
It seems like supporting Parquet is basically a completely open way to crash the
server if you can upload a file and run s3 select on it.
Until Parquet is more hardened it is DISABLED by default since hostile
crafted input can easily crash the server.
If you are in a controlled environment where it is safe to assume no hostile
content can be uploaded to your cluster you can safely enable Parquet.
To enable Parquet set the environment variable `MINIO_API_SELECT_PARQUET=on`
while starting the MinIO server.
Furthermore, we guard parquet by recover functions.
4 years ago
ede86845e5
docs: Add policy variables for resource and conditions ( #10278 )
...
Bonus fix adds LDAP policy variable and clarifies the
usage of policy variables for temporary credentials.
fixes #10197
4 years ago
670724184c
Update yaml files to latest version RELEASE.2020-08-16T18-39-38Z
4 years ago
01a2ccc52f
add bucket retention zh_CN document ( #10264 )
4 years ago
1c865dd119
Update yaml files to latest version RELEASE.2020-08-13T02-39-50Z
4 years ago
6914b2c99d
Add bucket replication zh_CN document ( #10243 )
4 years ago
b4b7a18497
add bucket quota zh_CN document ( #10232 )
4 years ago
a49e3647b6
add bucket lifecycle zh_CN document ( #10231 )
4 years ago
954e17c3d0
Update yaml files to latest version RELEASE.2020-08-08T04-50-06Z
4 years ago
8049184dcc
fix: documentation changes in replication docs ( #10209 )
4 years ago
19c4f3082b
update and improve bucket notifications zh_CN document ( #10224 )
4 years ago
6d64aab420
Update yaml files to latest version RELEASE.2020-08-07T01-23-07Z
4 years ago
adcaa6f9de
fix: Change ListBucketTargets handler ( #10217 )
...
to list all targets across a tenant.
Also fixing some validations.
4 years ago
ce129efa09
update and improve config,throttle zh_CN document ( #10214 )
4 years ago
121164db56
fix: relax some replication validations ( #10210 )
...
Also inherit storage class from source object
if replication configuration does not have a storage
class specified for destination bucket.
4 years ago
195f95196e
Update yaml files to latest version RELEASE.2020-08-05T21-34-13Z
4 years ago
3acc0ebb81
fix: Change service name in Arn for replication ( #10205 )
4 years ago
1cdaced8b6
Update yaml files to latest version RELEASE.2020-08-04T23-10-51Z
4 years ago
d90ab904e7
fix: multi-tenant deployment guide to use ellipses format ( #10192 )
4 years ago
Minio Trusted