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
I've been unsuccessful for some time now in figuring out the proper and preferred way to override the values that are being applied to ingress nginx while using argocd to apply the applications it manages when setting argocd_manage_add_ons = true.
I figured the ingress_nginx_helm_config would still apply here, but that does not and my values are not being picked up.
Is there any documentation on how this is to be managed? This seems like a pretty common request that'll need to be done for many people's installations and I don't see any repo in all of github that manages doing this successfully.
This seems to fix the issue I'm having but looking for best practices as to how this was envisioned working?
The text was updated successfully, but these errors were encountered:
that-kampe-steak
changed the title
Question/Bug/Feature? Override values for argocd_addon_applicaiton
Question/Bug/Feature? Override values for argocd_addon_application
Jan 10, 2023
This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days
Hello,
I've been unsuccessful for some time now in figuring out the proper and preferred way to override the values that are being applied to ingress nginx while using argocd to apply the applications it manages when setting
argocd_manage_add_ons = true
.I figured the
ingress_nginx_helm_config
would still apply here, but that does not and my values are not being picked up.Is there any documentation on how this is to be managed? This seems like a pretty common request that'll need to be done for many people's installations and I don't see any repo in all of github that manages doing this successfully.
This seems to fix the issue I'm having but looking for best practices as to how this was envisioned working?
The text was updated successfully, but these errors were encountered: