search

tazama-lf / EKS-helm

EKS Helm charts to install all the applications needed for the Tazama platform
https://frmscoe.github.io/EKS-helm/
Apache License 2.0
4 stars 1 forks source link

Jopacc EKS deployment in Tazama env missing configs #33

Open scott45 opened 1 month ago

scott45 commented 1 month ago

In June/July, we deployed / migrated Jopacc env previosuly deployed in the Sybrin account to a Tazama managed AWS / Eks account. The deployment was done following the EKS helm docs that we have.

Fast forward,

Justus mentioned that we'll be upgrading jopacc to 2.0.0 soon because they are still running the old version. But while checking the current env running in our account, I noticed a few discrepancies. I wouldn't want to be blocked when the upgrade time comes and stall the Jopacc 2.0.0 upgrade.

I have a few questions;

  1. Jenkins configs e.g (k8s config / pod templates) in the jopacc env as specified in the docs aren't present however the deployment is up & working. I don't know if they were removed after the deployment. I remember us following the docs and creating them when Sybrin devops was helping me out on getting the env running during the sessions we had.
  2. Have seen a required env-var in the jopacc deployment I think for a one rule processor service pointing to a Sybrin managed system e.g ForwardUrl - https://frmnitro.sybrin.com/Sybrin.Nest/Services/ExecuteApiAsync that I'm not understanding well etc. I don't know if that's a default value.

Looking forward to hearing from you. Thanks.

vorsterk commented 1 month ago

Email sent with documentation to Scott for the jenkins agent .

As discussed on Slack I have fixed the Jenkins agent issue, and it's now functioning correctly.

In case of Jenkins restarts, I’ve attached a user manual in both markdown and PDF formats, which details how to handle the Jenkins agent configuration and avoid information loss. The manual includes steps to restore the agent when necessary.

Additionally, I’ve attached the Dockerfile used for building the Jenkins agent image. I've also set up a Jenkins job that replicates the functionality of the Dockerfile, allowing you to rebuild and deploy the Jenkins agent with ease. You can choose either method depending on your preference.

Regarding point 2 in your issue log, the environment variable ForwardUrl refers to Sybrin's Case Management System (CMS) service, which Jopacc uses for their case processing. This is a default value needed for integration with the Sybrin platform, so no changes should be required unless you’re customizing the environment.