Skip to content

OSDOCS-17013-remediation-2 #109518

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.

Sign up for GitHub

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

Open
dfitzmau wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OSDOCS-17013-remediation-2 #109518

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion modules/installation-infrastructure-user-infra.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ endif::[]
= Preparing the user-provisioned infrastructure

[role="_abstract"]
To ensure a successful deployment and meet cluster requirements in {product-title}, prepare your user-provisioned infrastructure before starting the installation. Configuring your compute, network, and storage components in advance provides the stable foundation necessary for the installation program to function correctly.
Before you install {product-title} on user-provisioned infrastructure, you must prepare the underlying infrastructure.

This section provides details about the high-level steps required to set up your cluster infrastructure in preparation for an {product-title} installation. This includes configuring IP networking and network connectivity for your cluster nodes,
ifdef::ibm-z[]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-initializing-manual.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ endif::[]
= Manually creating the installation configuration file

[role="_abstract"]
To customise your {product-title} deployment and meet specific network requirements, manually create the installation configuration file. This ensures that the installation program uses your tailored settings rather than default values during the setup process.
Installing the cluster requires that you manually create the installation configuration file.

ifdef::vsphere-upi,restricted-upi[]
[IMPORTANT]
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-user-provisioned-validating-dns.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
= Validating DNS resolution for user-provisioned infrastructure

[role="_abstract"]
To prevent network-related installation failures and ensure node connectivity in {product-title}, validate your DNS configuration before deploying on user-provisioned infrastructure. This verification confirms that all required records resolve correctly, providing the stable foundation necessary for cluster communication.
To prevent network-related installation failures and ensure node connectivity in {product-title}, validate your DNS configuration before deploying on user-provisioned infrastructure.

[IMPORTANT]
====
Expand Down
2 changes: 1 addition & 1 deletion modules/ssh-agent-using.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ endif::[]
= Generating a key pair for cluster node SSH access

[role="_abstract"]
To enable secure, passwordless SSH access to your cluster nodes, provide an SSH public key during the {product-title} installation. This ensures that the installation program automatically configures the {op-system-first} nodes for remote authentication through the `core` user.
During an {product-title} installation, you can provide an SSH public key to the installation program. The key is passed to the {op-system-first} nodes through their Ignition config files and is used to authenticate SSH access to the nodes. The key is added to the `~/.ssh/authorized_keys` list for the `core` user on each node, which enables password-less authentication.

The SSH public key gets added to the `~/.ssh/authorized_keys` list for the `core` user on each node. After the key is passed to the {op-system-first} nodes through their Ignition config files, you can use the key pair to SSH in to the {op-system} nodes as the user `core`. To access the nodes through SSH, the private key identity must be managed by SSH for your local user.

Expand Down