Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC-0004]: imagerepo: Add support for insecure registries #395

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aryan9600
Copy link
Member

@aryan9600 aryan9600 commented Jun 19, 2023

Add a new field .spec.insecure to the ImageRepository API to allow indicating that the registry is an insecure registry, i.e. hosted at an HTTP endpoint. Furthermore, add a new flag --insecure-allow-http to allow the controller to make HTTP requests. By default, it is set to true to ensure backwards compatibility.

Implements RFC-0004.

Fixes: #324,#325
Part of: fluxcd/flux2#3310

@aryan9600 aryan9600 changed the title imagerepo: Add support for insecure registries [RFC-0004]: imagerepo: Add support for insecure registries Jun 19, 2023
@aryan9600 aryan9600 marked this pull request as draft June 19, 2023 12:56
@aryan9600 aryan9600 force-pushed the rfc-insecure-http branch 2 times, most recently from 796a8a1 to 5790e64 Compare July 3, 2023 07:00
@aryan9600 aryan9600 marked this pull request as ready for review July 3, 2023 07:00
Add a new field `.spec.insecure` to the `ImageRepository` API to allow
indicating that the registry is an insecure registry, i.e. hosted at an
HTTP endpoint. Furthermore, add a new flag `--insecure-allow-http` to
allow the controller to make HTTP requests. By default, it is set to
true to ensure backwards compatibility.

Implements [RFC-0004](https://github.com/fluxcd/flux2/tree/main/rfcs/0004-insecure-http).

Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.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.

[RFC-004] Add new flag --insecure-allow-http
1 participant