Integration for RGW host style bucket domains

[jpds]

Is this a bug report or feature request?

• Feature Request

Feature Request

Are there any similar features already existing: No

What should the feature do: AWS has a concept of a "host style bucket" domains, where clients can be configured to go to:

host_bucket = %(bucket)s.s3.amazonaws.com

• https://github.com/aws/aws-sdk-go/blob/master/service/s3/host_style_bucket.go

Rook could potential implement this with the help of a wildcard DNS entry which goes to a nginx/other ingress:

https://www.hastexo.com/resources/hints-and-kinks/configuring-radosgw-behave-amazon-s3/

It would seem that the RGW just needs to have a way of setting:

rgw dns name = domain.name

What would be solved through this feature: Some S3 clients expect this integration.

Does this have an impact on existing features: N/A.

[jpds]

Seems Kubernetes does not support wildcard ingress definitions (kubernetes/kubernetes#41881). For now, I'd be happy to have separate ingress definitions per bucket name which point to the same RGW instance (while using wildcard DNS).

[jpds]

I came across this while trying to find a fix for the issue I have in hashicorp/vault#3728 .

[jpds]

Potentially already implemented:

rook/pkg/daemon/ceph/rgw/daemon.go

Line 89 in 9678d80

"rgw dns name": config.Host,

Prehaps Host needs to be added to the YAML/documentation?

[travisn]

agreed, it seems we need to expose the dns name to the object.yaml.

[travisn]

Right now the rgw dns name is set to the name of the rgw service. The side effect of this is that the hostname in the URL of s3 client requests must match that name. For now, setting the default to be blank is the right thing until it's more clear how to use the bucket names with the wildcard.

@jpds do you have any more insight into how we can configure k8s to get this to work?

[travisn]

@jpds please reactivate if #1437 was not sufficient