5.1.10 Validating the Networking Environment
Perform the checks described in this section to ensure that your environment is ready for a
deployment. If any of the checks fail, then you must resolve before proceeding.
Note:
The variables used in this section are based on the values collected in the earlier Configuration Checkpoint sectionsBastion or Master/Control Plane
- From the Kubernetes bastion, or master/control plane node, run the following:
nc -zv <WEB_HOST> <PORT>
Note:
In this case <WEB_HOST> is the fully qualified hostname of the OHS (or load balancer if one is used in front of OHS), and<PORT>
is the configured SSL port.nc -zv <DB_HOST> <DB_PORT>
nc -zv <LDAP_HOST> <LDAP_PORT>
Ncat: Connected to <IP_ADDRESS>:<PORT>. Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
- Most containers do not have built in networking tools to allow you to check that DNS
resolution is working correctly. The easiest way to validate the changes is to use a
lightweight container with the network tools installed, such as alpine:
- Run the following command to run an alpine container:
kubectl run -i --tty --rm debug --image=docker.io/library/alpine:latest --restart=Never -- sh
Note:
The above assumes your Kubernetes cluster has access to the internet to accessdocker.io
. - Inside the container you can then run
nslookup
against the <DB_HOST>, <LDAP_HOST>, <WEB_HOST> (and <LBR_HOST> if using a load balancer), and <CIR_HOST>. For example:
Make sure the hostnames resolve correctly. If you have problems resolving any of the hostnames, contact the Kubernetes administrator to resolve before proceeding.nslookup ohs.example.com
- Run the following command to run an alpine container:
Web Tier (OHS)
From the <WEB_HOST>, run the following to check you can connect to
the ingress controller port:
nc -zv <K8S_WORKER_HOST1> 30777
nc -zv <K8S_WORKER_HOST2> 30777
nc -zv <K8S_WORKER_HOST3> 30777
Ncat: Connected to <IP_ADDRESS>:30777.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
OAA Installation Host
From the <INSTALL_HOST>, run the following:
ping <CIR_HOST>
kubectl get nodes
curl -k -I https://container-registry.oracle.com
Note:
You should receiveHTTP/1.0 200 Connection Established