Open
Conversation
Author
|
Author
|
New feature self-test log |
|
Do you have the minio service configured to forward and load balancer to your pods? This should expose the service which other pods can use. The instructions are in the production setup documentation and not included in the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
"Hello @vitalif, I've found that when MinIO and CSI are in the same cluster, and there's no external domain name, using systemd's GeeseFS prevents the connection through Kubernetes' service-ClusterIP. In the case of using systemd, a connection to the NodePort of the MinIO-service is mandatory.
Based on the above description, I've made some code modifications. I would appreciate it if you could review them."