3 Commits

Include renames

Author	SHA1	Message	Date
Josh Soref	6e7b8767f3	core: fix spelling ... * another * are * availability * available * bootstrap * boundaries * ceph * certificate * class * codifies * consuming * corrupted * createor * csi * deployments * exceeded * execute * filesystem * healthiness * heuristics * immediately * insecure * installed * isolated * maintained * maximum * minute * monitor * new * nginx * nonexistent * not * occurs * omitempty * operator * orchestration * persistentvolumes * placement * preexisting * prometheus * protecting * provisioner * purposes * reconcile * regex * related * requests * returns * rubbish * running * schedulable * schedule * serviceaccount * simulating * snapshots * statement * static * tenants * the * unavailable * volumeattachment * waiting * with * wrapper * zonegroup Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>	2022-07-07 18:10:47 -04:00
Jiffin Tony Thottan	fc2b8012c6	object: use us-east-1 for aws go lang sdk ... The aws go lang sdk needs value for region, it is set differently in various part of current code. With PR the value is always `us-east-1` so that it will work RGW server without any issues. This reverts commit 280c29f330. Signed-off-by: Jiffin Tony Thottan <thottanjiffin@gmail.com>	2022-03-24 14:37:39 +05:30
Sébastien Han	cda5dad291	rgw: use insecure TLS for bucket health check ... We have seen cases where the signed certificate used for the RGW does not contain the internal DNS endpoint, resulting in the health check to fail since the certificate is not valid for this domain. People consuming the gateways by external clients and for specific domains do not necessarily have the internal DNS configured in the certificate. So let's be a bit more flexible and simply ensure a connectivity check and bypass the certificate validation. Also, this is fixing the tls code in newS3Agent and adds unit tests. Closes: #8663 Signed-off-by: Sébastien Han <seb@redhat.com>	2021-09-28 14:48:07 +02:00