Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4645

OpenShift Ingress Controller should be able to pass user defined annotations to its service

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Network Edge
    • None
    • False
    • None
    • False
    • Not Selected

      It's very common for users to want to use load balancer features that are available to OpenShift via service annotations. Examples of which are setting a static ip [1], or enabling load balancer logging for compliance [2] or creating an allow-list of IPs that can access the LB [3].

      as ALBO support comes in to OpenShift these annotations will allow for some fairly complicated logic to do things like enable WAF / CloudFront.

      Proposal is that the operator would add a field in its CRDs for `serviceAnnotations: {}` that would be passed through to the service that is created for the ingress controller.

      [1] service.beta.kubernetes.io/aws-load-balancer-eip-allocations: eipalloc-xxxxxxxxxxxxxxxxx,eipalloc-yyyyyyyyyyyyyyyyy
      [2] service.beta.kubernetes.io/aws-load-balancer-access-log-enabled: true
      [3] service.beta.kubernetes.io/load-balancer-source-ranges

              mcurry@redhat.com Marc Curry
              pczarkow@redhat.com Paul Czarkowski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: