You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can run the `service-proxy` service locally to debug and test against a running greenhouse cluster.
4
+
5
+
## Prerequisites
6
+
7
+
Point the environment variable `KUBECONFIG` to the kubeconfig file of the target greenhouse cluster you want to test against.
8
+
9
+
The exposed service URLs generated on the target Greenhouse cluster need to be reachable from your local machine.
10
+
Set the environment variable `GREENHOUSE_DNS_DOMAIN` to the DNS domain used in the target greenhouse cluster. For example: `myorg.greenhouse.tld`
11
+
12
+
In order to forward the requests to your local machine, you can use a service like `nip.io` that maps wildcard DNS to IP addresses.
13
+
Set the environment variable `DEBUG_DOMAIN` to a domain that maps to your local machine. For example: `127.0.0.1.nip.io:8080`
14
+
15
+
This will override the DNS domain in the exposed service URLs generated on the target greenhouse cluster, allowing you to access them locally.
16
+
17
+
## Running the service
18
+
19
+
Run the service proxy locally passing the arguments for `--kubecontext` and `--kubenamespace` to point to the correct organization in the target greenhouse cluster.
20
+
21
+
In your browser you can now access the exposed services using the URLs generated by the service proxy, which will be redirected to your local machine. For this take the generated part `<cluster-name>--<service-hash>` and prepend it to the `DEBUG_DOMAIN`.
22
+
23
+
e.g. `http://testcluster--abcdefg.127.0.0.1.nip.io:8080/`
0 commit comments