Switching from AWS CLB to NLB for router-default about cluster-ingress-operator HOT 7 CLOSED

I am not an openshift developer, but I had the same need and after working with support I achieved it using

#! To apply this special file use:
#! oc replace --force -f - --wait --save-config
apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
  name: default
  namespace: openshift-ingress-operator
spec:
  replicas: 3
  defaultCertificate:
    name: router-certs
  endpointPublishingStrategy:
    loadBalancer:
      scope: Internal
      providerParameters:
        type: AWS
        aws:
          type: NLB
    type: LoadBalancerService

from cluster-ingress-operator.

@htkmts, as @kim0 mentions, support for AWS NLB's was added to the ingress operator in OCP 4.6.

Please see https://docs.openshift.com/container-platform/4.6/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.html

from cluster-ingress-operator.

/close

from cluster-ingress-operator.

@sgreene570: Closing this issue.

from cluster-ingress-operator.

But this doesnt allow the static IP addresses configuration for the NLBs. It just takes a ip allocated from the subnets assigned to the cluster. Can i know if we can custom config the static IP addresses for the NLB?

Also would love to see the customisation for below NLB config parameters:
Name
Subnets
Custom tags
Attributes
Static IP addresses

from cluster-ingress-operator.

I also have same requirement. Basically for whatever reason if i need to replace NLB I want to retain same IP ,this will help not to request firewall opening and all if NLB pickup some other random IP.If we see AWS documentation "you can optionally specify one private IP address per subnet." https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html

from cluster-ingress-operator.

Have also hit this. It seems as if https://github.com/openshift/cluster-ingress-operator/blob/master/pkg/operator/controller/ingress/load_balancer_service.go needs to be updated to pass annotations to the ingress controller's service:

• service.beta.kubernetes.io/aws-load-balancer-private-ipv4-addresses
• service.beta.kubernetes.io/aws-load-balancer-subnets annotations

or https://github.com/openshift/api/blob/54592eea55395af31e82fa9a605eb45523115454/operator/v1/types_ingress.go#L592-L595 needs to be updated to Deep Copy ELBv2 SubnetMappings into the resulting load balancer.

Probably the former.

See https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/ and https://docs.aws.amazon.com/sdk-for-go/api/service/elbv2/#SubnetMapping

from cluster-ingress-operator.