Open
Conversation
|
@dfitzmau: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
dfitzmau
commented
Apr 2, 2026
| = Adding TLS termination on the AWS Load Balancer | ||
|
|
||
| [role="_abstract"] | ||
| To secure traffic for your domain, configure TLS termination on the AWS Load Balancer. This setup routes traffic to the pods of a service while ensuring that encrypted connections are decrypted at the load balancer level. |
Contributor
Author
There was a problem hiding this comment.
| = Prepare to install the AWS Load Balancer Operator | ||
|
|
||
| [role="_abstract"] | ||
| To prepare your cluster for the AWS Load Balancer Operator, verify that your AWS VPC resources are tagged correctly and meet all requirements. You can also configure environment variables to customize the installation. |
Contributor
Author
There was a problem hiding this comment.
| = Set up temporary environment variables | ||
|
|
||
| [role="_abstract"] | ||
| To streamline the installation of the AWS Load Balancer Operator, define temporary environment variables for resource identifiers and configuration details. This optional configuration simplifies the execution of installation commands by storing reusable values. |
Contributor
Author
There was a problem hiding this comment.
| = Deploying the AWS Load Balancer Operator | ||
|
|
||
| [role="_abstract"] | ||
| After you deploy the The AWS Load Balancer Operator, the Operator automatically tags public subnets if the `kubernetes.io/role/elb` tag is missing. The Operator then identifies specific network resources in the underlying AWS cloud to ensure successful cluster integration. |
Contributor
Author
There was a problem hiding this comment.
| = Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost | ||
|
|
||
| [role="_abstract"] | ||
| To provision an AWS Application Load Balancer in an AWS VPC cluster extended into an Outpost, configure the AWS Load Balancer Operator. Note that the Operator cannot provision AWS Network Load Balancers because AWS Outposts does not support them. |
Contributor
Author
There was a problem hiding this comment.
| = Configuring the ARN role for the AWS Load Balancer Operator | ||
|
|
||
| [role="_abstract"] | ||
| To authorize the {aws-short} Load Balancer Operator, configure the Amazon Resource Name (ARN) role as an environment variable by using the CLI. This ensures the Operator has the necessary permissions to manage resources within the cluster. |
Contributor
Author
There was a problem hiding this comment.
| = The IAM role for the AWS Load Balancer Controller | ||
|
|
||
| [role="_abstract"] | ||
| To authorize the {aws-short} Load Balancer Controller, configure the `CredentialsRequest` object with a manually provisioned IAM role. This ensures the controller functions correctly by using the specific permissions defined in your manual provisioning process. |
Contributor
Author
There was a problem hiding this comment.
| = The IAM role for the AWS Load Balancer Operator | ||
|
|
||
| [role="_abstract"] | ||
| To install the {aws-first} Load Balancer Operator on a cluster by using {sts-short}, configure an additional Identity and Access Management (IAM) role. This role enables the Operator to interact with subnets and Virtual Private Clouds (VPCs), allowing the Operator to generate the `CredentialsRequest` object required for bootstrapping. |
Contributor
Author
There was a problem hiding this comment.
| = Creating an AWS IAM role by using the Cloud Credential Operator utility | ||
|
|
||
| [role="_abstract"] | ||
| To enable the {aws-short} Load Balancer Operator to interact with subnets and VPCs, create an {aws-short} IAM role by using the Cloud Credential Operator utility (`ccoctl`). By doing this task, you can generate the necessary credentials for the operator to function correctly within the cluster environment. |
Contributor
Author
There was a problem hiding this comment.
|
|
||
| [role="_abstract"] | ||
| To manage AWS Elastic Load Balancers (ELB) directly from your cluster, install the AWS Load Balancer Operator. This optional Operator is supported by Red{nbsp}Hat for use on SRE-managed {product-title} clusters. | ||
| The AWS Load Balancer Operator is an Operator supported by Red{nbsp}Hat that you can optionally install on SRE-managed {product-title} clusters. |
Contributor
Author
There was a problem hiding this comment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version(s):
4.16+
Issue:
OSDOCS-18673
Link to docs preview: