mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
18 lines
1.4 KiB
Plaintext
18 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="nw-aws-load-balancer-operator-considerations_{context}"]
|
|
= AWS Load Balancer Operator considerations
|
|
|
|
[role="_abstract"]
|
|
To ensure a successful deployment, review the limitations of the AWS Load Balancer Operator. Understanding these constraints helps avoid compatibility issues and ensures the Operator meets your architectural requirements before installation.
|
|
|
|
Review the following limitations before installing and using the AWS Load Balancer Operator:
|
|
|
|
* The IP traffic mode only works on AWS Elastic Kubernetes Service (EKS). The AWS Load Balancer Operator disables the IP traffic mode for the AWS Load Balancer Controller. As a result of disabling the IP traffic mode, the AWS Load Balancer Controller cannot use the pod readiness gate.
|
|
|
|
* The AWS Load Balancer Operator adds command-line flags such as `--disable-ingress-class-annotation` and `--disable-ingress-group-name-annotation` to the AWS Load Balancer Controller. Therefore, the AWS Load Balancer Operator does not allow using the `kubernetes.io/ingress.class` and `alb.ingress.kubernetes.io/group.name` annotations in the `Ingress` resource.
|
|
|
|
* The AWS Load Balancer Operator requires that the service type is `NodePort` and not `LoadBalancer` or `ClusterIP`.
|