You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Harshavardhana 4a4048fe27 Migrate minio etcd config to backend config (#7751) ... etcd when used in federated setups, currently mandates that all clusters should have same config.json, which is too restrictive and makes federation a restrictive environment. This change makes it apparent that each cluster needs to be independently managed if necessary from `mc admin info` command line. Each cluster with in federation can have their own root credentials and as well as separate regions. This way buckets get further restrictions and allows for root creds to be not common across clusters/data centers. Existing data in etcd gets migrated to backend on each clusters, upon start. Once done users can change their config entries independently.		5 years ago
..
bigdata	…
bucket/notifications	…
chroot	…
compression	…
config	…
deployment/kernel-tuning	…
disk-caching	…
distributed	doc: Merge large bucket with distributed docs (#7761)	5 years ago
docker	Add support for customizable user (#7569)	5 years ago
erasure	…
federation/lookup	Migrate minio etcd config to backend config (#7751)	5 years ago
gateway	…
kms	…
logging	…
metrics	…
multi-tenancy	…
multi-user	…
orchestration	Update yaml files to latest version RELEASE.2019-06-13T01-41-13Z	5 years ago
screenshots	doc: Merge large bucket with distributed docs (#7761)	5 years ago
security	…
select	…
shared-backend	…
sts	Fix OPA result response handling (#7763)	5 years ago
tls	…
zh_CN	…
minio-limits.md	…