Not able to set env var for target group long name via helm deploy

[rmullinnix461332]

The helm chart only supports environment var names for aws region, aws account id and cluster vpc id. Need the ability to also set TARGET_GROUP_NAME_LEN_MODE as part of helm deploy. We run multiple VPCs under the same account id. We have a separate qa environment on a separate vpc where we want to stage lattice services. The default setup for target group names results in the same target group name for both vpcs. The target group name in qa is overwriting the production target group. The TARGET_GROUP_NAME_LEN_MODE resolves this issue, but not able to set this value on helm deploy.

helm/values.yaml:
77 targetGroupNameLen: short

helm/templates/deployment.yaml
85. - name: TARGET_GROUP_NAME_LEN_MODE
86. value: {{ .Values.targetGroupNameLen }}

or add to the existing config map

[xWink]

Thanks for reporting the issue, we will be investigating it further. Please watch this channel for more updates, and feel free to reach out!

[zijun726911]

We run multiple VPCs under the same account id. We have a separate qa environment on a separate vpc where we want to stage lattice services. The default setup for target group names results in the same target group name for both vpcs. The target group name in qa is overwriting the production target group.

We have plan to deprecate the different TARGET_GROUP_NAME_LEN_MODE, and make normal target group name model don't cause above bug. It's already in our roadmap, we target to fix it for v0.1.0 beta release.

[rmullinnix461332]

this is a blocker for us being able to move forward with future lattice service development. we are not able to have qa environment due to it stomping on production.

[erikfuller]

@rmullinnix461332 can you have a look at #425 and see if the proposed approach would address your use case?

[graehren]

Targeting to resolve this issue with our upcoming v0.0.18 release

[graehren]

This should be resolved with PR #457 which will be available in the next release.

[graehren]

@rmullinnix461332 we released EKS controller version v0.0.18 yesterday which contains a revised TG naming strategy. This update should resolve your issues with the TG naming conflict. Please let us know if you have any other questions.