Sam Dowell
Sam Dowell
> The change looks good. Need to regenerate CRDs after API changes. `make configsync-crds` should do the trick. > > @sdowell did we document this in the contributor guide? No...
I expect this has to do with the details of local kind registry rather than a bug in helm/oci. From https://kind.sigs.k8s.io/docs/user/local-registry/#using-the-registry > If you build your own image and tag...
Our kind tests run in parallel on multiple clusters so for our e2e testing use case we would probably want to isolate the registry for each cluster anyways. From kind's...
``` failed to pull image kind-registry:5000/test-namespace:v1: Get https://kind-registry:5000/v2/: http: server gave HTTP response to HTTPS client ``` It appears this has to do with the `insecure` flag that you referenced...
@karlkfi This should add support for HTTP, although I'm still not sure whether it's needed https://github.com/GoogleContainerTools/kpt-config-sync/pull/316
> @karlkfi and @sdowell can comment on whether or not the linux/arm64 > > I see: > > ``` > PLATFORMS := linux_amd64 linux_arm64 darwin_amd64 darwin_arm64 windows_amd64 > ``` >...
/ok-to-test