mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
72 lines
2.5 KiB
Plaintext
72 lines
2.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_aws/installing-aws-network-customizations.adoc
|
|
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="nw-aws-nlb-new-cluster_{context}"]
|
|
= Configuring an Ingress Controller Network Load Balancer on a new AWS cluster
|
|
|
|
[role="_abstract"]
|
|
You can create an Ingress Controller backed by an {aws-full} Network Load Balancer (NLB) on a new cluster in situations where you need more transparent networking capabilities.
|
|
|
|
.Prerequisites
|
|
|
|
* Create and edit the `install-config.yaml` file. For instructions, see "Creating the installation configuration file" in the _Additonal resources_ section.
|
|
|
|
.Procedure
|
|
|
|
. Change to the directory that contains the installation program and create the manifests:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ./openshift-install create manifests --dir <installation_directory>
|
|
----
|
|
* 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:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ touch <installation_directory>/manifests/cluster-ingress-default-ingresscontroller.yaml
|
|
----
|
|
`<installation_directory>`:: Specifies the directory name that contains the `manifests/` directory for your cluster.
|
|
|
|
. Check the several network configuration files that exist in the `manifests/` directory by entering the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ls <installation_directory>/manifests/cluster-ingress-default-ingresscontroller.yaml
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
cluster-ingress-default-ingresscontroller.yaml
|
|
----
|
|
|
|
. Open the `cluster-ingress-default-ingresscontroller.yaml` file in an editor and enter a custom resource (CR) that describes the Operator configuration you want:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
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 because the installation program deletes the `manifests/` directory during cluster creation.
|