Hi 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?

Hi Reginaldo, what are you getting when running

orchest status

?

Failed to fetch Orchest Cluster status. The Orchest Cluster named 'cluster-1' in namespace 'orchest' could not be found.

Is the

orchest

namespace there? Did you get any interesting message when running

orchest install

?

orchest install --dev results in:

What pods are running in the orchest namespace? Any chance that the minikube mount is failing? The

--dev

flag expects the Orchest repo to be mounted to support hot reloading (see

--mount-string="$(pwd):/orchest-dev-repo" --mount

). Maybe you weren't in the repository directory when starting minikube?

Humm...

About the mounting, see cluster-for-development in the same page

I think it is the problem, Jacopo... I will try again.. thanks for a while...

When 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.

The repo is in my home dir, but I don't point correctly to it when run with dev flag....

Could you clarify? Do you mean applying code changes locally without using --dev?

Sorry. 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. 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

Thanks 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"

Note, if Orchest is not installed,

export TAG="$(orchest version --latest)"

will silently fail

ok, thank you Jacopo.