Hello guys I have a problem to perform the restart through t

Question

Hello guys I have a problem to perform the restart through the interface I ll send more information in the thread

Bruno Oliveira dos Santos · Answer

I made the json adjustment to enable authentication When I go to restart to apply the change I get this error

Bruno Oliveira dos Santos · Answer

Do you have any idea what this error could be

Bruno Oliveira dos Santos · Answer

For better context I uploaded a GKE cluster and deployed the application in two different namespaces each namespace is attached to a node group In a namespace application I didn t have this problem it s happening in the other one

Jacopo · Answer

Anything interesting in the browser debugging tools Both console messages and network request response code and payload

Jacopo · Answer

Any chance that the namespace for which things are working is the default namespace Can you check if the values of the env variables `ORCHEST NAMESPACE` and `ORCHEST CLUSTER` are set correctly for the `orchest api` pod part of the namespace for which things are failing

Jacopo · Answer

Should also check the following pods logs when making a restart request which fails `orchest api` `orchest webserver` `orchest controller`

Bruno Oliveira dos Santos · Answer

Hello Jacopo Thank you for the informations Looking at the logs I found some inconsistencies and managed to do a reset and the mentioned problem was solved

Bruno Oliveira dos Santos · Answer

However I have another problem and I would like some advice from you

Bruno Oliveira dos Santos · Answer

In this same described scenario a cluster running two Orchests with two different namespaces and in this cluster I have two NodePools Through Labels I attached the main deployments to each corresponding NodePool

Bruno Oliveira dos Santos · Answer

However when I go to build some environment I noticed that it uploads a POD called image build task and this POD is not being attached to the correct NodePool causing an error

Bruno Oliveira dos Santos · Answer

Is there any way for this problem to be resolved If you need more details I ll let you know in this thread

Jacopo · Answer

gt Hello Jacopo Thank you for the informations Looking at the logs I found some inconsistencies and managed to do a reset and the mentioned problem was solved happy to hear that gt However when I go to build some environment I noticed that it uploads a POD called image build task and this POD is not being attached to the correct NodePool causing an error Take a look at ` get image build manifest` in `services orchest api app app core image utils py` you ll see the `pod scheduling modify image builder pod scheduling behaviour manifest ` call at the end of the function the `services orchest api app app core pod scheduling py` module is in charge of doing changes to manifests so that scheduling happens in a way we like in this particular case it ll look for the `WORKER PLANE SELECTOR` env variable of the orchest api and celery worker to adjust the behaviour for multi tenancy you ll likely need to do some minor changes around these variables