You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
New tgz helm packages were created with version 0.1.1 which is referenced by the umbrella chart.
The text was updated successfully, but these errors were encountered: