1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/installation-osp-accessing-api-floating.adoc

102 lines
3.7 KiB
Plaintext

// Module included in the following assemblies:
//
// * installing/installing_openstack/installing-openstack-installer.adoc
// * installing/installing_openstack/installing-openstack-installer-custom.adoc
// * installing/installing_openstack/installing-openstack-user.adoc
ifeval::["{context}" == "installing-openstack-user"]
:osp-user:
endif::[]
ifeval::["{context}" == "installing-openstack-user-sr-iov"]
:osp-user:
endif::[]
:_mod-docs-content-type: PROCEDURE
[id="installation-osp-accessing-api-floating_{context}"]
= Enabling access with floating IP addresses
Create floating IP (FIP) addresses for external access to the {product-title}
ifdef::osp-user[API, cluster applications, and the bootstrap process.]
ifndef::osp-user[API and cluster applications.]
.Procedure
. Using the {rh-openstack-first} CLI, create the API FIP:
+
[source,terminal]
----
$ openstack floating ip create --description "API <cluster_name>.<base_domain>" <external_network>
----
. Using the {rh-openstack-first} CLI, create the apps, or Ingress, FIP:
+
[source,terminal]
----
$ openstack floating ip create --description "Ingress <cluster_name>.<base_domain>" <external_network>
----
ifdef::osp-user[]
. By using the {rh-openstack-first} CLI, create the bootstrap FIP:
+
[source,terminal]
----
$ openstack floating ip create --description "bootstrap machine" <external_network>
----
endif::osp-user[]
. Add records that follow these patterns to your DNS server for the API and Ingress FIPs:
+
[source,dns]
----
api.<cluster_name>.<base_domain>. IN A <API_FIP>
*.apps.<cluster_name>.<base_domain>. IN A <apps_FIP>
----
+
[NOTE]
====
If you do not control the DNS server, you can access the cluster by adding the cluster domain names such as the following to your `/etc/hosts` file:
* `<api_floating_ip> api.<cluster_name>.<base_domain>`
* `<application_floating_ip> grafana-openshift-monitoring.apps.<cluster_name>.<base_domain>`
* `<application_floating_ip> prometheus-k8s-openshift-monitoring.apps.<cluster_name>.<base_domain>`
* `<application_floating_ip> oauth-openshift.apps.<cluster_name>.<base_domain>`
* `<application_floating_ip> console-openshift-console.apps.<cluster_name>.<base_domain>`
* `application_floating_ip integrated-oauth-server-openshift-authentication.apps.<cluster_name>.<base_domain>`
The cluster domain names in the `/etc/hosts` file grant access to the web console and the monitoring interface of your cluster locally. You can also use the `kubectl` or `oc`. You can access the user applications by using the additional entries pointing to the <application_floating_ip>. This action makes the API and applications accessible to only you, which is not suitable for production deployment, but does allow installation for development and testing.
====
. Add the FIPs to the
ifdef::osp-user[`inventory.yaml`]
ifndef::osp-user[`install-config.yaml`]
file as the values of the following
ifdef::osp-user[variables:]
ifndef::osp-user[parameters:]
ifdef::osp-user[]
* `os_api_fip`
* `os_bootstrap_fip`
* `os_ingress_fip`
endif::osp-user[]
ifndef::osp-user[]
* `platform.openstack.ingressFloatingIP`
* `platform.openstack.apiFloatingIP`
endif::osp-user[]
If you use these values, you must also enter an external network as the value of the
ifdef::osp-user[`os_external_network` variable in the `inventory.yaml` file.]
ifndef::osp-user[`platform.openstack.externalNetwork` parameter in the `install-config.yaml` file.]
[TIP]
====
You can make {product-title} resources available outside of the cluster by assigning a floating IP address and updating your firewall configuration.
====
ifeval::["{context}" == "installing-openstack-user"]
:!osp-user:
endif::[]
ifeval::["{context}" == "installing-openstack-user-sr-iov"]
:!osp-user:
endif::[]