A customer has requested the ability to create hostAliases in order to be able to override the DNS at pod level.
They currently manually update the /etc/hosts file on each apicast instance and would like an option that will persist between pod deployments.

We do have a Openshift cluster dns that routs traffic to our internal corp network. This internal network has secureauth authentication servers with internal facing endpoints.
However our 3scale APICAST pod needs to route to an internet facing endpoint of the same authentication server that is also routable on the internal corp network for authentication token introspection for one of our internet facing customer portals.
If we don't use the hostAliases entry with the internet facing endpoint of the secureauth server, by default the traffic gets routed by the dns entry to the internal corp endpoint and the token introspection in this case is not valid.

Since our cluster has many workloads and multiple apicast instances changing the dns resolver is not an option.
Another problem we have is the dns name of the internal authentication server needed for internal apps is the same so by default if we change the dns resolver it would impact all the other internal apps needing authentication on the cluster.