Nick Young
Nick Young
This can't be done until we push out 1.17, so this is deliverable in the 1.18 timeframe.
I'd like to understand more about this - I would rather not tie the operator exclusively to a single management framework. How does OLM help solve migration and update problems?
Ah, I see. So OLM support is just about supplying the CSVs and other metadata about versions somehow?
I agree, setting status on the Contour object seems like the go here.
Thanks for this issue @jberger. It sounds like you want to be able to specify the `spec.loadBalancerIP` field? That seems like a reasonable knob to expose in Contour, with the...
The implementation caveat I need to give you is that we are the process of changing how Contour and the Operator fit together, so this may end up held up...
Moving to 1.17.
I moved this to 1.14, as I don't think we'll finish up the outstanding in time. Definitely need to devote some resources to it though.
I think in this case, that the securityContext of the Contour and Envoy pods should be configurable, maybe just with a single "userID" or similar setting.
For HTTPProxy, we literally copied the `status.loadBalancer` struct from Ingress and Service, which allows for both multiple IP addresses and multiple hostnames. Maybe it's better to just reuse that again...