Title
r
Reginaldo Ré
03/22/2023, 11:49 AMHi everyone! I need some help to configure my dev environment. I followed the development workflow steps (https://docs.orchest.io/en/stable/development/development_workflow.html). Everything installed without any problems, but after that, I didn't see orchest running on minikube when I took a look on k9s. Any tips?
j
Jacopo
03/22/2023, 11:51 AMHi Reginaldo, what are you getting when running
orchest statusr
Reginaldo Ré
03/22/2023, 11:56 AMFailed to fetch Orchest Cluster status.
The Orchest Cluster named 'cluster-1' in namespace 'orchest' could not be found.
j
Jacopo
03/22/2023, 11:57 AMIs the
orchestorchest installr
Reginaldo Ré
03/22/2023, 11:58 AMorchest install --dev results in:
Installing into existing namespace: orchest.
Installing the Orchest Controller to manage the Orchest Cluster...
nothing else
Namespaces active are:
default Active 102m
ingress-nginx Active 102m
kube-node-lease Active 102m
kube-public Active 102m
kube-system Active 102m
orchest Active 89m
trying to access orchest using chrome results in 404 from nginx
j
Jacopo
03/22/2023, 12:05 PMWhat pods are running in the orchest namespace? Any chance that the minikube mount is failing? The
--dev--mount-string="$(pwd):/orchest-dev-repo" --mountr
Reginaldo Ré
03/22/2023, 12:07 PMHumm...
j
Jacopo
03/22/2023, 12:08 PMAbout the mounting, see cluster-for-development in the same page
r
Reginaldo Ré
03/22/2023, 12:09 PMI think it is the problem, Jacopo...
I will try again.. thanks for a while...
👍 1
Your help was great...
👍 1
y
Yannick
03/22/2023, 12:13 PMWhen installing through the dev flag you indeed need the mount and run the build containers script. The dev flag expects some files in the repo to be present.
r
Reginaldo Ré
03/22/2023, 12:14 PMThe repo is in my home dir, but I don't point correctly to it when run with dev flag....
But... it is possible to install a local image version without use dev flag ?
j
Jacopo
03/22/2023, 12:28 PMCould you clarify? Do you mean applying code changes locally without using --dev?
r
Reginaldo Ré
03/22/2023, 1:43 PMSorry. Considering you need to use the build-container.sh script when changes are made, and, to avoid issues with hot reloading, couldn't I just build a set of imagens (for example, scripts/build_container.sh -i orchest-api -t $TAG -o $TAG) and run orchest install without dev flag?
I tested a new minikube mounting using local repo directory and the problem isn't on hot reloading. Also, the issues remain, there are no resources in orchest namespace and the pods running are: ingress-nginx-admission-create-t98nq, ingress-nginx-admission-patch-sb5v9, ingress-nginx-controller-77669ff58-7868j, coredns-787d4945fb-v57dx, kube-apiserver-minikube, kube-controller-manager-minikube, kube-proxy-cnqhh, kube-scheduler-minikube, storage-provisioner.
👀 1
j
Jacopo
03/22/2023, 2:33 PMSorry. Considering you need to use the build-container.sh script when changes are made, and, to avoid issues with hot reloading, couldn't I just build a set of imagens (for example, scripts/build_container.sh -i orchest-api -t $TAG -o $TAG) and run orchest install without dev flag?Sorry forgot to reply here, yes, you can indeed do that, it' something we did often for development, see https://docs.orchest.io/en/stable/development/development_workflow.html#redeploying-orchest-after-code-changes
r
Reginaldo Ré
03/22/2023, 3:00 PMThanks for your attention.
In that case, to make a first deploy (without any changes) the steps are:
#Enter inside the root of the orchest repository
cd orchest_local_repo
#Run minikube without --mount-string option
minikube delete
minikube start \
--cpus max \
--memory max \
--addons ingress metrics-server
# Use minikube's Docker daemon:
eval $(minikube -p minikube docker-env)
# Set the tag to the latest Orchest version available
export TAG="$(orchest version --latest)"
# Build the minimal set of images for Orchest to run
scripts/build_container.sh -M -t $TAG -o $TAG
# Install orchest
orchest install
So, after any change (like in orchest-api), the steps are:
# Rebuild the images that need it
scripts/build_container.sh -i orchest-api -t $TAG -o $TAG
# Kill the pods of the orchest-api, so that the new image gets used
# when new pod gets automatically deployed.
kubectl delete pods -n orchest -l "app.kubernetes.io/name=orchest-api"
j
Jacopo
03/22/2023, 4:05 PMNote, if Orchest is not installed,
export TAG="$(orchest version --latest)"aside from that, this looks correct, but you need to run install before setting the $TAG variable
r
Reginaldo Ré
03/22/2023, 4:13 PMok, thank you Jacopo.
👍 1
Just to give a feedback. After to follow the steps discussed (without use dev flag), pods in the namespace orchestra are ok and orchestra seems to be correctly installed. I will conduct some tests. Hot reloading might have been the root of the problems I faced.Thank you, again!
👍 2
🙌 1