Skip to content

Bug 1804083: Explains requirements for delploying RHEL compute node #21130

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

Closed
adduarte wants to merge 1 commit into from
Closed

Bug 1804083: Explains requirements for delploying RHEL compute node #21130

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: 2 additions & 0 deletions _topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,6 +212,8 @@ Topics:
# File: installing-openstack-load-balancing
- Name: Uninstalling a cluster on OpenStack
File: uninstalling-cluster-openstack
- Name: Adding RHEL compute machines to a cluster on OpenStack
File: adding-rhel-compute-openstack
- Name: Installing on vSphere
Dir: installing_vsphere
Topics:
Expand Down
16 changes: 16 additions & 0 deletions installing/installing_openstack/adding-rhel-compute-openstack.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
[id="adding-hrel-compute-openstack"]
= Adding a RHEL compute node to OpenShift cluster
include::modules/common-attributes.adoc[]
:context: adding-rhel-compute-openstak

toc::[]

The following are additional requirements for xref:../../machine_management/adding-rhel-compute.adoc[Adding RHEL compute machines to an {product-title} cluster],
when the cluster has been deployed on {rh-openstack-first}:

* The RHEL compute nodes being added and the host that executes the playbooks, need to be able to access the cluster api
endpoints using dns resolvable hostnames.

* Security groups must be configured such that RHEL compute nodes and the host executing the playbooks are allowed to
access the cluster api endpoints. This can be tested by trying to access the api tcp port being used by the cluster
from an user account on the hosts. The default tcp port for api access to the cluster is 6443.