hello, we are already doing something similar, having multiple hostnames publicly using just one backend hostname. Since you are using haproxy, in your haproxy backend section you could enforce a single hostname by setting the header like this http-request set-header Host example.com i hope this helps you On Mon, Aug 16, 2021 at 9:53 AM Burkhard Linke < Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > > we are running RGW behind haproxy for TLS termination and load > balancing. Due to some major changes in our setup, we would like to > start a smooth transition to a new hostname of the S3 endpoint. The > haproxy part should be straightforward (adding a second frontend). > > > But on the RGW side it might be more complex. Let's assume that the > current DNS name is example.com, and I want to transition to > example.org. The example.com name is set as rgw_dns_name in the ceph > configuration for that rgw instance. It is also set as a single endpoint > in the active zone/zonegroup. > > > Is it sufficient to update the zonegroup setting and add a second > endpoint for example.org? User should be able to access their bucket as > bucket.example.org and bucket.example.com during the transition time. > > > Regards, > > Burkhard > > > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |