From d5e485f9bf8418961bd1a25fb153ba9e3fbd96ea Mon Sep 17 00:00:00 2001 From: Max Erenberg Date: Mon, 3 Jan 2022 10:29:12 -0500 Subject: [PATCH] use NodePort instead of Ingress for Harbor --- harbor/values.yaml | 26 ++++++++++++++++++-------- 1 file changed, 18 insertions(+), 8 deletions(-) diff --git a/harbor/values.yaml b/harbor/values.yaml index 0f9d1c2..1de2082 100644 --- a/harbor/values.yaml +++ b/harbor/values.yaml @@ -3,14 +3,24 @@ expose: # We are performing TLS termination OUTSIDE of the k8s cluster tls: enabled: false - type: ingress - ingress: - hosts: - core: registry.cloud.csclub.uwaterloo.ca - notary: notary.cloud.csclub.uwaterloo.ca - annotations: - ingress.kubernetes.io/ssl-redirect: "false" - nginx.ingress.kubernetes.io/ssl-redirect: "false" + #type: ingress + #ingress: + # hosts: + # core: registry.cloud.csclub.uwaterloo.ca + # notary: notary.cloud.csclub.uwaterloo.ca + # annotations: + # ingress.kubernetes.io/ssl-redirect: "false" + # nginx.ingress.kubernetes.io/ssl-redirect: "false" + type: nodePort + nodePort: + name: harbor + ports: + http: + port: 80 + nodePort: 30002 + notary: + port: 4443 + nodePort: 30004 externalURL: https://registry.cloud.csclub.uwaterloo.ca harborAdminPassword: REPLACE_ME # must be a string of 16 chars