Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove hardcoded storage class to allow usage of the installed, default storage class resource, and not force the usage of the
standard
storage class which may not exist on a particular k8s deployment.The default storage class is automatically chosen by k8s on deployment of the minio tenant.
Test steps (using an lxc instance)
Note: The desired result is that basically the guide at https://github.com/minio/operator/tree/master/helm/operator or https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-minio-tenant-helm.html#deploy-tenant-helm should work out of the box with no failures.
Persist the session even after rebooting. This is needed only on lxc instances.
Install k3s. Print versions.
Output
Install helm
Install minio-operator. Print version.
Validate minio-operator running
Add http Nodeport to service
Get jwt and login e.g. http://operator-1605.minio.training:31000
Install tenant. Validate pods work. Note in this case the tenant was also edited to remove TLS for ease of testing
Add nodeport to access tenant
Using the default user/password, login e.g. http://operator-1605.minio.training:31090