quick setup deployment error on local vm

[jagannathamkrishna]

After go run digit_setup.go i am getting this error
Thanks
------------------------------------ DEPLOYING CLUSTER CONFIGS ------------------------------------
2023/05/16 16:06:58 helm template -f /home/krishna/DIGIT-DevOps/deploy-as-code/helm/environments/quickstart-config.yaml --output-dir /tmp/helm-230921531 -f /home/krishna/DIGIT-DevOps/deploy-as-code/helm/environments/quickstart-config-secrets.yaml .
2023/05/16 16:06:59 exit status 1: error: resource mapping not found for name: "root-ingress" namespace: "egov" from "ingress/root-ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
ensure CRDs are installed first

panic: exit status 1: error: resource mapping not found for name: "root-ingress" namespace: "egov" from "ingress/root-ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
ensure CRDs are installed first

[nikhilmulinti]

Hi @jagannathamkrishna , Can you please use this branch kubernetes-1.22-changes to deploy the helm charts? Do let me know incase the same issue occurs again

[jagannathamkrishna]

Hi Nikhil,
Thanks for the reply, the issue is resolved, but i am facing a new issue in post deployment when: kubectl get pods -A
getting this as per documentation(pgr-services are in crashloopbackoff state) in postman after running seed data collection
this error is coming
In Network inspect
error 500 is coming in egov-mdms-service.

thanks for the help

[jagannathamkrishna]

Thanks Egovernments/Digit-Core for the help. The error: no match kind "Ingress" in version "extensions/v1beta1" is resolved by deploying the master branch itself. But facing a new issue in postman, the egov-mdms-service is throwing error 500. Even after deleting the pods, they are still in crashloopbackoff only. Can this be fixed by deploying branch kubernetes-1.22-changes Thanks in advance. Regards

…

On Tue, 23 May 2023 at 10:45, nikhilmulinti-egov ***@***.***> wrote: Hi @jagannathamkrishna <https://github.com/jagannathamkrishna> , Can you please use this branch kubernetes-1.22-changes to deploy the helm charts? Do let me know incase the same issue occurs again — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A74R2I5BR7W5GY5EXYQTFZDXHRBVTANCNFSM6AAAAAAYDO5MII> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Thanks and Best Regards,* *Krishna Chaitanya. J* * DevOps Consultant* *+91-9949447178* https://www.perpetualblock.io [image: Perpetual Block AG]

[shashankdhwaniris]

i am also facing the same issue while deploying the application on server, some pods are constantly crashing even after deleting the pods

[naresh-egov]

@jagannathamkrishna Kindly initiate a pod restart. Once the reboot is completed, please provide the pod description by using the 'kubectl describe pod ' command. This will aid us in further debugging