8.4 Accessing OUDSM Through Ingress
Using the Helm chart, ingress objects are created according to configuration.
The following table details the rules configured in ingress object(s) for access to Oracle Unified Directory Services Manager (OUDSM) interfaces through ingress.
| Port | NodePort | Host | Example Hostname | Path | Backend Service:Port | Example Service Name:Port |
|---|---|---|---|---|---|---|
| http/https | 30080/30443 | <deployment/release name>-N | oudsm-N | N | <deployment/release name>-N:http | oudsm-1:http |
| http/https | 30080/30443 | * | * |
/oudsm /console |
<deployment/release name>-lbr:http | oudsm-lbr:http |
Note:
In the table above, example values are based on the value ‘oudsm’ as the deployment/release name for Helm chart installation.
The NodePorts mentioned in the table are according to ingress configuration described in
the previous section. When an External LoadBalancer is not available/configured,
interfaces can be accessed through NodePort on a Kubernetes node.
Changes in /etc/hosts to Validate Hostname Based Ingress Rules
If it is not possible to update the DNS with the OUDSM hostname interfaces, then the
following entries can be added in
/etc/hosts file on the host from
where OUDSM interfaces will be accessed.<IP Address of External LBR or Kubernetes Node> oudsm oudsm-1 oudsm-2 oudsm-N
- In the table above, hostnames are based on the value ‘
oudsm’ as the deployment/release name for Helm chart installation. - When External LoadBalancer is not available/configured, interfaces can be accessed through NodePort on the Kubernetes Node.