Change Domain Access to IP Access

Change Domain Access to IP Access¶

1. Modify SVC Configuration of Related Services¶

• Modify the service status under 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 under 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 under the func2 Namespace

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

Get the corresponding SVC NodePort and record it for later use.

2. Modify ConfigMap Configuration of Related Services¶

• Log in to the launcher interface via browser

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

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

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

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

• Modify the ConfigMap configuration of kodo-nginx under forethought-kodo

• Modify the ConfigMap configuration of func2 related to the func center

• Confirm and modify the configuration, then select to restart the service and verify it in the browser

Note: After modification, wait a few minutes for the service to restart before accessing.