Readiness Probe Warnings for API pods
## Summary
<!-- enter brief summary text here, 2-3 sentences -->
The readiness probes of the OpenStack API pods are throwing ProbeWarnings, despite that the probes are working as they should.
### Detailed Description
<!-- At least one comprehensible use case -->
Some OpenStack APIs are returning a Multiple Choice (300) on their index document.
The HTTP Probe logs a warning and terminates redirects if it receives a HTTP 300[1], the probe still succeeds however [2].
We do not see the issue for the Nova and Neutron API as they return a HTTP 200.
#### Result
<!-- what happened? -->
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ProbeWarning 8m8s (x53130 over 6d3h) kubelet Readiness probe warning: {"versions": {"values": [{"id": "v3.14", "status": "stable", "updated": "2020-04-07T00:00:00Z", "links": [{"rel": "self",
"href": "https://10.244.252.87:5001/v3/"}], "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}]}]}}
Warning ProbeWarning 3m8s (x53160 over 6d3h) kubelet Readiness probe warning: {"versions": {"values": [{"id": "v3.14", "status": "stable", "updated": "2020-04-07T00:00:00Z", "links": [{"rel": "self",
"href": "https://10.244.252.87:5000/v3/"}], "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}]}]}}
```
#### Expected Result
If the readiness probe is healthy, there shouldn't be any ProbeWarning events.
#### Additional Information
<!-- Configuration, data, software versions etc. which are involved. If possible, provide the git commit ID you are running off. -->
[1] https://github.com/kubernetes/kubernetes/blob/v1.23.17/pkg/probe/http/http.go#L136-L139
[2] https://github.com/kubernetes/kubernetes/blob/v1.23.17/pkg/kubelet/prober/prober.go#L126-L131
## Resolution
<!-- OPTIONAL section in case you have concrete ideas for a fix. If unused, delete this entire section -->
Change the probes of affected APIs to curl specific versions to avoid the Multiple Choice (300) code.
### Proposal
To be discussed.
<!-- Alternatively, you can add a full text or bullet-pointed proposal here for discussion -->
### Specification
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this issue are to be interpreted *in the spirit of* [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119), even though we're not technically doing protocol design.
<!-- Bullet-point list of MUST, SHOULD, MAY, SHOULD NOT and MUST NOT. will be added as a result of the proposal discussion process. -->
issue