@@ -5,6 +5,52 @@ Openshift's ingress operator gives us very little flexibility for configuration
One issue in particular made it necessary to fork the upstream component and add our own modifications: the ability to modify Loadbalancer services created by the operator (we need to set specific annotations for Openstack) and the ability to selectively enable the PROXY protocol for specific router shards.
Details can be found in [okd4-install!703](https://gitlab.cern.ch/paas-tools/okd4-install/-/merge_requests/703).
In particular, the following IngressController configuration:
```yaml
apiVersion:operator.openshift.io/v1
kind:IngressController
metadata:
name:apps-lb-1
annotations:
okd.cern.ch/service-annotations:|
{
"annotation1": "value1",
"annotation2": "value2"
}
okd.cern.ch/service-labels:|
{
"label1": "value1"
}
spec:
endpointPublishingStrategy:
type:LoadBalancerService
# [...]
```
will result in the creation of this Service resource:
**Note**: this behavior is only implemented for `LoadBalancerService` ingresscontrollers, but not `HostNetwork` ICs.
The Gitlab repository is configured to automatically mirror the [upstream cluster-ingress-operator repository](https://github.com/openshift/cluster-ingress-operator).
Use the following workflow to port our custom patches to a new release: