Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update api and frontend helm charts for better handling of environments #19

Open
jcadam14 opened this issue Oct 30, 2024 · 0 comments · May be fixed by #20
Open

Update api and frontend helm charts for better handling of environments #19

jcadam14 opened this issue Oct 30, 2024 · 0 comments · May be fixed by #20
Assignees

Comments

@jcadam14
Copy link
Collaborator

With the updates to EKS v1.28, it was identified that there is an opportunity to allow both umbrella and standalone helm charts to be deployed. However, because of the way the standalone charts define names in selectors and labels, this would cause issues with helm deployments.

Update the charts so that names are consistent for specific labels/selectors. The following were identified as causing issues when switching between helm installs:

  • app.kubernetes.io/instance: regtech-sbl (this hardcodes the instance, which is a key determiner for if helm can upgrade an existing deployment)
  • app.kubernetes.io/name (this will be set to the service fullname to better identify the service)
  • The container name is set to the fullname, to ensure multiple containers aren't created for a deployment when switching between helm installs

New tgz helm packages were created with version 0.1.1 which is referenced by the umbrella chart.

@jcadam14 jcadam14 self-assigned this Oct 30, 2024
@jcadam14 jcadam14 linked a pull request Oct 30, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant