Merge pull request #79754 from abrennan89/OSDOCS-11553

OSDOCS-11553: Move AWS Outposts content to install book

Author: abrennan89

_topic_maps/_topic_map.yml

@@ -182,7 +182,7 @@ Topics:
       File: installing-aws-localzone
     - Name: Installing a cluster with compute nodes on Wavelength Zones
       File: installing-aws-wavelength-zone
-    - Name: Installing a cluster with compute nodes on Outposts
+    - Name: Extending an AWS VPC cluster into an AWS Outpost
       File: installing-aws-outposts
   - Name: User-provisioned infrastructure
     Dir: upi
@@ -654,8 +654,6 @@ Topics:
 - Name: AWS Local Zone or Wavelength Zone tasks
   File: aws-compute-edge-zone-tasks
   Distros: openshift-enterprise
-- Name: Extending an AWS VPC cluster into an AWS Outpost
-  File: configuring-aws-outposts
 ---
 Name: Updating clusters
 Dir: updating

installing/installing_aws/ipi/installing-aws-outposts.adoc

@@ -1,13 +1,89 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="installing-aws-outposts"]
-= Installing a cluster with compute nodes on AWS Outposts
+= Extending an AWS VPC cluster into an AWS Outpost
 include::_attributes/common-attributes.adoc[]
 :context: installing-aws-outposts
+:zone-type: AWS Outposts
 
 toc::[]
 
-In {product-title} version 4.14, you could install a cluster on Amazon Web Services (AWS) with compute nodes running in AWS Outposts as a Technology Preview. As of {product-title} version 4.15, this installation method is no longer supported.
+In {product-title} version 4.14, you could install a cluster on Amazon Web Services (AWS) with compute nodes running in AWS Outposts as a Technology Preview. As of {product-title} version 4.15, this installation method is no longer supported. Instead, you can install a cluster on AWS into an existing VPC, and provision compute nodes on AWS Outposts as a postinstallation configuration task.
 
-Instead, you can xref:../../../installing/installing_aws/ipi/installing-aws-vpc.adoc#installing-aws-vpc[install a cluster on AWS into an existing VPC] and provision compute nodes on AWS Outposts as a postinstallation configuration task.
+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].
 
-For more information, see xref:../../../post_installation_configuration/configuring-aws-outposts.adoc#configuring-aws-outposts[Extending an AWS VPC cluster into an AWS Outpost]
+//AWS Outposts on {product-title} requirements and limitations
+include::modules/aws-outposts-requirements-limitations.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../installing/installing_aws/ipi/installing-aws-outposts.adoc#nw-aws-load-balancer-with-outposts_installing-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:../../../installing/installing_aws/ipi/installing-aws-outposts.adoc#aws-outposts-load-balancer-clb_installing-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:../../../installing/installing_aws/ipi/installing-aws-outposts.adoc#nw-aws-load-balancer-with-outposts_installing-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-installing-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]

installing/installing_aws/ipi/installing-aws-vpc.adoc

@@ -105,4 +105,4 @@ include::modules/logging-in-by-using-the-web-console.adoc[leveloffset=+1]
 * xref:../../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
 * If necessary, you can xref:../../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
 * If necessary, you can xref:../../../post_installation_configuration/changing-cloud-credentials-configuration.adoc#manually-removing-cloud-creds_changing-cloud-credentials-configuration[remove cloud provider credentials].
-* After installing a cluster on AWS into an existing VPC, you can xref:../../../post_installation_configuration/configuring-aws-outposts.adoc#configuring-aws-outposts[extend the AWS VPC cluster into an AWS Outpost].
+* After installing a cluster on AWS into an existing VPC, you can xref:../../../installing/installing_aws/ipi/installing-aws-outposts.adoc#installing-aws-outposts[extend the AWS VPC cluster into an AWS Outpost].

modules/aws-outposts-environment-info-aws.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="aws-outposts-environment-info-aws_{context}"]
@@ -57,4 +57,4 @@ $ aws outposts get-outpost-instance-types \
 ----
 $ aws ec2 describe-subnets \
   --filters Name=outpost-arn,Values=<outpost_arn_value>
-----
+----

modules/aws-outposts-environment-info-oc.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="aws-outposts-environment-info-oc_{context}"]
@@ -63,4 +63,4 @@ $ oc get machinesets.machine.openshift.io <compute_machine_set_name_1> \
 $ oc get machinesets.machine.openshift.io <compute_machine_set_name_1> \
   -n openshift-machine-api \
   -o jsonpath='{.spec.template.spec.providerSpec.value.subnet.id}'
-----
+----

modules/aws-outposts-load-balancer-clb.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="aws-outposts-load-balancer-clb_{context}"]
@@ -120,4 +120,4 @@ $ HOST=$(oc get service <application_name> -n <application_namespace> --template
 $ curl $HOST
 ----
 
-. In the AWS console, verify that only the labeled instances appear as the targeted instances for the load balancer.
+. In the AWS console, verify that only the labeled instances appear as the targeted instances for the load balancer.

modules/aws-outposts-machine-set.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="aws-outposts-machine-set_{context}"]
@@ -216,4 +216,4 @@ NAME                             PHASE          TYPE        REGION      ZONE
 [source,terminal]
 ----
 $ oc describe machine <machine_from_new_1> -n openshift-machine-api
-----
+----

modules/aws-outposts-requirements-limitations.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 :_mod-docs-content-type: REFERENCE
 [id="aws-outposts-requirements-limitations_{context}"]
@@ -44,4 +44,4 @@ You must use AWS Application Load Balancers to enable load balancing for edge co
 To provision an Application Load Balancer, you must use an Ingress resource and install the AWS Load Balancer Operator.
 If your cluster contains both edge and cloud-based compute instances that share workloads, additional configuration is required.
 +
-For more information, see "Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost".
+For more information, see "Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost".

modules/create-user-workloads-aws-edge.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
 //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.
 
@@ -132,4 +132,4 @@ spec:
 [source,terminal]
 ----
 $ oc create -f <application_service>.yaml
-----
+----

modules/installation-cloudformation-subnet-localzone.adoc

@@ -3,9 +3,9 @@
 // * installing/installing-aws-localzone.adoc (Installing a cluster on AWS with worker nodes on AWS Local Zones)
 // * installing/installing-aws-wavelength-zone.adoc (Installing a cluster on AWS with compute nodes on AWS Wavelength Zones)
 // * post_installation_configuration/aws-compute-edge-zone-tasks.adoc (AWS zone tasks)
-// * post_installation_configuration/configuring-aws-outposts.adoc
+// * installing/installing_aws/ipi/installing-aws-outposts.adoc
 
-ifeval::["{context}" == "configuring-aws-outposts"]
+ifeval::["{context}" == "installing-aws-outposts"]
 :outposts:
 endif::[]
 
@@ -150,6 +150,6 @@ ifdef::outposts[]
 endif::outposts[]
 ====
 
-ifeval::["{context}" == "configuring-aws-outposts"]
+ifeval::["{context}" == "installing-aws-outposts"]
 :!outposts:
-endif::[]
+endif::[]