10 Commits (312a07398fa6bef2a9e0d9a973de360dfb4c7044)

Author	SHA1	Message	Date
Antonio Gamez Diaz	ad6f45819a	Merge branch 'main' ... Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> Conflicts: pkg/registry/client.go pkg/registry/utils_test.go	2 years ago
Scott Rigby	7d190be0d0	Merge pull request #12128 from aryan9600/plain-http ... oci: Add flag --plain-http to enable working with HTTP registries	2 years ago
Andrew Block	c4870d990c	Add created OCI annotation ... Signed-off-by: Andrew Block <andy.block@gmail.com>	2 years ago
Sanskar Jaiswal	6defb96dac	oci: add tests for plain HTTP and insecure HTTPS registries ... Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>	2 years ago
Antonio Gamez Diaz	770c51ef0a	Add ClientOptResolver to test util file ... Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>	2 years ago
Andrew Block	f900e9f1b1	Attach annotations to OCI artifacts ... Signed-off-by: Andrew Block <andy.block@gmail.com>	2 years ago
Matt Farina	046646c944	Handle failed DNS case for Go 1.20+ ... Go 1.20 introduced DNS/CNAME handling changes. This can cause an IP address represented in hex, oct, etc to be looked up as DNS and fail. This change introduces a mock DNS resolver. Note, with the mock resolver, we don't need to use 0x7f000001 any longer. Keeping because it was already there. Signed-off-by: Matt Farina <matt.farina@suse.com>	2 years ago
Matt Farina	4e7e939f19	Updating the Go version in go.mod ... At this time both Go 1.19 and 1.20 are supported. The version specified in the go.mod file is the minimum version we expect Helm to be compiled against. This is the oldest supported version to support environments where others compile Helm. The Helm project is using Go 1.20 to build Helm itself. Updating to Go 1.19 also includes dealing with io/ioutil deprecation and some additional linting issues around staticcheck. All the staticcheck issues were in test files so linting was skipped for those. Signed-off-by: Matt Farina <matt.farina@suse.com>	2 years ago
Andrew Block	08593c8dd6	Added support for insecure OCI registries ... Signed-off-by: Andrew Block <andy.block@gmail.com>	2 years ago
Soule BA	b0ecb21056	Enable custom certificates option for OCI ... If implemented, users will be able to use custom certificates and CA to while interacting with OCI registries. Signed-off-by: Soule BA <bah.soule@gmail.com>	2 years ago