Updated asset paths and next config for cname.
This commit is contained in:
@ -22,7 +22,7 @@ There are of course many different options for installing OpenShift in a restric
|
||||
To get underway open your web browser and navigate to this etherpad link to reserve yourself a user https://etherpad.wikimedia.org/p/OpenShiftDisco_2023_12_20. You can reserve a user by noting your name or initials next to a user that has not yet been claimed.
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Etherpad collaborative editor* |
|
||||
</Zoom>
|
||||
@ -50,7 +50,7 @@ For the purposes of this workshop we will be operating within Amazon Web Service
|
||||
The diagram below shows a simplified overview of the networking topology:
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Workshop network topology* |
|
||||
</Zoom>
|
||||
|
||||
@ -38,7 +38,7 @@ echo "Security group id is: ${SG_ID}"
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Creating aws ec2 security group* |
|
||||
</Zoom>
|
||||
@ -55,7 +55,7 @@ aws ec2 authorize-security-group-ingress --group-id $SG_ID --protocol tcp --port
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Opening ssh port ingress* |
|
||||
</Zoom>
|
||||
@ -81,7 +81,7 @@ aws ec2 run-instances --image-id "ami-092b43193629811af" \
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Launching a prep rhel8 ec2 instance* |
|
||||
</Zoom>
|
||||
@ -103,7 +103,7 @@ ssh -i disco_key ec2-user@$PREP_SYSTEM_IP
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Connecting to the prep rhel8 ec2 instance* |
|
||||
</Zoom>
|
||||
@ -161,7 +161,7 @@ rm -f openshift-installer.tar.gz
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Downloading required tools with curl* |
|
||||
</Zoom>
|
||||
|
||||
@ -14,7 +14,7 @@ In this exercise, we'll prepare the **High side**. This involves creating a bast
|
||||
>
|
||||
> We could rectify this by running `sudo dnf install -y podman` on the bastion system, but the bastion server won't have Internet access, so we need another option for this lab. To solve this problem, we need to build our own RHEL image with podman pre-installed. Real customer environments will likely already have a solution for this, but one approach is to use the [Image Builder](https://console.redhat.com/insights/image-builder) in the Hybrid Cloud Console, and that's exactly what has been done for this lab.
|
||||
>
|
||||
> [workshop](/workshops/static/images/disconnected/image-builder.png)
|
||||
> [workshop](/static/images/disconnected/image-builder.png)
|
||||
>
|
||||
> In the home directory of your web terminal you will find an `ami.txt` file containng our custom image AMI which will be used by the command that creates our bastion ec2 instance.
|
||||
|
||||
@ -47,7 +47,7 @@ aws ec2 run-instances --image-id $(cat ami.txt) \
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Launching bastion ec2 instance* |
|
||||
</Zoom>
|
||||
@ -87,7 +87,7 @@ ssh -t -i disco_key ec2-user@$PREP_SYSTEM_IP "ssh -t -i disco_key ec2-user@$HIGH
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Connecting to our bastion ec2 instance* |
|
||||
</Zoom>
|
||||
@ -111,7 +111,7 @@ ssh -t -i disco_key ec2-user@$PREP_SYSTEM_IP "rsync -avP -e 'ssh -i disco_key' /
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Initiating the sneakernet transfer via rsync* |
|
||||
</Zoom>
|
||||
|
||||
@ -59,7 +59,7 @@ INFO[2023-07-06 15:43:41] Quay is available at https://ip-10-0-51-47.ec2.interna
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Running the mirror-registry installer* |
|
||||
</Zoom>
|
||||
@ -94,7 +94,7 @@ oc mirror --from=/mnt/high-side/mirror_seq1_000000.tar --dest-skip-tls docker://
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Running the oc mirror process to push content to our registry* |
|
||||
</Zoom>
|
||||
|
||||
@ -17,7 +17,7 @@ By default, the installation program acts as an installation wizard, prompting y
|
||||
We'll then customize the `install-config.yaml` file that is produced to specify advanced configuration for our disconnected installation. The installation program then provisions the underlying infrastructure for the cluster. Here's a diagram describing the inputs and outputs of the installation configuration process:
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Installation overview* |
|
||||
</Zoom>
|
||||
@ -200,7 +200,7 @@ We're ready to run the install! Let's kick off the cluster installation by copyi
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Installation overview* |
|
||||
</Zoom>
|
||||
|
||||
Reference in New Issue
Block a user