$ oc get infrastructure/cluster -o jsonpath='{.status.platformStatus.type}'
AWS
OpenShift Container Platform provides methods for communicating from outside the cluster with services running in the cluster. This method uses a Network Load Balancer (NLB), which forwards the client’s IP address to the node. You can configure an NLB on a new or existing AWS cluster.
You can create an Ingress Controller backed by an AWS Network Load Balancer (NLB) on an existing cluster.
You must have an installed AWS cluster.
PlatformStatus
of the infrastructure resource must be AWS.
To verify that the PlatformStatus
is AWS, run:
$ oc get infrastructure/cluster -o jsonpath='{.status.platformStatus.type}'
AWS
Create an Ingress Controller backed by an AWS NLB on an existing cluster.
Create the Ingress Controller manifest:
$ cat ingresscontroller-aws-nlb.yaml
apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
name: $my_ingress_controller(1)
namespace: openshift-ingress-operator
spec:
domain: $my_unique_ingress_domain(2)
endpointPublishingStrategy:
type: LoadBalancerService
loadBalancer:
scope: External(3)
providerParameters:
type: AWS
aws:
type: NLB
1 | Replace $my_ingress_controller with a unique name for the Ingress Controller. |
2 | Replace $my_unique_ingress_domain with a domain name that is unique among all Ingress Controllers in the cluster. |
3 | You can replace External with Internal to use an internal NLB. |
Create the resource in the cluster:
$ oc create -f ingresscontroller-aws-nlb.yaml
Before you can configure an Ingress Controller NLB on a new AWS cluster, you must complete the Creating the installation configuration file procedure. |
You can create an Ingress Controller backed by an AWS Network Load Balancer (NLB) on a new cluster.
Create the install-config.yaml
file and complete any modifications to it.
Create an Ingress Controller backed by an AWS NLB on a new cluster.
Change to the directory that contains the installation program and create the manifests:
$ ./openshift-install create manifests --dir=<installation_directory> (1)
1 | For <installation_directory> , specify the name of the directory that
contains the install-config.yaml file for your cluster. |
Create a file that is named cluster-ingress-default-ingresscontroller.yaml
in the <installation_directory>/manifests/
directory:
$ touch <installation_directory>/manifests/cluster-ingress-default-ingresscontroller.yaml (1)
1 | For <installation_directory> , specify the directory name that contains the
manifests/ directory for your cluster. |
After creating the file, several network configuration files are in the
manifests/
directory, as shown:
$ ls <installation_directory>/manifests/cluster-ingress-default-ingresscontroller.yaml
cluster-ingress-default-ingresscontroller.yaml
Open the cluster-ingress-default-ingresscontroller.yaml
file in an editor and enter a CR that describes the Operator configuration you want:
apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
creationTimestamp: null
name: default
namespace: openshift-ingress-operator
spec:
endpointPublishingStrategy:
loadBalancer:
scope: External
providerParameters:
type: AWS
aws:
type: NLB
type: LoadBalancerService
Save the cluster-ingress-default-ingresscontroller.yaml
file and quit the text editor.
Optional: Back up the manifests/cluster-ingress-default-ingresscontroller.yaml
file. The installation program deletes the manifests/
directory when creating the cluster.
For more information, see Network Load Balancer support on AWS.