Skip to content

Add --insecure-allow-http flag to block insecure HTTP sources - #2119

Open
amarkdotdev wants to merge 1 commit into
fluxcd:mainfrom
amarkdotdev:feat/insecure-allow-http
Open

Add --insecure-allow-http flag to block insecure HTTP sources#2119
amarkdotdev wants to merge 1 commit into
fluxcd:mainfrom
amarkdotdev:feat/insecure-allow-http

Conversation

@amarkdotdev

Copy link
Copy Markdown

Summary

  • Add --insecure-allow-http (default true) via helper.ConnectionOptions (RFC-004 / Create a new flag to block use of HTTP endpoints for sources #806)
  • Block plain HTTP URLs, HTTP proxies, and spec.insecure when the flag is false for GitRepository, HelmRepository (default), HelmChart/OCI HelmRepository, Bucket, and OCIRepository
  • Stall Azure/GCP Buckets with spec.insecure as UnsupportedConnectionType
  • Reject HTTP→HTTPS redirect path for Git by disallowing http:// URLs when the flag is false (managed libgit2 transport removed; go-git redirect gated by scheme reject)

Test plan

  • Unit tests for GitRepository / HelmRepository / HelmChart / Bucket / OCIRepository insecure HTTP blocking
  • Controllers start with --insecure-allow-http=false and reject HTTP sources end-to-end

Fixes #806

Wire helper.ConnectionOptions into GitRepository, HelmRepository,
HelmChart, Bucket, and OCIRepository reconcilers so cluster admins
can disallow plain HTTP URLs, HTTP proxies, and spec.insecure when
the flag is set to false. Azure/GCP buckets with insecure stall as
UnsupportedConnectionType.

Fixes fluxcd#806

Signed-off-by: amarkdotdev <64331623+amarkdotdev@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a new flag to block use of HTTP endpoints for sources

1 participant