Allow setting custom extra environment variables in http-add-on components

[ilia-medvedev]

It's a common practice in Helm charts to use extraEnv:[] value that allows users to set extra environment variables for containers. As of now http-add-on only allows setting predefined variables for each component.

Use-Case

This will help with testing addition of new environment variables for http-add-on.

Specification

• Demand helm 3 crd support #1

[ramsaikrishna]

@ilia-medvedev-codefresh Can we set queue for http interceptor as we are facing issue for cold start request. We have seen the pod scaling is trigger but failing to send response until idle timeout (4 mins for azure lb) . we have set tcptimeout and response timeout for interceptor high around 10s as we have long timing apis for our application. our cold start request is failing but concurrent or next request is successful . can you guide me what to set?

[esteban1983cl]

+1 to this request, I want to add OTEL_PROM_EXPORTER_ENABLED and OTEL_PROM_EXPORTER_PORT env vars to interceptor

[robinderooij-rl]

This is already implemented in #777 @esteban1983cl

[jhead-aai]

Ideally this should have been implemented as a list of objects. As a map you are unable to set complex environment variables via configmaps, secrets, or the downward API. Perhaps add a env option (as a list of objects) for people to use alongside extraEnv?

Example:

- name: HOST_IP
  valueFrom:
    fieldRef:
      fieldPath: status.hostIP