You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An undocumented consequence of PR #3414 is that users are not allowed to use a bucket name that matches the first subdomain on an s3 endpoint.
To Reproduce
I am using Ceph RGW to create an S3-compatible object gateway at mimir.rgw.jlh.name and a bucket named mimir. This bucket can be accessed at mimir.mimir.rgw.jlh.name or mimir.rgw.jlh.name/mimir. I use multiple RGW gateway, as different buckets may have different Ceph storage pool requirements. (e.g. ssd vs hdd)
I have configured mimir to use this bucket, but Mimir crashes with the error "error validating config: invalid rulestore config: the endpoint must not prefixed with the bucket name".
This check breaks an otherwise valid configuration, which can be a minor annoyance for users. Perhaps it should should be removed or documentation should be added.
Environment
Infrastructure: Kubernetes
Deployment tool: mimir-distributed helm
The text was updated successfully, but these errors were encountered:
Describe the bug
An undocumented consequence of PR #3414 is that users are not allowed to use a bucket name that matches the first subdomain on an s3 endpoint.
To Reproduce
I am using Ceph RGW to create an S3-compatible object gateway at
mimir.rgw.jlh.name
and a bucket namedmimir
. This bucket can be accessed atmimir.mimir.rgw.jlh.name
ormimir.rgw.jlh.name/mimir
. I use multiple RGW gateway, as different buckets may have different Ceph storage pool requirements. (e.g. ssd vs hdd)I have configured mimir to use this bucket, but Mimir crashes with the error "error validating config: invalid rulestore config: the endpoint must not prefixed with the bucket name".
Expected behavior
This check breaks an otherwise valid configuration, which can be a minor annoyance for users. Perhaps it should should be removed or documentation should be added.
Environment
The text was updated successfully, but these errors were encountered: