Include Custom Stage Variables in CI_COMMON_ENV_POD ConfigMap
next fiscal quarter
S
Shamrock green Newt
Description:
The CI_COMMON_ENV_POD feature flag reduces pod.yaml size by storing Harness internal environment variables in a shared ConfigMap. However, custom stage variables are still duplicated across every step container, even when not referenced by that step.
Request:
Extend this optimization to include custom stage variables in the common ConfigMap, and only inject variables into steps that actually use them.
This would significantly reduce pod.yaml size for pipelines with many steps and stage variables, helping prevent "etcdserver: request is too large" failures in Kubernetes environments.
Log In
P
Pewter Vicuna
Hi Shivkumar
We also highlighted during out previous discussions that the secrets are being repeated for each step in pod.yaml manifest. As we have ~100 steps in our pipelines, this is resulting in large object size which is being blocked by GCP as the limit for object size is 1.5MB on their end.
We need the secrets also to be added to config map and refer to that instead of duplicating them for each step.
s
shivkumar.loka
marked this post as
next fiscal quarter
s
shivkumar.loka
Hey Nick
Thank you for your request. I have created a ticket to evaluate and track this request with our engineering team. We will prioritize this enhancement and keep you posted. Please continue to monitor our release notes page here for more updates: https://developer.harness.io/release-notes/continuous-integration
Thank you
Cheers
Shivkumar Loka
Harness Product Team