From f23f1005b73bcc2e083b350d1591ec422fb71917 Mon Sep 17 00:00:00 2001 From: Gianni Carafa Date: Mon, 2 Sep 2024 00:13:29 +0200 Subject: [PATCH] create an ingress for the registry --- config/samples/application_v1alpha1_kubero.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/config/samples/application_v1alpha1_kubero.yaml b/config/samples/application_v1alpha1_kubero.yaml index cca0648..01ed876 100644 --- a/config/samples/application_v1alpha1_kubero.yaml +++ b/config/samples/application_v1alpha1_kubero.yaml @@ -31,6 +31,7 @@ spec: registry: enabled: false # creates registry credentials for a external or a local registry (required for build strategy apps) create: false # spins up a local registry + public: true # makes the registry public available #host: registry.kubero.svc.cluster.local # works for pushes, but not for pulls. DO NOT USE THIS :( since it requires to configure all nodes ot acceppt this "insecure" registry #host: docker.io # requires a docker account. Might be the best choice when running on a non public domain host: registry.demo.kubero.dev # will make your images publicly avaialble with a basic auth protection