minio-hl-svc has no ClusterIP about operator HOT 6 CLOSED

@nitisht ^^

from operator.

not really clear what the problem is @cons0l3 . minio-hl-service is a headless service created as a pre-requisite for StatefulSet

from operator.

Hi @nitisht,
oh, thanks. When working through the readme, my expectation was to have a running minio webfront-end and minio api endpoint (same when you work through the minio/readme). As the minio-hl-service (and now I know hl stands for headleass) has no webfront-end or adress api endpoint.

What is the suggested way of setting up a StatefulSet and should that be added to the readme?

from operator.

What is the suggested way of setting up a StatefulSet and should that be added to the readme?

Operator will create a statefulset, using given parameters in the sample yaml file. To access the MinIO statefulset you can create a separate service like this (https://github.com/minio/minio/blob/master/docs/orchestration/kubernetes/minio-distributed-service.yaml) - feel free to update the service type as per your requirements

from operator.

In the examples folder I have found a "minioinstance-with-external-service.yaml" which seems to be a not headless variant. In other words the "minioinstance.yaml" is the headless variant, where as the formentioned is not. A hint in the readme would be terrific, maybe with a little use case description for either variant. Two ways to set it up and enjoy ;-)
Thanks for your outstanding service and support.

from operator.

What is the suggested way of setting up a StatefulSet and should that be added to the readme?

Operator will create a statefulset, using given parameters in the sample yaml file. To access the MinIO statefulset you can create a separate service like this (https://github.com/minio/minio/blob/master/docs/orchestration/kubernetes/minio-distributed-service.yaml) - feel free to update the service type as per your requirements

it seems the reference link is broken here.

EDIT: found some example

---
apiVersion: v1
kind: Service
metadata:
  name: minio-buckets  # named this way for descriptive purpose loki chunks
spec:
  type: ClusterIP
  ports:
    - name: http-minio  # arbitrary name (chose minio default naming)
      port: 9000  # used for loki chunks bucket push
      targetPort: 9000
      protocol: TCP
  selector:
    v1.min.io/tenant: minio1   # name of tenant

TLDR doesnt help anyways... msg="error processing requests from scheduler" err="rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection termination" when using istio service mesh with minio it is impossible to connect to the minio object store.

from operator.