How to create additional ingress on ROSA 4.14

Resolution

Important: Additional ingresscontrollers are considered customer workloads and must not run on infra node, as stated in the ROSA service definition page. Please, ensure the nodePlacement in the ingresscontroller definition is configured to run on worker nodes as shown below.

From ROSA , customer can using below document to create a new ingress
ingress-sharding

• Create a IngressController yaml and apply it

apiVersion: v1
items:
- apiVersion: operator.openshift.io/v1
  kind: IngressController
  metadata:
    name: sharded
    namespace: openshift-ingress-operator
  spec:
    domain: apps-sharded.basedomain.example.net
    nodePlacement:
      nodeSelector:
        matchLabels:
          node-role.kubernetes.io/worker: ""
    routeSelector:
      matchLabels:
        type: sharded
  status: {}
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

• check if the new ingress been created

$ oc --namespace openshift-ingress-operator get ingresscontrollers
NAME      AGE
default   47m
sharded   14m

$ oc get svc -n openshift-ingress
NAME                      TYPE           CLUSTER-IP       EXTERNAL-IP                                                                          PORT(S)                      AGE
router-default            LoadBalancer   172.30.28.52     xxxxxxxxxxxxxxxxxx-xxxxxxxxxxxx.elb.ap-northeast-1.amazonaws.com   80:30197/TCP,443:30685/TCP   39m
router-internal-default   ClusterIP      172.30.143.239   <none>                                                                               80/TCP,443/TCP,1936/TCP      39m
router-internal-sharded   ClusterIP      172.30.194.19    <none>                                                                               80/TCP,443/TCP,1936/TCP      7m10s
router-sharded            LoadBalancer   172.30.109.251   yyyyyyyyyyyyyyyyyy-yyyyyyyyyyyy.elb.ap-northeast-1.amazonaws.com   80:32462/TCP,443:31101/TCP   7m10s