Skip to content

Add details to why the minio tenant headless service must be used over the normal clusterIP service #564

@AntonOfTheWoods

Description

@AntonOfTheWoods

"The console service is for managing the tenant, while the hl service exposes the S3 compatible API. "

the <tenant>-hl service is a headless service. There is also a minio "normal" (clusterIP) service created. Why can't we used the "normal" service? Does the plugin have to connect to all of the pods behind the service? I have been testing with a single pod and it works with the normal service (not the headless version) but that may just be because there is a single pod. Can you update the docs to say why it can't use the normal service, if indeed that is the case? Thanks!

EDIT: Furthermore, how does https://cloudnative-pg.io/plugin-barman-cloud/docs/retention/ ("The Barman Cloud Plugin supports automated cleanup of obsolete backups via retention policies, configured in the .spec.retentionPolicy field of the ObjectStore resource.") square with https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/#s3-lifecycle-policy ("Barman Cloud uploads backup files to S3 but does not modify or delete them afterward. ") ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions