sincecutoff.com
← all changes

ApplicationSet controller SCM proxy flags

Introduced 2026-08-04 · score 0.98

HOW TO USE IT

When the ApplicationSet controller must reach GitHub, GitLab, Gitea, or Bitbucket Server APIs through a proxy, set `--scm-proxy-url` and optionally `--scm-no-proxy` (or their documented environment variables). These settings route outbound SCM API requests; use `--proxy-url` for Kubernetes API traffic.

argocd-applicationset-controller \ --scm-proxy-url=http://<proxy-host>:<port> \ --scm-no-proxy=<host-or-CIDR>[,<host-or-CIDR>...]
ARGOCD_APPLICATIONSET_CONTROLLER_SCM_PROXY_URL=http://<proxy-host>:<port> ARGOCD_APPLICATIONSET_CONTROLLER_SCM_NO_PROXY=<host-or-CIDR>[,<host-or-CIDR>...]

WHY THIS HELPS

Generate ApplicationSets from SCM provider APIs through a proxy while keeping Kubernetes API traffic on its existing route.

BEFORE THIS CHANGE

Use `--proxy-url` to route the controller's traffic through a proxy, including Kubernetes API requests.

REQUIREMENTS AND LIMITATIONS

  • Version: v3.5.0
  • --scm-proxy-url / ARGOCD_APPLICATIONSET_CONTROLLER_SCM_PROXY_URL (required): HTTP/HTTPS proxy URL for outbound SCM provider API requests; does not affect Kubernetes API connectivity.
  • --scm-no-proxy / ARGOCD_APPLICATIONSET_CONTROLLER_SCM_NO_PROXY: Comma-separated hosts that bypass the SCM proxy.
  • --proxy-url: Use this standard kubectl flag to proxy Kubernetes API traffic.
  • Prerequisite: Use an HTTP/HTTPS proxy; documented provider coverage is GitHub, GitLab, Gitea, and Bitbucket Server.
  • `--scm-proxy-url` affects outbound SCM API requests and does not affect Kubernetes API server connectivity.
  • Proxy support is stated for GitHub, GitLab, Gitea, and Bitbucket Server.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card