Could someone tell me why orchest controller can t start all

Question

Could someone tell me why orchest controller can t start all pods The <http controller orchest io deploy ingress|controller orchest io deploy ingress> false option is set why my nginx is configured separately

Alexsander Pereira · Answer

If I apply with the option to allow orchest controller to create nginx it works

Alexsander Pereira · Answer

```apiVersion kind OrchestCluster metadata name cluster 1 namespace orchest annotations false spec singleNode true orchest authServer image public ecr aws u5k1d2l0 orchest auth server v2022 10 5 1 0 0 orchestWebServer image public ecr aws u5k1d2l0 orchest webserver v2022 10 5 1 0 0```

Yannick · Answer

A bit more info is added here <https docs orchest io en stable getting started installation html install nginx|https docs orchest io en stable getting started installation html install nginx> Basically the orchest controller will based on your k8s distro e g EKS decide whether or not to automatically deploy the Nginx Ingress controller unless you add the annotation to not deploy Nginx Ingress at all If your cluster already has ingress configured then there would be an error if the orchest controller tries to set it up again So I guess setting the annotation to false works for you

Alexsander Pereira · Answer

< Yannick> Would that option ```notes false ``` It is already defined and the error still occurs

Alexsander Pereira · Answer

orchest controller yml orchest cluster yml

Alexsander Pereira · Answer

I m testing again by creating an empty cluster

Alexsander Pereira · Answer

Same error

Yannick · Answer

What cluster did you create Because based on the cluster we automatically set the annotation Still using EKS < Navid H> Something you can quickly look at

Navid H · Answer

After you created the cluster controller changes the `OrchestCluster` object can you also post that one

Yannick · Answer

gt If I apply with the option to allow orchest controller to create nginx it works So you have two options on EKS 1 Don t set the ` false ` annotation and let Orchest set up ingress for you Which is easier than having to install nginx yourself but of course allows less configuration from your side 2 Install nginx ingress controller on the cluster yourself and then install Orchest with the ` false ` annotation

Alexsander Pereira · Answer

I didn t understand Did you see the configuration files I already add the annotation ```<http controller orchest io deploy ingress|controller orchest io deploy ingress> false ```

Alexsander Pereira · Answer

< Navid H> < Yannick> I install Nginx and create the cluster with this annotation but even so the problem indicated in the logs happens

Yannick · Answer

< Navid H> Could you try to reproduce this on EKS So first install Nginx and then installing Orchest with the annotation pray

Alexsander Pereira · Answer

Okay

Alexsander Pereira · Answer

I m changing the installation order Old orchest gt nginx New nginx gt orchest

Navid H · Answer

< Alexsander Pereira> I ll try to reproduce Will comeback here

Alexsander Pereira · Answer

Problem now occurs on installation ```namespace monitoring created daemonset apps node exporter created service node exporter created namespace ingress nginx created serviceaccount ingress nginx created serviceaccount ingress nginx admission created created created created created created created created created configmap ingress nginx controller created service ingress nginx controller created service ingress nginx controller admission created deployment apps ingress nginx controller created job batch ingress nginx admission create created job batch ingress nginx admission patch created created created namespace orchest created serviceaccount orchest controller created created created created created service orchest controller created deployment apps orchest controller created Error from server InternalError error when creating files orchest controller yml Internal error occurred failed calling webhook failed to call webhook Post no endpoints available for service ingress nginx controller admission ```

Navid H · Answer

I m looking into it

Alexsander Pereira · Answer

< Navid H> Any news I need to create an Orchest cluster in production

Navid H · Answer

Unfortunately I was not able to reproduce it in EKS or Minikube cluster maybe we can jump on a call to debug the issue together

Alexsander Pereira · Answer

Have you tried deployer using our yaml

Navid H · Answer

I tried your `OrchestCluster` yaml file it get stuck in pulling `Auth Server` because I don t have access to your custom image but it does not try to deploy ingress could you run the following command ```kubectl get ingressclass```

Alexsander Pereira · Answer

I ll send you the step by step without the custom images

Alexsander Pereira · Answer

This is the Jinja2 template from nginx In it I just modify the load balancer tags and add the ACM certificate

Alexsander Pereira · Answer

Steps 1 kubectl apply f files nginx yml 2 kubectl apply f files orchest controller yml The error happens even before deploying the yaml cluster

Alexsander Pereira · Answer

orchest controller yml

Navid H · Answer

So it happens before deploying the `OrchestCluster`

Navid H · Answer

the ingress and other third party components can be enabled at controller deployment level if you see the error before creating the `OrchestCluster` CRD then ingress should have been enabled at controller level deployment but I don t see this in you deployment

Alexsander Pereira · Answer

I will send you the outputs of each deployment

Navid H · Answer

After investigating it for a while I think this issue is not related to orchest it seems your cluster is deployed in a way that the nginx admission webhook is not reachable maybe some calico configuration for port 443 I don t know to validate that the problem is related to webhook you can remove the admission webhook and try again but I believe this is not a good solution it is better to invest time in figuring out why admission webhook is not reachable you can remove the admission webhook by following command ```kubectl delete A validatingwebhookconfiguration ingress nginx admission```

Alexsander Pereira · Answer

But how do I solve it then We at Dadosfera are blocked from using Orchest and we don t know how to solve this problem

Navid H · Answer

the easy solution is to run that command

Alexsander Pereira · Answer

After installing nginx And before orchest

Navid H · Answer

yes