Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect to private HCP cluster using public NLB #615

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update _index.md
  • Loading branch information
nedoshi authored Feb 5, 2025
commit 7324888b0e5b2362df01586eaac01c722dc96a21
7 changes: 4 additions & 3 deletions content/rosa/hcp-public-nlb/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ This document provides guidance on using a public AWS Network Load Balancer (NLB


3. (Optional) Launch an Jump Host EC2 instance in Public NLB VPC
This guide requires connectivity to the cluster, because we are using a private cluster you will need to ensure your workstation is connected to the AWS VPC which hosts the ROSA cluster. If you already have this connectivity through a VPN, Direct Link or other method you can skip this part. If you do need to establish connectivity to the cluster [these instructions](./rosa/hcp-private-nlb/rosa-private-nlb-jumphost) will guide you through creating a jump host on the public subnet of the ROSA cluster.
This guide requires connectivity to the cluster, because we are using a private cluster you will need to ensure your workstation is connected to the AWS VPC which hosts the ROSA cluster. If you already have this connectivity through a VPN, Direct Link or other method you can skip this part. If you do need to establish connectivity to the cluster [these instructions](https://cloud.redhat.com/experts/rosa/hcp-private-nlb/rosa-private-nlb-jumphost/) will guide you through creating a jump host and connectto the ROSA HCP cluster.

## Create security group, target group and network load balancer in AWS subscription

Expand All @@ -30,7 +30,6 @@ Once ROSA HCP cluster is installed with external authentication as Entra ID we n
- Navigate to the **Security Groups** section in the AWS console click **Create security group**.
- **Name tag**: Give your security group a name. Select the VPC that your Network Load Balancer is in.**Click Create**.
- **Modify Inbound Rules** Select the newly created security group from the list. Go to the **Inbound rules** tab and click **Edit inbound rules**. Add a new inbound rule with the following settings:

- **Type**: Choose the appropriate protocol for your NLB (e.g., HTTP, HTTPS, or TCP, depending on the service you're exposing).
- **Protocol**: Choose the protocol for your NLB (TCP is commonly used for NLBs).
- **Port Range**: Specify the port your NLB is listening on (e.g., 80 for HTTP, 443 for HTTPS).
Expand Down Expand Up @@ -141,7 +140,9 @@ example output:
export nlb-domain-name=https://api.example.com
```

create a KUBECONFIG file here with EntraID details for example create **rosa-auth.kubeconfig** file with following information
create a KUBECONFIG file here with EntraID details for [ROSA HCP cluster with external auth enabled](https://cloud.redhat.com/experts/rosa/entra-external-auth).

example create **rosa-auth.kubeconfig** file with following information

```bash
apiVersion: v1
Expand Down