object: Add field in hosting to specify wildcard supported entries in DNSnames #14087
Labels
Comments
thotz
added a commit
to thotz/rook
that referenced
this issue
Apr 29, 2024
The users need to careful about port and ssl certs while consuming virtual host feature for rgw. Fixes: rook#14087 Signed-off-by: Jiffin Tony Thottan <thottanjiffin@gmail.com>
6 tasks
thotz
added a commit
to thotz/rook
that referenced
this issue
May 8, 2024
The users need to careful about port and ssl certs while consuming virtual host feature for rgw. Fixes: rook#14087 Signed-off-by: Jiffin Tony Thottan <thottanjiffin@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug report or feature request?
To support vhost style we introduce RGW support Rook mimic
rgw dns nameswithhosting.DNSnamefield in cephobjectstore CRD. But limitation is that it includes all the domains in which rgw server can be accessed. So Rook Op cannot identity which of them is wildcard support, can use those domains specifically for OBC config maps. To add that support better user need to convey which endpoint supports wildcards, so Rook can use those as the preferred way of accessing rgw serverWhat should the feature do:
Introduce new field
wildcard dns endpointsin the hosting sessionWhat is use case behind this feature:
Improves accuracy in the choosing the endpoint for rgw server
Environment:
The text was updated successfully, but these errors were encountered: