mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
87 lines
5.2 KiB
Plaintext
87 lines
5.2 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="configuring-aws-outposts"]
|
|
= Extending an AWS VPC cluster into an AWS Outpost
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: configuring-aws-outposts
|
|
:zone-type: AWS Outposts
|
|
|
|
toc::[]
|
|
|
|
After xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[installing a cluster on Amazon Web Services (AWS) into an existing Amazon Virtual Private Cloud (VPC)], you can create a compute machine set that deploys compute machines in AWS Outposts.
|
|
AWS Outposts is an AWS edge compute service that enables using many features of a cloud-based AWS deployment with the reduced latency of an on-premise environment.
|
|
For more information, see the link:https://docs.aws.amazon.com/outposts/[AWS Outposts documentation].
|
|
|
|
//AWS Outposts on {product-title} requirements and limitations
|
|
include::modules/aws-outposts-requirements-limitations.adoc[leveloffset=+1]
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
* xref:../post_installation_configuration/configuring-aws-outposts.adoc#nw-aws-load-balancer-with-outposts_configuring-aws-outposts[Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost]
|
|
|
|
[id="aws-outposts-environment-info_{context}"]
|
|
== Obtaining information about your environment
|
|
|
|
To extend an AWS VPC cluster to your Outpost, you must provide information about your {product-title} cluster and your Outpost environment.
|
|
You use this information to complete network configuration tasks and configure a compute machine set that creates compute machines in your Outpost.
|
|
You can use command-line tools to gather the required details.
|
|
|
|
//Obtaining information from your {product-title} cluster
|
|
include::modules/aws-outposts-environment-info-oc.adoc[leveloffset=+2]
|
|
|
|
//Obtaining information from your AWS account
|
|
include::modules/aws-outposts-environment-info-aws.adoc[leveloffset=+2]
|
|
|
|
[id="aws-outposts-network-config_{context}"]
|
|
== Configuring your network for your Outpost
|
|
|
|
To extend your VPC cluster into an Outpost, you must complete the following network configuration tasks:
|
|
|
|
* Change the Cluster Network MTU.
|
|
* Create a subnet in your Outpost.
|
|
|
|
//Changing the Cluster Network MTU to support AWS Outposts
|
|
include::modules/nw-cluster-mtu-change.adoc[leveloffset=+2]
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
* xref:../networking/changing-cluster-network-mtu.adoc#changing-cluster-network-mtu[Changing the MTU for the cluster network]
|
|
|
|
//Creating subnets for AWS edge compute services
|
|
include::modules/installation-creating-aws-vpc-subnets-edge.adoc[leveloffset=+2]
|
|
|
|
//CloudFormation template for the VPC Subnet
|
|
include::modules/installation-cloudformation-subnet-localzone.adoc[leveloffset=+2]
|
|
|
|
//Creating a compute machine set that deploys edge compute machines an Outpost
|
|
include::modules/aws-outposts-machine-set.adoc[leveloffset=+1]
|
|
|
|
//Creating user workloads in an Outpost
|
|
include::modules/create-user-workloads-aws-edge.adoc[leveloffset=+1]
|
|
//To-do: reintegrate installation-extend-edge-nodes-aws-local-zones.adoc with create-user-workloads-aws-edge.adoc. Requires global repo update of any xrefs/includes.
|
|
|
|
[id="aws-outposts-network-scheduling-workloads_{context}"]
|
|
== Scheduling workloads on edge and cloud-based AWS compute resources
|
|
|
|
When you extend an AWS VPC cluster into an Outpost, the Outpost uses edge compute nodes and the VPC uses cloud-based compute nodes.
|
|
The following load balancer considerations apply to an AWS VPC cluster extended into an Outpost:
|
|
|
|
* Outposts cannot run AWS Network Load Balancers or AWS Classic Load Balancers, but a Classic Load Balancer for a VPC cluster extended into an Outpost can attach to the Outpost edge compute nodes.
|
|
For more information, see xref:../post_installation_configuration/configuring-aws-outposts.adoc#aws-outposts-load-balancer-clb_configuring-aws-outposts[Using AWS Classic Load Balancers in an AWS VPC cluster extended into an Outpost].
|
|
|
|
* To run a load balancer on an Outpost instance, you must use an AWS Application Load Balancer.
|
|
You can use the AWS Load Balancer Operator to deploy an instance of the AWS Load Balancer Controller.
|
|
The controller provisions AWS Application Load Balancers for Kubernetes Ingress resources.
|
|
For more information, see xref:../post_installation_configuration/configuring-aws-outposts.adoc#nw-aws-load-balancer-with-outposts_configuring-aws-outposts[Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost].
|
|
|
|
//Using Classic Load Balancers in an AWS VPC cluster extended into an Outpost
|
|
include::modules/aws-outposts-load-balancer-clb.adoc[leveloffset=+2]
|
|
|
|
//Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost
|
|
include::modules/nw-aws-load-balancer-with-outposts.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
* xref:../networking/aws_load_balancer_operator/create-instance-aws-load-balancer-controller.adoc#nw-creating-instance-aws-load-balancer-controller_create-instance-aws-load-balancer[Creating an instance of the AWS Load Balancer Controller using AWS Load Balancer Operator]
|
|
|
|
[role="_additional-resources"]
|
|
[id="additional-resources_configuring-aws-outposts"]
|
|
== Additional resources
|
|
* xref:../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[Installing a cluster on AWS into an existing VPC] |