TGR 5 Helm

[Bailonis]

To give some context we have a small team, 2 backend and 2 front end developers, 1 Senior and 1 junior, on both cases. Unfortunately, the backend senior developer leaved the team, and I do not have much experience on helm charts, and we have 2 problems:

1 - kubernetes was not finding the image 2 - With the old images we were not able to gain external access, it gave a timeout in the frontend

I would like someone that could help me in this situation. Thanks in advance

[tomaszbarwicki]

Hey @Bailonis, thank you for reaching out to us. Would you mind provide a link to your repo so we can review the helm charts?

[Bailonis]

Hi there @tomaszbarwicki this is the repository link: https://github.com/catenax-ng/tx-demand-capacity-mgmt/tree/feat/DCMFOSS-53

We also received an advice from Sebastian Bezold, that youl be better have the helm charts this way:

<repo>
└───charts
    └───demand-capacity-management
        └───Chart.yaml
        └───templates
            └─── deployment-frontend.yaml
            └─── deployment-backend.yaml
            └─── service-frontend.yaml
            └─── service-backend.yaml

[tomaszbarwicki]

Yes, definitely that would be our recommendation to restructure your helm chart into Sebastian's suggestion.

With regards to your image issues, it seems you are using wrong image references in the deployments:

FRONTEND:

you have: ghcr.io/catenax-ng/demand-capacity-mgmt-frontend:latest

correct one is: ghcr.io/catenax-ng/tx-demand-capacity-mgmt/demand-capacity-mgmt-frontend:latest

BACKEND:

you have: ghcr.io/catenax-ng/tx-demand-capacity-mgmt-backend:1.16.0

it seems there is no image with 1.16.0 tag published, I used latest with below link and seems to work: ghcr.io/catenax-ng/tx-demand-capacity-mgmt/demand-capacity-mgmt-backend:latest

Hope that helps.

[Bailonis]

Thanks for the help! @tomaszbarwicki It would be possible to schedule a meeting, so I canl try to restructure, and resolve the images references?

[Bailonis]

So now I'm having this error: I went to the helpers.tpl, but is seems correct I tried to include fullname: on the Values.yaml file on the frontend part, but also did not work

[Bailonis]

Frontend is blocked by this error:

Back end is Blocked by this error:

[tomaszbarwicki]

Hi @Bailonis, as advised on Teams please update your values.yaml with correct port number for readiness and liveness probes for backend. Try also deploy the chart to one of our environments available for you using ArgoCD. It did work for me, all pods were running. Moreover as mentioned experiment a bit with memory allocation for frontend seems it uses it quickly. There is Grafana dashboard which can detail metrics of usage.

[Bailonis]

Issue resolved, thanks @tomaszbarwicki !