Corrects docs to state that when expanding a site replication peer set,
you must list all existing peers.
Closes#1340
Adds information that when adding Distinguished Names as search
parameters, multiple DNs must be separated with a semi-colon.
Closes#1341
Closes#1291
Missed a few log lines referencing Operator Console.
Also cleaning up some broken refs and further simplifying references to
the Console when in context of Tenant/MinIO Object Store.
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Addresses #1273
# Summary
This pass does three things:
1. Updates all tutorials related to Operator/Tenant deployment for
Kustomize and Helm
2. Removes references to Operator Console + updates to reference
Kustomize/Helm wherever possible
3. Slightly tidies up old or dangling references
This pass does not do these things:
- Link out heavily to Kubernetes docs (for later)
- Clean up organization (singleplat build handles this)
- Addresses OpenShift, Rancher, etc.
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Allan Roger Reid <allanrogerreid@gmail.com>
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Fix build warnings from https://github.com/minio/docs/pull/1219
Some are broken refs that need to point elsewhere.
Some are because `openshift`, `eks`, `gke`, `aks` can't see a target
that's on a `k8s` page, apparently due to how
`operations/installation.rst` is structured. These we are still
investigating.
Updates for MinIO Server RELEASE.2024-05-10T01-41-38Z
- Removes references to `MINIO_SERVER_URL` envvar.
- Updates KMS and KES related envvar settings to add KMS as an option.
- Also differentiates KMS and KES related envvar into three groups,
which are mutually exclusive.
Closes#1214
By request, for readability and also apparently it will then work on
other platforms too.
---------
Co-authored-by: Ramon de Klein <mail@ramondeklein.nl>
Partially addresses #1190
No staged build unless someone requests it.
# Summary
After some thinking, we've leaned towards just making a note of the
upgrade step and calling it done. We do not typically make extended
discussion of backward-breaking changes at this time, and have no where
to keep that sort of guidance.
Maybe in the future or as part of a larger re-arch we can consider where
we would best keep that kind of guidance.
As far as the rest:
- We are not covering s3zip today, so that's a no-op. We should leave
the ticket open in the event we have bandwidth to document the feature
later
- No changes to Console that need documentation at this time
- Added a quick callout on the warning behavior to the Versioning page
- Metrics v3 is also still In progress, come back to this once the
project is fully baked.
Admonition added as an include, then put in many files throughout the
docs.
Where it is included, it's the same admonition and text.
It's worth making sure where I placed the include makes sense.
Closes#1186
Updates for server RELEASE.2024-03-30T09-41-56Z
- Adds information that SSE-C encrypted objects can now replicate.
Closes#1177
- Adds information on operator renewal of tenant certificates
Closes#1167
- Corrects a description for `ilm restore` function
Closes#1175
Updates for Console release 0.45.0
- Removes healing references
- Updates headings and subheadings for the current Console UI
Closes#1107
MinIO SERVER RELEASE.2024-01-05T22-17-24Z - added new metrics to
github.com/minio/minio for later sync
MinIO SERVER RELEASE.2024-01-28T22-35-53Z - MinIO preallocates memory,
mc update compresses binary in transit MinIO SERVER
RELEASE.2024-02-06T21-36-22Z -
MinIO adds condition key for restricting STS AssumeRoleWithWebIdentity
duration at policy level
Closes#1124 ,
Partially addresses #1116
Partially Addresses #1105
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Internal request to split the Operator and Tenant helm chart into
separate pages.
This adds a replacement link in default-conf to automate updating the
operator version in the URL.
No related issue here, just freewheeling from an internal request.
This started with the request to change our recommendation around
label/uuid-based drive mounting to a requirement.
Looking at the pages I feel like our pre-req and considerations are a
little long in the tooth, and are at least slightly duplicative of what
is on the checklist pages (hardware, software)
This is at least a first swing at tidying things up. I think in a second
pass I'll move more of the pre-reqs into the Hardware/Software/Security
checklist pages, and keep the on-tutorial sections as simple defnlists
so that the page flows more easily. We can push users to the details if
they want it while keeping the high level requirements there.
Noting this does **not** yet address the new features related to
non-sequential hostname support. That has to come later.
---------
Co-authored-by: Eco <41090896+eco-minio@users.noreply.github.com>
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
…cript for xfs settings to Linux"
Closes#1084
Accomplishing a few things here:
1. General tidy-up of the installation pages so Windows/Container/MacOS
only display the appropriate deployment topos
2. Better admonitions/guidance on when to use what distribution
3. Added a section on Storage + XFS Settings to resolve an ongoing
customer request
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Installing the latest minio operator helm chart sets the console port to
9090 not 9001. I fixed the port in the port-forward command.
```
k get svc -n minio-operator
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
console ClusterIP 10.97.140.40 <none> 9090/TCP,9443/TCP 21m
operator ClusterIP 10.106.20.115 <none> 4221/TCP 21m
sts ClusterIP 10.106.182.83 <none> 4223/TCP 21m
```
We're getting a lot of repeated requests during
inbounds on sizing VMs specifically.
Our baremetal and K8s checklists are slightly generic to this and imply
a baseline that may be uncommon within a virtualized context
This attempts to bring together a slightly wider band while emphasizing
that our high-watermark is intended for high performance, while the low
watermark is a bare minimum.
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Important @ravindk89 : the installation of the tenant will end up with
CrashLooping pods unless a Standard storageclass is previously installed
- similar to the following. Please document this where best you see fit.
```
cat <<EOF | kubectl apply -f -
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: standard
provisioner: rancher.io/local-path
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
EOF
Closes#1021Closes#1055Closes#968Closes#943
---------
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Pedro Juarez <pjuarezd@users.noreply.github.com>
- Adds additional flag for `mc admin trace`
- Adds info about supported secret types for k8s
Closes#1039
For the `mc admin trace --stats` flag, also adding example output.
Closes#1045
Operator upgrade docs for 4.2.3 to 4.5.8 had an incorrect sentence
saying the procedure could upgrade directly to latest stable.
This updates the description to clarify that upgrade should first
upgrade to 4.5.8.
This was noted by a community Slack user.
mc RELEASE.2023-07-18T21-05-38Z
- Replaces mc replicate diff with mc replicate backlog
- Adds mc support top net
mc RELEASE.2023-07-07T05-25-51Z
- Adds mc support perf site-replication
- Deprecates mc admin replicate --sync flag in favor of new mc admihn
replicate --mode flag
- Updates output example of mc admin user info to show authentication
info
Partially addresses #930
- Adds information about 3 attempts at site or bucket replication tasks
- Adds note about additional info for delete markers
- Updates mc admin info command example output
Partially addresses #931 .
Not staged, but can do if needed.
### Objective:
To rephrase the Operator Support accordingly for single node single
drive configurations.
---------
Co-authored-by: Ravind Kumar <ravindk89@gmail.com>
