Modify Domain Access to IP Access

Domain Access Modification 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 ports for the svc services and record them, as they will be used later.

2. Modify the ConfigMap Configuration of Related Services¶

• Log in to the launcher interface via the browser

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

Modify it to the corresponding HOST IP + port under the forethought-core Namespace for management-backend

• 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 the func center in func2

• Confirm the configuration modifications, check the restart service option, and verify through the browser

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