Question: Ensuring CMP Plugin Invocation for Bootstrap Components with ${TEMPLATE_VAR_**} Interpolation
#25417
Unanswered
david-VigneshN
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
I’m facing an intermittent issue with ArgoCD deployment. The
/generatescript reliably executes every 24 hours for each repository/ArgoCD application (on cache expiry or manual hard refresh) and interpolation of template variables such as${TEMPLATE_VAR_**}works as expected. However, in between these scheduled runs, raw manifests containing${TEMPLATE_VAR_**}sometimes get applied to the cluster without interpolation, resulting in misconfigured resources.Current Helm/ArgoCD Configuration
A relevant excerpt from our Helm values and repo-server settings is shown below:
/findcommand is configured to search for the existence of akustomization.yamlfile in the repository; if found, it triggers the plugin execution.Observed Scheduling and Manifest Issues
/generateruns every 24 hours and interpolation works.${TEMPLATE_VAR_**}) are applied to the cluster, bypassing interpolation/plugin logic.Questions for the Community
/generateexecutions?${TEMPLATE_VAR_**}?Request for Community Help
If you have insight or experience with enforcing CMP plugin invocation or safeguarding against un-interpolated manifests, please share your best practices, documentation, or example configurations.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions