Chapter 4. Configuring a cluster-wide proxy

• You are the cluster owner.
• Your account has sufficient privileges.
• You have an existing Virtual Private Cloud (VPC) for your cluster.
• You are using the Customer Cloud Subscription (CCS) model for your cluster.
• The proxy can access the VPC for the cluster and the private subnets of the VPC. The proxy is also accessible from the VPC for the cluster and from the private subnets of the VPC.

• You have added the following endpoints to your VPC endpoint:

  • ec2.<aws_region>.amazonaws.com
  • elasticloadbalancing.<aws_region>.amazonaws.com

  • s3.<aws_region>.amazonaws.com

    These endpoints are required to complete requests from the nodes to the AWS EC2 API. Because the proxy works at the container level and not at the node level, you must route these requests to the AWS EC2 API through the AWS private network. Adding the public IP address of the EC2 API to your allowlist in your proxy server is not enough.

    Important

    When using a cluster-wide proxy, you must configure the s3.<aws_region>.amazonaws.com endpoint as type Gateway.

• If your proxy re-encrypts egress traffic, you must create exclusions to the domain and port combinations. The following table offers guidance into these exceptions.

  • Your proxy must exclude re-encrypting the following OpenShift URLs:

    Address	Protocol/Port	Function
    observatorium-mst.api.openshift.com	https/443	Required. Used for Managed OpenShift-specific telemetry.
    sso.redhat.com	https/443	The https://cloud.redhat.com/openshift site uses authentication from sso.redhat.com to download the cluster pull secret and use Red Hat SaaS solutions to facilitate monitoring of your subscriptions, cluster inventory, and chargeback reporting.

  • Your proxy must exclude re-encrypting the following site reliability engineering (SRE) and management URLs:

    Address	Protocol/Port	Function
    *.osdsecuritylogs.splunkcloud.com OR inputs1.osdsecuritylogs.splunkcloud.cominputs2.osdsecuritylogs.splunkcloud.cominputs4.osdsecuritylogs.splunkcloud.cominputs5.osdsecuritylogs.splunkcloud.cominputs6.osdsecuritylogs.splunkcloud.cominputs7.osdsecuritylogs.splunkcloud.cominputs8.osdsecuritylogs.splunkcloud.cominputs9.osdsecuritylogs.splunkcloud.cominputs10.osdsecuritylogs.splunkcloud.cominputs11.osdsecuritylogs.splunkcloud.cominputs12.osdsecuritylogs.splunkcloud.cominputs13.osdsecuritylogs.splunkcloud.cominputs14.osdsecuritylogs.splunkcloud.cominputs15.osdsecuritylogs.splunkcloud.com	tcp/9997	Used by the splunk-forwarder-operator as a log forwarding endpoint to be used by Red Hat SRE for log-based alerting.
    http-inputs-osdsecuritylogs.splunkcloud.com	https/443	Used by the splunk-forwarder-operator as a log forwarding endpoint to be used by Red Hat SRE for log-based alerting.

• Ensuring that the contents of the additional trust bundle are valid
• Ensuring that the certificates, including intermediary certificates, contained in the additional trust bundle have not expired
• Tracking the expiry and performing any necessary renewals for certificates contained in the additional trust bundle
• Updating the cluster configuration with the updated additional trust bundle

Prerequisites

• You have an OpenShift Dedicated cluster that uses the Customer Cloud Subscription (CCS) model .
• Your cluster is deployed in a VPC.

Verification

• Under the Virtual Private Cloud (VPC) section on the Networking page, verify that the proxy configuration for your cluster is as expected.