Support proxy option for the Gitlab Agent

Release notes

Users' Kubernetes clusters can often access GitLab only through a proxy. Until now, the GitLab agent for Kubernetes did not support proxied connections. We added support for extra environment variables to the agentk Helm package to support proxied connections.

Problem to solve

Some of our K8S clusters have restricted internet access and must use a Squid proxy to reach the internet The Gitlab K8S agents require internet access and do not have a proxy option.

Proposal

Update the Agent to support the ability to use a proxy for connecting to the internet

• Add support for the industry-standard HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables? But this might be inconsistent with the fact that everything is configurable via the configuration file. Maybe support both (config in file overrides the env variables)?
• Configuration should be applied to ALL outbound connections: kas, kubernetes API, Cilium, etc

Document how to use the new functionality

Intended users

Metrics

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.