Hi [~weil],
The example sent for you regards the ingress[1] shows be a test and not the implementation that will create the resource to expose the service. Also, shows that it is not used because I could not find any part of the Prometheus code calling this func.
Following some notes:
* Also, shows that this is just used to test the operator and not to expose the service on it.
* Shows that prometheus is using the host as we are doing. See [here|https://github.com/linzhuangrong/prometheus-operator/blob/9874ab3427f7395b57b1fd696f24ca52ff928f55/helm/alertmanager/templates/ingress.yaml#L24] and asking for setup the host see [here|https://github.com/linzhuangrong/prometheus-operator/blob/9874ab3427f7395b57b1fd696f24ca52ff928f55/helm/grafana/README.md#L47]
* Prometheus shows expose the services by shell too. See [here|https://github.com/linzhuangrong/prometheus-operator/blob/9874ab3427f7395b57b1fd696f24ca52ff928f55/helm/grafana/templates/NOTES.txt#L11]
* Shows that Integr8ly is informing the host as we are doing here. See [here|https://github.com/integr8ly/gitea-operator/blob/9b58cafe5e57b28606fafb569fbd0b2928021af2/templates/gitea-ingress.yaml#L10] and [here|https://github.com/integr8ly/gitea-operator/blob/9b58cafe5e57b28606fafb569fbd0b2928021af2/templates/gitea-config.yaml#L31]
Please, let me know if you be able to find any project/example where the route in OCP is created by the ingress without informing the IP HOST . I will be working on it and I will try to find a way to move in this way. Thank you for your collab and support.
[1] - https://github.com/coreos/prometheus-operator/blob/c8eb45194a9115f37b64f3a3084c34dee4f8972f/test/framework/ingress.go#L32 |
|
