Merge pull request #35810 from bergerhoffer/updating-hostname

Updating instances of 'host name' to 'hostname'

Author: bergerhoffer

contributing_to_docs/doc_guidelines.adoc

@@ -408,7 +408,7 @@ control-plane-3.example.com   Ready    master   41m   v1.19.0+9f84db3
 
 [NOTE]
 ====
-Some provider-formatted host names include IPv4 addresses. An OpenShift Container Platform node name typically reflects the host name of a node. If node names in your output need to be provider-specific and require this format, use private IPv4 addresses. For example, you could use `ip-10-0-48-9.example.com` as a node name that includes a private IPv4 address.
+Some provider-formatted hostnames include IPv4 addresses. An OpenShift Container Platform node name typically reflects the hostname of a node. If node names in your output need to be provider-specific and require this format, use private IPv4 addresses. For example, you could use `ip-10-0-48-9.example.com` as a node name that includes a private IPv4 address.
 ====
 
 == IP addresses

contributing_to_docs/term_glossary.adoc

@@ -641,7 +641,7 @@ A service account binds together:
 Usage: SkyDNS
 
 Component of the Kubernetes control plane or OpenShift control plane that provides
-cluster-wide DNS resolution of internal host names for services and pods.
+cluster-wide DNS resolution of internal hostnames for services and pods.
 
 ''''
 === Source-to-Image (S2I)

modules/accessing-hosts-on-aws.adoc

@@ -38,7 +38,7 @@ API is responsive, run privileged pods instead.
 ====
 
 . Run `oc get nodes`, inspect the output, and choose one of the nodes that is a
-master. The host name looks similar to `ip-10-0-1-163.ec2.internal`.
+master. The hostname looks similar to `ip-10-0-1-163.ec2.internal`.
 
 . From the bastion SSH host you manually deployed into Amazon EC2, SSH into that
 control plane host (also known as the master host). Ensure that you use the same SSH key you specified during the

modules/auth-allowing-javascript-access-api-server.adoc

@@ -8,7 +8,7 @@
 The default {product-title} configuration only allows the web console to send requests to the API server.
 
 If you need to access the API server or OAuth server from a JavaScript
-application using a different host name, you can configure additional host names
+application using a different hostname, you can configure additional hostnames
 to allow.
 
 .Prerequisites
@@ -25,7 +25,7 @@ $ oc edit apiserver.config.openshift.io cluster
 ----
 +
 . Add the `additionalCORSAllowedOrigins` field under the `spec` section and
-specify one or more additional host names:
+specify one or more additional hostnames:
 +
 [source,yaml]
 ----
@@ -44,7 +44,7 @@ spec:
   additionalCORSAllowedOrigins:
   - (?i)//my\.subdomain\.domain\.com(:|\z) <1>
 ----
-<1> The host name is specified as a link:https://github.com/google/re2/wiki/Syntax[Golang regular expression] that matches
+<1> The hostname is specified as a link:https://github.com/google/re2/wiki/Syntax[Golang regular expression] that matches
 against CORS headers from HTTP requests against the API server and OAuth server.
 +
 [NOTE]

modules/cluster-logging-collector-legacy-fluentd.adoc

@@ -95,11 +95,11 @@ To configure {product-title} to forward logs using the legacy Fluentd method:
 ----
 <1> Enter the shared key between nodes.
 <2> Specify `tls` to enable TLS validation.
-<3> Set to `true` to verify the server cert host name. Set to `false` to ignore server cert host name.
+<3> Set to `true` to verify the server cert hostname. Set to `false` to ignore server cert hostname.
 <4> Specify the path to the private CA certificate file as `/etc/ocp-forward/ca_cert.pem`.
 <5> Specify the link:https://docs.fluentd.org/configuration/buffer-section[Fluentd buffer parameters] as needed.
 <6> Optionally, enter a name for this server.
-<7> Specify the host name or IP of the server.
+<7> Specify the hostname or IP of the server.
 <8> Specify the host label of the server.
 <9> Specify the port of the server.
 <10> Optionally, add additional servers.

modules/configuring-firewall.adoc

@@ -39,9 +39,9 @@ There are no special configuration considerations for services running on only c
 
 |===
 +
-When you add a site, such as `quay.io`, to your allowlist, do not add a wildcard entry, such as `*.quay.io`, to your denylist. In most cases, image registries use a content delivery network (CDN) to serve images. If a firewall blocks access, then image downloads are denied when the initial download request is redirected to a host name such as `cdn01.quay.io`.
+When you add a site, such as `quay.io`, to your allowlist, do not add a wildcard entry, such as `*.quay.io`, to your denylist. In most cases, image registries use a content delivery network (CDN) to serve images. If a firewall blocks access, then image downloads are denied when the initial download request is redirected to a hostname such as `cdn01.quay.io`.
 +
-CDN host names, such as `cdn01.quay.io`, are covered when you add a wildcard entry, such as `*.quay.io`, in your allowlist.
+CDN hostnames, such as `cdn01.quay.io`, are covered when you add a wildcard entry, such as `*.quay.io`, in your allowlist.
 
 . Allowlist any site that provides resources for a language or framework that your builds require.
 
@@ -144,7 +144,7 @@ the routes work. If you are the cluster administrator and do not want to allow
 `*.apps.<cluster_name>.<base_domain>`, then allow these routes:
 +
 * `oauth-openshift.apps.<cluster_name>.<base_domain>`
-* `console-openshift-console.apps.<cluster_name>.<base_domain>`, or the host name
+* `console-openshift-console.apps.<cluster_name>.<base_domain>`, or the hostname
 that is specified in the `spec.route.hostname` field of the
 `consoles.operator/cluster` object if the field is not empty.
 

modules/dedicated-configuring-your-application-routes.adoc

@@ -37,7 +37,7 @@ service externally, you must create a new route with a specific label,
 `route=external`.
 
 To expose a new route for an existing service, apply the label `route=external`
-and define a host name that contains the secondary, public router shard ID:
+and define a hostname that contains the secondary, public router shard ID:
 
 ----
 $ oc expose service <service-name> -l route=external --name=<custom-route-name> --hostname=<custom-hostname>.<shard-id>.<cluster-id>.openshiftapps.com

modules/identity-provider-github-CR.adoc

@@ -48,7 +48,7 @@ application]. The application must be configured with a callback URL of
 `\https://oauth-openshift.apps.<cluster-name>.<cluster-domain>/oauth2callback/<idp-provider-name>`.
 <5> Reference to an {product-title} `Secret` object containing the client secret
 issued by GitHub.
-<6> For GitHub Enterprise, you must provide the host name of your instance, such as
+<6> For GitHub Enterprise, you must provide the hostname of your instance, such as
 `example.com`. This value must match the GitHub Enterprise `hostname` value in
 in the `/setup/settings` file and cannot include a port number. If this
 value is not set, then either `teams` or `organizations` must be defined.

modules/images-configuration-cas.adoc

@@ -16,7 +16,7 @@ The `image.config.openshift.io/cluster` custom resource can contain a reference
 
 You can create a config map in the `openshift-config` namespace and use its name in `AdditionalTrustedCA` in the `image.config.openshift.io` custom resource to provide additional CAs that should be trusted when contacting external registries.
 
-The config map key is the host name of a registry with the port for which this CA is to be trusted, and the base64-encoded certificate is the value, for each additional registry CA to trust.
+The config map key is the hostname of a registry with the port for which this CA is to be trusted, and the base64-encoded certificate is the value, for each additional registry CA to trust.
 
 .Image registry CA config map example
 [source,yaml]

modules/images-configuration-parameters.adoc

@@ -27,7 +27,7 @@ Every element of this list contains a location of the registry specified by the
 The namespace for this config map is `openshift-config`. The format of the config map is to use the registry hostname as the key, and the PEM-encoded certificate as the value, for each additional registry CA to trust.
 
 |`externalRegistryHostnames`
-|Provides the host names for the default external image registry. The external hostname should be set only when the image registry is exposed externally. The first value is used in `publicDockerImageRepository` field in image streams. The value must be in `hostname[:port]` format.
+|Provides the hostnames for the default external image registry. The external hostname should be set only when the image registry is exposed externally. The first value is used in `publicDockerImageRepository` field in image streams. The value must be in `hostname[:port]` format.
 
 |`registrySources`
 |Contains configuration that determines how the container runtime should treat individual registries when accessing images for builds and
@@ -60,6 +60,6 @@ The `status` field of the `image.config.openshift.io/cluster` resource holds obs
 |Set by the Image Registry Operator, which controls the `internalRegistryHostname`. It sets the hostname for the default internal image registry. The value must be in `hostname[:port]` format. For backward compatibility, you can still use the `OPENSHIFT_DEFAULT_REGISTRY` environment variable, but this setting overrides the environment variable.
 
 |`externalRegistryHostnames`
-|Set by the Image Registry Operator, provides the external host names for the image registry when it is exposed externally. The first value is used in `publicDockerImageRepository` field in image streams. The values must be in `hostname[:port]` format.
+|Set by the Image Registry Operator, provides the external hostnames for the image registry when it is exposed externally. The first value is used in `publicDockerImageRepository` field in image streams. The values must be in `hostname[:port]` format.
 
 |===