Khuyen Tran
12/27/2021, 9:30 PMflytectl sandbox start --source .
. After doing that, I can access to Flyte UI. However, after stopping the container, I tried to run flytectl sandbox start --source .
to resume the existing sandbox cluster, but I can't access to Flyte UI. Here is the specific outputs I got:
β flytectl sandbox start
π§βπ Bootstrapping a brand new flyte cluster... π¨ π§
delete existing sandbox cluster [y/n]: n
Existing details of your sandboxπ¨βπ» Flyte is ready! Flyte UI is available at <http://localhost:30081/console> π π π
Add KUBECONFIG and FLYTECTL_CONFIG to your environment variable
export KUBECONFIG=$KUBECONFIG:/home/khuyen/.kube/config:/home/khuyen/.flyte/k3s/k3s.yaml
export FLYTECTL_CONFIG=/home/khuyen/.flyte/config-sandbox.yaml
I wonder what is the best way to resume the existing cluster?Haytham Abuelfutuh
12/27/2021, 9:34 PMflytectl version
CC @Prafulla Mahindrakar @YuvrajKhuyen Tran
12/27/2021, 9:39 PMHaytham Abuelfutuh
12/27/2021, 10:38 PMls ~/.flyte/
export KUBECONFIG=$KUBECONFIG:/home/khuyen/.kube/config:/home/khuyen/.flyte/k3s/k3s.yaml
export FLYTECTL_CONFIG=/home/khuyen/.flyte/config-sandbox.yaml
kubectl config use-context default
kubectl port-forward -n flyte ingress/flyte-system
curl -LO "<https://dl.k8s.io/release/$(curl> -L -s <https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl>"
kubectl get pods -A
docker exec -it <the container id> sh
Yuvraj
12/28/2021, 6:29 AMdocker start flyte-sandbox
Khuyen Tran
12/28/2021, 2:35 PMYuvraj
12/28/2021, 2:37 PMKhuyen Tran
12/28/2021, 8:00 PM