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
On Kubernetes, we should deploy it in two separate containers, one for be and the other for fe.
We already have docker files for the two in their respective folders.
We provide a deployment, service and external route/node-port/load-balancer for the rest api. All the pyiceberg related configuration will go to backend. Once the be container is deployed, we need a URL using which one can access the be services from their browser. This is the url the fe client will use to communicate with the be services.
Once the be rest api url is available, we need to configure the fe app. It requires two things:
#Front end specific properties
PUBLIC_API_SERVER= <- this is the externally accessible url of the be rest api.
PUBLIC_API_SERVER_SERVER_SIDE= <- this is the kubernetes service name and port of the be service. Svelte uses this on the server side.
With the above two available, then it is a matter of providing the deployment yaml for for the fe container and it will have its own externally facing URL from which the lakevision UI will be available.
The text was updated successfully, but these errors were encountered:
On Kubernetes, we should deploy it in two separate containers, one for
be
and the other forfe
.We already have docker files for the two in their respective folders.
We provide a deployment, service and external route/node-port/load-balancer for the rest api. All the pyiceberg related configuration will go to backend. Once the be container is deployed, we need a URL using which one can access the
be
services from their browser. This is the url thefe
client will use to communicate with thebe
services.Once the
be
rest api url is available, we need to configure thefe
app. It requires two things:#Front end specific properties
PUBLIC_API_SERVER= <- this is the externally accessible url of the
be
rest api.PUBLIC_API_SERVER_SERVER_SIDE= <- this is the kubernetes service name and port of the
be
service. Svelte uses this on the server side.With the above two available, then it is a matter of providing the deployment yaml for for the
fe
container and it will have its own externally facing URL from which the lakevision UI will be available.The text was updated successfully, but these errors were encountered: