Skip to content

Latest commit

 

History

History
38 lines (32 loc) · 1.17 KB

port_forwarding.md

File metadata and controls

38 lines (32 loc) · 1.17 KB
Raw

Port Forwarding (No Ingress) Architecture

Port Forwarding Architecture

Configuration

You can create the ingress using the following steps.

1) Change production_json in values.yaml

console:
  production_json:
    CONSOLE_API:
      ENDPOINT: http://127.0.0.1:8081
    CONSOLE_API_V2:
      ENDPOINT: http://127.0.0.1:8082

After editing the values.yaml file, upgrade the helm chart.

helm upgrade cloudforet cloudforet/spaceone -n spaceone -f values.yaml
kubectl delete po -n spaceone -l app.kubernetes.io/name=console

2) Port Forwarding

Since the ingress is not used, you need to port forward the console, console-api and console-api-v2-rest services.

kubectl port-forward svc/console -n spaceone 8080:80 --address=0.0.0.0 &
kubectl port-forward svc/console-api -n spaceone 8081:80 --address=0.0.0.0 &
kubectl port-forward svc/console-api-v2-rest -n spaceone 8082:80 --address=0.0.0.0 &

3) Connect to the Console

You can access the console using the following URL.

4) Close Port Forwarding

kill $(ps aux | grep 'kubectl port-forward' | awk '{print $2}')