Modify Domain Access to IP Access

Change Domain Access to IP Access¶

1. Modify the SVC Configuration of Related Services¶

• Modify the service status in the forethought-webclient Namespace

kubectl patch svc management-webclient -n forethought-webclient -p '{"spec": {"type": "NodePort"}}'
kubectl patch svc front-webclient -n forethought-webclient -p '{"spec": {"type": "NodePort"}}'
kubectl patch svc dataflux-doc -n forethought-webclient -p '{"spec": {"type": "NodePort"}}'

• Modify the service status in the forethought-core Namespace

kubectl patch svc management-backend -n forethought-core -p '{"spec": {"type": "NodePort"}}'
kubectl patch svc static-resource-nginx -n forethought-core -p '{"spec": {"type": "NodePort"}}'
kubectl patch svc front-backend -n forethought-core -p '{"spec": {"type": "NodePort"}}'

• Modify the service status in the func2 Namespace

kubectl patch svc server -n func2 -p '{"spec": {"type": "NodePort"}}'

Obtain the corresponding NodePort of the SVC and record it for later use.

2. Modify the ConfigMap Configuration of Related Services¶

• Log in to the launcher interface via browser

• Modify the ConfigMap configuration related to backend management in forethought-webclient

Change to the host IP + port corresponding to management-backend in the forethought-core Namespace

• Modify the ConfigMap configuration related to the homepage in forethought-webclient

• Modify the ConfigMap configuration related to the homepage in forethought-core

• Modify the ConfigMap configuration related to kodo-nginx in forethought-kodo

• Modify the ConfigMap configuration related to func center in func2

• Confirm the configuration changes, then check the restart service option and verify in the browser

Note: After making changes, wait a few minutes for the services to restart before accessing them.